Every sequence needs an ending

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.

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.

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.