Automation should stop at the moment the interaction changes from scheduled outreach to a real conversation. A recipient reply is not another campaign event to send through.
The reply-to-stop workflow
- The connected mailbox receives an inbound message.
- Synchronization associates it with the correct thread, contact, and campaign enrollment where possible.
- The enrollment records the reply and cancels remaining scheduled follow-up.
- The thread appears in the unified inbox under its owning mailbox.
- An operator sets a disposition, assigns, tags, and answers the conversation.
- The reply disposition contributes to campaign and step analysis.
Why the stop must happen before sending
A follow-up may already be queued when the reply arrives. Checking only when a delay expires is not enough; the outbound preparation path should re-evaluate reply and suppression state before it sends.
The same principle applies to unsubscribe, complaint, hard bounce, manual suppression, and block-list changes. Eligibility can change after enrollment.
Stop the right thing
| Signal | Minimum action | Possible broader action |
|---|---|---|
| Associated reply | Stop that enrollment's pending follow-ups | Operator may update the contact or opportunity state |
| Unsubscribe or explicit stop request | Suppress the recipient | Apply the requested scope across relevant campaigns/workspaces |
| Hard bounce | Suppress the failed address | Audit the audience source when failures form a pattern |
| Complaint | Suppress the recipient | Pause and investigate the affected audience or campaign |
| Mailbox loses readiness | Remove it from sender eligibility | Pause the campaign if no eligible sender remains |
Edge cases to review
- Replies from an alternate address or forwarded conversation.
- Automatic replies and out-of-office messages.
- Replies arriving during synchronization delay.
- Multiple campaigns involving the same contact.
- Manual sends or replies made outside MailSequence.
- Shared inboxes where ownership or assignment changes.
These cases require explicit product behavior and operator review. Do not invent a universal classification rule where the inbound evidence is ambiguous.
MailSequence behavior
MailSequence synchronizes replies from connected business inboxes, associates them with campaign activity, stops remaining follow-up for the relevant enrollment, and keeps the thread replyable from its owning inbox. Operators can search, filter, assign, tag, set a reply disposition, and respond without merging mailbox identities.
Reply stopping and unsubscribe need separate actions
A normal reply stops the active sequence; an unsubscribe or explicit stop request should also create the appropriate suppression so future campaigns cannot restart outreach accidentally. Applicable marketing and subscription mail may additionally require one-click unsubscribe headers defined by RFC 8058 and mailbox-provider rules.
Sources and product basis
- Google: Email sender guidelines
Recipient expectation, truthful identity, unsubscribe, and complaint requirements. - IETF RFC 8058: One-click unsubscribe
Standard mechanism for one-click list-email unsubscribe headers. - MailSequence unified inbox
Product behavior for reply synchronization, thread ownership, assignment, tags, disposition, and reply-aware stopping.