When to stop following up (and why it matters)

Persistence is a virtue in outbound right up to the point where it becomes the thing that gets you blocked.

A sequence with no end is not persistence

It is nagging, and it is also unmanageable. Decide the number of touches before you start, and let the sequence finish. Contacts who did not respond go into a finished state rather than an indefinite loop.

How many follow-ups, and over how long

Most working sequences land between three and five touches spread across two to four weeks. Fewer than three leaves replies on the table, because a large share of positive answers arrive after the first message rather than from it. More than six starts producing complaints faster than it produces meetings.

Spacing matters as much as the count. Two to four working days between the first touches, then widening to a week for the last one, gives the message room to land during a normal working period without stacking up in the same inbox view. A sequence that fires five emails inside eight days reads as software regardless of how the copy is written.

Set the endpoint before the campaign launches and treat it as fixed. The temptation to add "one more" always arrives on the day the numbers look thin, which is exactly the wrong moment to make that decision. The structure behind the touches is covered in the follow-up sequence that does the work.

Signals to stop earlier than planned

The planned endpoint is a ceiling, not a target. Several signals justify stopping before you reach it.

• An explicit no. Ends the sequence immediately, whether or not the person used the word unsubscribe.
• A hard bounce. The address is dead. Continuing to send at it damages the domain and reaches nobody.
• An auto-reply saying the person has left. Stop, and use the named replacement if one is given.
• A wrong-fit reply. If they tell you they do not do the thing you assumed they do, the targeting was wrong. Fix the list rather than continuing the sequence.
• A forward to someone else. The original contact's sequence ends there. Continuing to chase both looks disorganised.
• Any hint of irritation. Not a legal obligation, but the cost of one more email is a complaint and the upside is close to zero.

Reading these correctly is the same skill as answering a not-interested reply: separating a soft no from a hard one, and responding to each on its own terms.

The one absolute rule

If someone asks not to be contacted, that request is honoured immediately, permanently, and without a final "just checking" message.

This is not a judgement call. Under European rules an objection has to be respected, and the contact should be recorded so no future campaign picks them up again.

Keep a do-not-contact record

The practical mechanism is a list that every future campaign is checked against. Without it, the same person gets contacted again in six months by a different sequence, which is worse than the original message and entirely avoidable.

Silence is not the same as objection

Worth separating the two. Someone who never replied has not refused, so finishing your planned sequence is reasonable. Someone who said no has refused, and that ends it. Treating both the same way means either giving up too early or pushing too far.

Why this protects you

Complaints damage sender reputation more than almost anything else, and they follow the domain rather than the campaign. Clean stopping rules are part of deliverability, not a separate compliance chore.

Should the last email be a break-up?

The closing message is worth writing properly, because it consistently pulls replies that the previous four did not. Keep it short, state that this is the last message, and remove the pressure rather than adding it. Two lines is enough: the reason you got in touch, and an offer to close the file unless they say otherwise.

Avoid the manipulative variants. Fake resignation, guilt, or a subject line implying a prior agreement all generate replies, and the replies are annoyed ones. A plain, honest sign-off is covered in the break-up email, and it is the version that leaves the door open for a future campaign.

Stopping is not the same as deleting

A finished sequence produces three groups, and they need three different treatments.

1. Objected. Onto the suppression list, permanently, never re-entered by any campaign.
2. Not now. Given a date and a reason to return, then worked as nurture rather than outbound.
3. Silent. Parked, and eligible for a fresh approach later if something has genuinely changed.

The third group is where teams either waste an asset or abuse it. A silent contact is not a refusal, so re-approaching in six to twelve months is reasonable provided something is different: a new angle, a new trigger event, a new offer, or a change at their end. Rerunning the identical sequence into the same list next quarter is not persistence, it is the same email arriving twice, and it earns complaints. Doing it properly is the subject of reactivating cold leads.

Common mistakes at the end of a sequence

• No defined endpoint. The sequence runs until somebody notices. Fix: decide the touch count before launch and let the tool enforce it.
• Treating a soft no as an objection. "Not this quarter" is a date, not a door closing. Fix: park it with a follow-up date instead of suppressing it.
• Treating an objection as a soft no. Far more expensive. Fix: any request to stop goes to suppression immediately, without interpretation.
• Judging a sequence on the first email alone. Fix: measure across the whole sequence, using your own response rate data rather than a published average.
• Adding touches when results disappoint. Fix: fix the list or the offer. Volume against the wrong audience only accelerates the damage.
• Re-entering the same contacts across campaigns. Fix: exclude anyone who finished a sequence in the last six months from new lists by default.

Where the line sits in Europe

Across the markets we run campaigns in, the tolerance for persistence varies more than most teams expect. German recipients tend to respond to a fourth or fifth touch by objecting formally rather than ignoring it, and German law backs them up, so a shorter, cleaner sequence with impeccable sender identification performs better there. Nordic recipients just stop reading. In the Baltics and Poland, where professional networks are small enough that people recognise names, an over-persistent sequence costs you standing with prospects you have not contacted yet.

What does not vary is the legal floor. An objection is honoured everywhere in the EU, immediately, and the queued touches in an already-running sequence are not an excuse. Build the suppression check into the send step and the question stops arising.

Not now is not never

A polite "not right now" deserves a date rather than deletion. That is a different state from both silence and refusal, and it is often where future pipeline comes from.