By Ryan Richardson · Published 8 October 2026
A buyer replies to an email, has an exchange, and then receives a follow-up message from the same sequence a day or two later as though the conversation never happened.
A sequence engine that only checks whether a scheduled message has been sent, not whether the recipient has since engaged in a real reply, has no way to stop itself once a human conversation has actually started. The queued messages behind the reply keep firing on schedule, oblivious to the fact that their job has already been done by a person. Triggered, automated follow-up beats broadcast email by a wide margin in general, partly from a selection effect (triggered messages go to people who just took an action, broadcasts go to everyone), but that advantage disappears the moment a triggered sequence ignores a reply.
One rule sits above every automated chain: a reply from a real person stops everything queued behind it, across every sequence a buyer is in, not just the one that triggered the reply. Test this directly before any sequence ships: reply from a buyer address partway through, and confirm the next scheduled message fails to arrive.
Reply to one of your own automated sequences mid-flow, from a real test address, and watch what happens to the next scheduled message. If it still arrives, your sequence engine is tracking sent-or-not rather than replied-or-not, and every buyer who ever replies early is getting this exact experience.
| Claim | Value | Source |
|---|---|---|
| The specific sequence failure and its cause | a sequence fired at a reader two days after he'd already replied to an earlier message, because the system only tracked sent or not sent | THE BOOK FULL.md Piece 17, line 1804 |
| Why triggered follow-up beats broadcast email generally | partly a selection effect: triggered messages go to people who just bought something, broadcasts go to everyone | THE BOOK FULL.md Piece 16, line 1802 |