Skip to main content
A plain sequence sends the same messages on a timer. A smart sequence reacts to what happens: who has an email address, who replies, and who is out of office. These building blocks work together inside the sequence editor.

​
Watch it live

  1. Start with one goal. For example: introduce an opportunity, or re-engage past candidates.
  2. Make sure you can reach people. Add Enrich Email & Phone before email and SMS actions, choose which details to find, and add a Condition after it (Has email or Has mobile phone, set to Must have) so you can handle contacts it couldn’t find details for.
  3. Split by who you can reach. Add a Condition with Must have and Exclude requirements, such as has email or a do-not-contact tag, and build the True and False paths.
  4. Plan for replies. Open Reply Identification. For each reply type, choose a tag, a pipeline stage, another sequence, or nothing. Set the reporting category, and decide whether unclear and out-of-office replies continue or reschedule the sequence.
  5. Add human steps with a Task step where a call or personal message works better than automation. The sequence waits for it.
  6. Personalize. Use @ smart fields, and AI prompts that use each contact’s role and career history.
  7. Check readiness. Use the launch preview to catch missing contact details before you launch.
  8. Review and adjust. After launch, use Sequence analytics to see which steps work. You can keep editing messages and conditions, but the changes only reach contacts not yet queued.

​
Conditions

A Condition step splits the sequence into two paths, so each contact follows the one that fits.
  • True is for contacts who pass: every Must have requirement is met and no Exclude requirement matches.
  • False is for everyone else: a Must have requirement fails, or an Exclude requirement matches.
Add the steps you want on each path. Deleting a Condition removes both of its paths and every step inside them, and that can’t be undone. You can edit a Condition at any time, even when contacts are already in the sequence, but the change only applies to contacts who haven’t been queued yet. Once contacts are in a sequence you can’t delete steps. See Edit a sequence that already has contacts.

​
What you can check

For each requirement, choose Must have or Exclude, or leave it unset to ignore it.

​
Examples

  • Skip people you must not contact. Set Exclude tags to your do-not-contact tag, and put your outreach on the True path. Tagged contacts follow False, where you leave the path empty or end the sequence.
  • Choose a channel. Must have an email: send an email on True. On False, send a social message instead, or follow the enrichment pro tip below.
  • Only the right connections. Must be a 1st connection: send a direct message on True, and an invitation on False.

​
Enrichment steps

Add an Enrich Email & Phone step before an outreach action so the sequence has the details it needs. For each step you choose:
  • What to find: email, phone, CV and social profile, or a combination.
  • Whether email enrichment looks for work or private addresses, and whether to require only that type or use it as the preferred one.
If the sequence has an SMS sender, Jobin suggests phone enrichment. The selected behavior shows in the launch preview. See Contact enrichment.
Pro tip: always follow enrichment with a Condition. Enrichment doesn’t always find what you asked for. A Condition right after it tells you how it went, and lets you decide what to do in each case. For example, after an email enrichment, add a Has email condition set to Must have. Contacts with an email take the True path, where you send the email. Contacts without one take the False path, where you can do something else: a Notify step to alert yourself or a colleague, a Task step to find the details by hand, or an Assign step to tag them for later review and segmentation.

​
Follow enrichment with a condition

  1. Add your Enrich Email & Phone step, and choose what to find.
  2. Add a Condition directly after it with the requirement for what you enriched: Has email for email, or Has mobile phone for SMS. Set it to Must have.
  3. For email, set the condition’s email address type to match the enrichment (Work or Private). Auto follows the sequence’s address type.
  4. Put the outreach on the True path.
  5. Decide what the False path does for contacts you couldn’t enrich:
    • Notify a teammate (or yourself) that the contact needs attention.
    • Create a Task, so someone finds the details manually.
    • Assign a tag, such as “needs email”, so you can find and review these contacts later.
    • Or end the sequence for them.

​
Reply handling

Open Reply Identification from the sequence editor to define how replies are categorised and what happens next. Jobin’s AI matches the intent of a reply, not its exact wording, so describe the type of reply and don’t list sample replies.

​
Reply types

Each sequence starts with these rules:
  • Interested (counted as positive).
  • Not interested (counted as negative).
  • Maybe - Later (not counted either way until you choose).
  • Inconclusive and Out of office, two locked system rules you can’t rename.
Add your own types, such as a referral or a question about salary. A type’s name is a short label of up to 35 characters. Drag rules to reorder them.

​
What Jobin does when a reply matches

For each type, choose what happens. You can combine the first three:
  • Tag. Add tags to the contact.
  • Pipeline. Move the contact to a pipeline stage.
  • Sequence. Add the contact to another sequence.
  • Nothing. Just categorise the reply.
A categorised reply stops the sequence for that contact and counts in your sequence analytics. To follow up automatically, give a type the Sequence action (the sequence you’re editing isn’t offered) or the Pipeline action. See start another sequence when a candidate replies and move a candidate to a stage when they reply. To move candidates for every reply on a job, use a stage entry rule instead.

​
Count it in reports

Set each type’s Reply reporting category to Positive, Negative, or Unclassified. Analytics uses it to count positive, negative, and unclassified replies.

​
The two system rules

  • Inconclusive covers replies the AI can’t place. Turn on Continue the sequence instead of stopping it to keep going when a reply is unclear. While it’s on, this rule can’t be removed and can’t start another sequence.
  • Out of office covers automatic replies. Reschedule the sequence when this triggers is on by default, so the next step is pushed back rather than the sequence ending, and the auto-reply isn’t counted as a human reply. While it’s on, this rule can’t start another sequence either.

​
Tasks and human steps

Add a Task step when a person needs to act. You can write instructions for the recruiter, choose the priority, assignee, and task queue, and set a relative due time in minutes, hours, or days. The sequence waits until the task is resolved, and the pending task opens directly from the contact’s active sequence. A sequence made only of tasks doesn’t need a messaging sender. See Tasks and task queues.

​
Personalization

  • Smart fields. Type @ in the message composer to search for and insert fields for the contact, the sender, the job, and your custom CRM data.
  • AI prompts. Use AI with a contact’s role, career history, company, or profile summary to draft an introduction or icebreaker, then add your own call to action.
  • Formatting. Set one font family and size across a whole email, and clear unwanted formatting before you send.

​
Meetings

When a candidate books a meeting, Jobin can reflect it as a sequence outcome, so it counts in your sequence analytics. See Calendar and meetings.

​
How-to guides

Quick, step-by-step answers for common tasks:

Sequences

Build and launch a sequence.

Inbox

Read and answer the replies.