Treat every reply as an immediate sequence stop, then classify it. Maintain a durable global suppression ledger for opt-outs, hard bounces, and complaints. Authenticate events, expect duplicates and reordering, and reconcile webhook state against the mailbox or provider.
Make the recipient state machine explicit
| Signal | Immediate action | Later interpretation |
|---|---|---|
| Any human reply | Stop the active automated sequence | Interested, not now, referral, objection, opt-out, out-of-office, ambiguous |
| Hard bounce | Suppress the address | Review source and domain-level pattern |
| Soft bounce or deferral | Hold or retry under bounded policy | Classify cause and adjust destination rate |
| Spam complaint | Suppress globally and alert | Investigate audience, identity, copy, and source |
| Unsubscribe | Suppress globally | Record mechanism, scope, time, and evidence |
| Provider block | Pause the affected route or campaign | Diagnose before resuming |
Stop first, classify second
A model may take seconds to classify a reply or may be unavailable. The next scheduled follow-up should not depend on that inference. When an inbound message matches a campaign recipient, set a deterministic sequence stop immediately. Classification can then route it to sales, support, a referral flow, or suppression.
Automatic out-of-office replies are the main nuance. Even there, the safer default is to hold the sequence until the system confidently identifies the response and an approved policy decides whether a later resume is appropriate.
Design for imperfect events
- Authenticate webhooks and reject stale or invalid signatures.
- Use provider event IDs plus your own stable message and recipient IDs.
- Assume events can arrive twice, late, or out of order.
- Persist the raw event before applying derived state.
- Make suppression monotonic unless an accountable person explicitly reverses it.
- Reconcile periodically against the provider API or inbound mailbox.
- Alert when event delivery or inbound polling becomes stale.
Unsubscribe is a product surface, not footer decoration
The visible link, reply-based request, one-click header, manual operator action, complaint event, and imported suppression should converge on the same durable state. The recipient should not have to log in, explain a reason, or repeat the request for another campaign.
The FTC requires a clear opt-out method for U.S. commercial mail and honoring requests within ten business days; a responsible system should stop automated mail much faster. RFC 8058 defines the technical signaling commonly used for one-click list unsubscribe. [1][2]
Test the race you hope never happens
Schedule a follow-up, then inject a reply immediately before the worker claims the message. The send path should recheck suppression after claiming and before submission. Repeat with a duplicate complaint, delayed webhook, address reimport, campaign clone, and worker restart.
If any test produces another automated message after a stop signal, the problem is not the classifier. It is missing transaction and reconciliation design.
Common questions
Questions, answered plainly
Should every reply stop a sequence?
Yes by default. Stop immediately, then classify the reply and apply an approved policy for any exceptional resume.
What is global suppression?
A durable rule preventing a recipient from being reactivated by another campaign, list import, retry, or workspace workflow within the required scope.
Are unsubscribe and complaint events the same?
Both should prevent future sends, but preserve them as distinct event types because their operational causes and reporting implications differ.
Evidence
Sources and methodology
Product capabilities were checked against first-party documentation available on September 9, 2026. Policies, plans, and prices can change; verify them before buying. General guidance is educational and is not legal advice.
- CAN-SPAM Act: A Compliance Guide for Business U.S. Federal Trade Commission. Official U.S. guidance for commercial email, including B2B messages.
- RFC 8058: Signaling One-Click Functionality for List Email Headers RFC Editor. Technical standard for one-click list unsubscribe signaling.
- Email sender guidelines Google. Authentication, DNS, spam-rate, formatting, unsubscribe, and volume guidance for Gmail.
Your agent can do the thinking.
The infrastructure still needs a grown-up.