How to read these sequences
Each sequence is a chain of steps: an action (profile visit, LinkedIn invitation, LinkedIn message, email, WhatsApp message), a wait, or a condition that splits into two branches. The conditions used here are deliberately simple and observable: invitation accepted, replied, email opened, has email, has phone.
- Days are indicative: Day 3 means three days after the previous step, inside your sending windows.
- A time-based condition (invitation accepted, email opened, replied) is checked for a few days before taking the “no” branch. We give a suggested duration.
- A reply stops everything: as soon as someone replies, the sequence stops for them and you take over by hand.
- Variables like {{first_name|there}} are replaced with the prospect’s data, or with the value after the pipe when it is missing.
Sequence 1: LinkedIn first, to reach a decision maker
For: people found on LinkedIn (founders, sales leaders, HR managers). The most common and gentlest sequence.
- 1Day 0: profile visit
They may see your name in their profile viewers. No message.
- 2Day 1: LinkedIn invitation
No note, or a very short one. According to LinkedIn Help, free accounts can add a note to a limited number of invitations per month, and each note is capped at 200 characters.
- 3Condition: invitation accepted (checked for up to 7 days)
Yes → LinkedIn message 1. No → “has email” condition.
- 4Yes branch: message 1, then message 2 on day 4
The first message thanks them and asks one question; the second brings something useful (an example, a figure from your own work, a resource).
- 5No branch: has email?
Yes → a short email asking the same question. No → end. Note: a LinkedIn search does not give you email addresses; this branch only helps if you got the address another way (CSV import, previous exchange).
Sequence 2: local businesses from Google Maps, email then WhatsApp
For: local businesses (clinics, agencies, restaurants, hotels) found on Google Maps, with a business email and phone. WhatsApp only comes as a follow-up, never first.
- 1Day 0: email 1
One specific observation about the business (its listing, reviews or website) and one question. No attachment.
- 2Condition: email opened (checked for up to 3 days)
Yes → “has phone” condition. No → email 2.
- 3Opened branch: has phone?
Yes → a short WhatsApp message that refers to the email. No → email 2.
- 4Email 2 (day 4)
New subject, different angle: a concrete example or a simple offer (a free ten-minute audit, for instance).
- 5Day 5: breakup email
A short note saying you won’t keep writing, leaving the door open.
A word on opens: they are a signal, not proof. Apple says Mail Privacy Protection downloads remote content privately in the background when a message arrives, which stops senders from learning when it is viewed. Write your WhatsApp follow-up so it still makes sense if the email was never really read.
Sequence 3: warm follow-up after an event or webinar
For: people you met at a trade show, webinar registrants, conference attendees. You have real common ground, so use it in the first line.
- 1Day 0: LinkedIn invitation with a note
The note mentions the event. This is where a personal note makes the most sense.
- 2Condition: invitation accepted (checked for up to 5 days)
Yes → LinkedIn message with the promised resource. No → “has email” condition.
- 3Day 3: condition “replied” (checked for up to 3 days)
No → LinkedIn message 2 offering a fifteen-minute call. If they reply, the sequence stops on its own.
- 4Not-accepted branch: has email?
Yes → recap email with the resource. No → end.
Sequence 4: recruiting, companies that are hiring
For: recruitment and staffing firms targeting companies with open jobs, then the person who hires (HR lead, founder, hiring manager).
- 1Day 0: profile visit
On the decision maker’s profile, not just the company page.
- 2Day 1: LinkedIn invitation
No note, or a note that mentions the open role.
- 3Condition: invitation accepted (checked for up to 7 days)
Yes → message 1 about the role. No → “has email” condition, then email, otherwise end.
- 4Day 5: message 2
Something useful: a type of candidate you have available, or a hiring timeline you see in your own work.
- 5Day 7: breakup message
Short, no guilt, door open for future hires.
Sequence 5: re-engage old contacts
For: past prospects, quotes that went quiet, contacts imported from a CSV. These people already know you, so WhatsApp is perfectly legitimate here.
- 1Day 0: “what’s new” email
What has changed on your side since you last spoke, and one simple question.
- 2Condition: email opened (checked for up to 4 days)
Yes → “has phone” condition. No → profile visit, then LinkedIn invitation.
- 3Opened branch: has phone?
Yes → a short, personal WhatsApp message. No → email 2 on day 4.
- 4Not-opened branch: LinkedIn
Invitation, then “invitation accepted” condition (7 days) and a LinkedIn message repeating the question.
Rules that apply to every sequence
- Three to five touches is enough. Beyond that you damage your reputation more than you gain replies.
- One message, one question. The prospect should be able to answer in one line.
- Space out channels. Don’t fire email, LinkedIn and WhatsApp on the same day.
- Respect caps. Send during business hours, at reasonable daily volumes, with a gradual ramp-up for new accounts. Our article on LinkedIn invitation limits covers this in detail.
- Give a way out. The last message says clearly that you are stopping. Remove anyone who asks, immediately.
Building these sequences in Yalors
All five sequences can be built as-is in Yalors’ visual multichannel prospecting builder: profile visit, invitation, wait, conditions (invitation accepted, replied, email opened, has email, has phone), LinkedIn, WhatsApp and email messages. Variables with fallbacks, spintax and A/B variants work on every message, and the sequence stops as soon as a prospect replies. By default each account is capped at 15 LinkedIn invitations and 50 messages a day, with a 14-day ramp-up for new accounts.
For the wording itself, use our cold message templates, and check your email setup with our guide to cold email deliverability.