Handling a spam complaint, end to end

The flow, stage by stage#

1. Trigger — a recipient marks a message as spam in their own mail client.
2. External event — their provider notifies the sending side; this arrives as a signed notification, not as an email.
3. Authentication and workspace resolution — the notification is matched to the mailbox that sent the message, and the mailbox is what names the workspace.
4. Ingest — the notification is normalised: which address complained, about which message.
5. Canonical record — a suppression is written for that recipient with complaint as its origin and the time it happened.
6. Classification and reasoning — a complaint is not a bounce and is not an unsubscribe; treating them alike loses the distinction that makes each one actionable.
7. Knowledge, memory and rules — the person's record gains the entry, so anyone opening the relationship sees it before writing.
8. Autonomy and approval — no bearing. The suppression applies to an autonomous workspace exactly as to a supervised one.
9. Action through a provider — none outbound. Nothing is sent in response to a complaint, and nothing apologises for one.
10. Result — every subsequent outreach to that address is refused, with the origin named in the refusal.
11. Relationship, timeline and memory — the complaint is part of the person's history, which is what stops a colleague re-adding them to a list next quarter.
12. Audit, usage and Needs You — the entry and every refusal it causes are recorded as decisions.

What a complaint is, and what it is not#

Keeping them apart is what makes any of them useful. A workspace with many unsubscribes has an audience problem; a workspace with many complaints has a relevance or a consent problem, and those need different corrections. Collapsing all three into one list produces a number that cannot be acted on.

The sender-side change#

The suppression protects one person. What protects the mailbox is what happens next, because complaints are read by receiving providers as a statement about the sender rather than about a single message. A pattern of them affects whether later mail — including ordinary replies to customers — reaches an inbox at all.

• Look at what was sent, not only at who complained. One complaint is noise; several against one campaign is a message about the campaign.
• Check consent evidence before the next outreach run. Prospecting keeps evidence for contactability, and a complaint is a reason to re-read it rather than to send harder.
• Reduce volume before improving wording. Sending less to a better-qualified list moves the number that matters; rewriting a subject line rarely does.
• Never respond to a complaint with a message. The recipient has already said what they wanted, and an apology sent to a suppressed address is the exact behaviour that generated the complaint.

Failure modes#

The complaint cannot be matched to a person

The address is suppressed regardless. Compliance works on the address; the relationship link is a convenience, not a precondition.

The complaint arrives after the sequence finished

The suppression still stands and still refuses future outreach. Nothing is retroactive, and nothing already delivered can be recalled.

A colleague re-imports the address

The suppression is read at the send gate rather than at import, so the entry still refuses. The import is not the protection.

Complaints keep arriving from one campaign

Stop the campaign. Each further message is another recipient's chance to report the sender rather than the message.

What a person should actually do#

1. Open the person's record and read the entry with its origin.

   Result You know whether this was a complaint, an unsubscribe or a bounce, which decides everything that follows.

2. Leave the suppression alone.

   Result The recipient stops hearing from the workspace, which is what they asked for and is also what protects the mailbox.

3. Look at the other recipients of the same run.

   Result You find out whether this is one person's preference or a batch that should not have been sent.

4. Record what you learned as a standing instruction if it should change future outreach.

   Result The lesson survives the campaign, rather than living in one person's memory of a bad week.

Questions#

Related#

• Spam complaints
• Deliverability
• Applying a suppression, end to end
• Handling a bounce, end to end
• The compliance check before outreach