Multichannel cadences: what separates spam from prospecting

A multichannel cadence is a sequence of touches across email, LinkedIn and phone, planned before the first send, where every touch has a reason, a set gap and an exit rule. What separates it from spam isn't the channel or the tool. It's that every message adds something new, reaches the right person at a moment that makes sense and stops when it has to stop.

What a multichannel cadence is

A multichannel cadence is the complete plan for how you're going to contact a specific profile: how many touches, through which channel, with how much time between them, what each one says and what happens when someone replies or doesn't.

Sending the same message by email, LinkedIn and phone in the same week isn't a multichannel cadence. It's just noise, repeated. What makes a cadence work is the sequence, the spacing and the reason behind each message. Each channel has a different job:

• Email carries the context. It's where your argument has room, and it's what gets forwarded internally.
• LinkedIn builds familiarity. A connection with no sales pitch, or an interaction with what they post: when the email arrives, your name won't be new.
• The call resolves in real time. It's for checking whether the problem exists, clearing up an objection or reaching whoever owns the topic.

All of this has a precondition: the list. If you write to the wrong account, or to the role that doesn't suffer the problem, no sequence fixes it. How to choose and order those accounts is covered in ABM for small teams.

Every touch needs a reason

Every touch has to add something the last one didn't. If it doesn't, it's an empty reminder and it should go.

"Just wanted to make sure you saw my email" is the classic example: it gives no new reason to reply. Write the cadence as a conversation in which each message changes angle.

An example cadence, to illustrate the structure and not as a recipe: six touches over about three weeks.

1. Email. The situation the recipient recognises, what it costs them and a question. No company introduction.
2. LinkedIn. A connection with no pitch, or an interaction with something they have posted.
3. Email. Another angle on the same problem: how another role in their company experiences it, or what usually happens if it carries on.
4. Call. Short, to check whether the problem exists, not to do the demo.
5. Email. Something useful even if they don't reply: a guide, a checklist, a comparison.
6. Break-up email. An explicit way out: if it's not a priority, you'll leave it there and only come back if there's a reason.

The number and order of touches change with the profile. The rule that each one needs a reason doesn't.

Spacing matters as much as content

The time between touches decides whether the cadence reads as interest or as pressure.

Three touches in three days feel like pressure. The same three touches spread over two weeks feel like genuine interest. Three rules:

• Don't stack channels on the same day. An email, a LinkedIn invitation and a call in the same morning read as harassment.
• Widen the gaps as it progresses. The first touches can be closer together; the last ones, further apart.
• Let a signal change the pace. If the account moves mid-cadence, bring a touch forward; if someone says "not now", the cadence stops.

Personalise by profile and by signal, not by name

Real personalisation means changing the argument according to the recipient's role and the reason for the contact; putting the company's name in the first line isn't personalisation.

By profile

The person who pays, the person who uses it and the person who implements it don't buy for the same reason. Write one version per profile: what is happening to them today, what it costs them, what they gain and what risk they take on by saying yes. Start with the situation they recognise, leave what you do for the end and use your customers' words, not the industry's.

That's how we did it in the After case: four campaigns in Lemlist, one per role, because the Office Manager who organises team activities and the CRO who needs to keep their own team's energy up don't respond to the same message.

By signal

The signal (a new person in the buying role, a hire that gives a project away, a regulatory change) justifies the timing and suggests the problem. You don't need to mention it: "I saw that..." sounds like surveillance. It's enough to talk about the problem that signal makes likely.

A fixed version so you can measure

If the message changes depending on who writes it, you'll never know which one works. Lock one canonical version per profile for a set period and change one variable at a time. AI helps with drafts and with classifying accounts, but a person reviews everything that goes out.

Deliverability comes before the message

If the email doesn't reach the inbox, it doesn't matter how good it is: the sending infrastructure is the first condition of any cadence.

The basics:

• Never prospect from your primary domain. Invoices and contracts go through it. Use secondary domains with their own sending history.
• Authenticate every domain. SPF, DKIM and DMARC configured and aligned.
• Warm up the mailboxes before using them. A newly created mailbox that starts by sending cold raises suspicion.
• Be disciplined about volume. Stay below the point where your sends look like bulk mail, spread them across mailboxes and rotate them. If you need more volume, you need more infrastructure, not more sends per mailbox.
• Verify the addresses before every campaign and remove bounced addresses straight away.
• Offer an easy unsubscribe in every send and honour it centrally, across all campaigns.
• Check where it lands with test mailboxes, and separate two questions: whether the message arrives and whether it persuades. Mixing them up leads to rewriting the copy when the problem was delivery.

And one thing to settle first if you prospect in Spain: the LSSI (Spain's Information Society Services Act) restricts unsolicited commercial email, and it doesn't distinguish between individuals and businesses. Decide which recipients you work by email and which only through other channels, store the address type as a field in the CRM and check the policy with your lawyers before building the sequence.

Exit rules: what separates prospecting from spam

A cadence with no exit criterion keeps writing to people who have already said no, and that's what turns it into spam in the recipient's eyes.

What to do with each reply

• Any reply stops the cadence. From then on a person answers, not the sequence.
• "Not interested": out, with no last attempt.
• "Not now": out, with a re-entry date noted on the account.
• "I'm not the right person": thank them, and move on to the person they pointed you to.
• Unsubscribe: onto an exclusion list shared by all campaigns.
• No reply by the end: the account goes back to the universe with a re-entry date, not onto tomorrow's list as if it were new.

The handoff to sales and the CRM

When someone shows interest, qualify the reply against the criteria you've agreed with sales and get it to them the same day. A reply that sits for days in an inbox nobody checks is a lost conversation. It goes into the CRM with its context: the source, the signal that prompted the contact, the cadence and the touch that got the reply.

Put like that, the difference is easy to see. Prospecting writes to people who have a reason to listen, says why, brings something in every message and steps back when asked. Spam writes to everyone, repeats the same thing and doesn't stop.

Iterate on what opens conversations, not on replies

Iterating a cadence means measuring which message moves the conversation forward and changing a single variable at a time.

The message that produces a polite "it's not the right time" isn't the same as the one that opens a conversation with the decision-maker. Measure the second, and record which touch each reply came from: with few contacts, counts read better than percentages. If you change the subject line, the segment and the copy at the same time, the result tells you nothing.

Where to start

Start with the list and the infrastructure, not the copy:

1. Review the list: accounts that fit, the right role and a reason to write now.
2. Set up secondary domains, authenticate them and warm up the mailboxes.
3. Write one cadence per profile, with the purpose of each touch.
4. Define the exit rules and the handoff to the CRM before sending anything.
5. Launch on a few accounts, read the results and change one thing only.

Designing all of this in your own stack is part of the Outbound System. If you'd rather we run it, the Fractional Lead Generation Agency does it from our infrastructure and the Fractional GTM Engineer from yours. Neither guarantees a number of meetings: at those two levels we set an objective and review it every month with the data in front of us.