This guide assumes automated email sequences is already deployed and passing. It covers what breaks at scale and how mature teams operate it.
Edge cases that break a working setup#
- Continuing after a negative reply.
- Identical cadence for every contact regardless of engagement.
- Mail forwarded through mailing lists or personal forwarders, which alters headers and content.
- Acquisitions and rebrands that introduce domains nobody audited.
- Vendors silently changing their sending infrastructure.
Operating it as infrastructure#
- Assign an owner for each sending domain and each vendor relationship.
- Put DNS records under version control or a change-review process.
- Alert on authentication pass rate drops and reputation changes, not just outages.
- Run a quarterly audit against the setup steps below.
- Document runbooks for the three most common failures.
Reference: the baseline setup#
- Plan 3 to 5 steps over 2 to 3 weeks; diminishing returns set in after step 5.
- Give each step a distinct angle rather than 'just bumping this'.
- Stop the sequence automatically on reply, bounce, or unsubscribe.
- Thread follow-ups as replies for context, but vary subject lines when starting new angles.
- Review reply sentiment weekly and adjust.
Frequently asked questions#
How many follow-ups should a cold sequence have?
Three to five. Most positive replies come by step three; beyond five, complaints rise.