A cold email opt-out is a promise: this person will not hear from you again. That promise is easy to break later, when a second mailbox, a new campaign or a CRM sync brings the same address back.
This guide covers what counts as an opt-out, how quickly to act, how to keep one suppression list across everything you send from, and where suppressed contacts tend to re-enter. It ends with a list an approver can use before anything goes out. For a short definition of the term, see the suppression list glossary entry.
This is operational guidance, not legal advice. Rules differ by where your recipients are and by how you contact them. Ask a lawyer about your own situation.
Who this is for
This guide is for the people who run or approve outbound email:
- A founder or sales lead sending from one or two mailboxes who has so far handled opt-outs by hand.
- An operations or RevOps person who owns the sending stack and the CRM, and has to keep them in agreement.
- An approver who signs off on campaigns and wants to know what to look for before saying yes.
If you send from several mailboxes or domains, or from more than one tool, the sections on one list and on re-entry matter most to you.
Why B2B email is not exempt
Some teams assume that opt-out rules apply to consumer email only. The FTC's CAN-SPAM guide says otherwise: "The law makes no exception for business-to-business email." [[1]](#sources)
Other regimes treat business recipients differently. The UK's ICO says of its PECR guidance: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[2]](#sources) That is a statement about corporate bodies. Even where email to a company is allowed, stopping when someone asks you to is sound practice.
Under GDPR, one lawful basis for processing is "necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[3]](#sources) In practice, stop sending once someone has said no, whatever basis you rely on.
Whatever your legal position, the practical rule is the same. Treat every opt-out as final, in every channel you use.
What counts as an opt-out
Define this before you send, in writing, so that nobody decides case by case at 6 p.m. on a Friday. Four kinds of signal arrive in practice.
The unsubscribe link or button. This is the clearest case. Google's sender guidelines say: "Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body." [[4]](#sources) RFC 8058 "describes a method for signaling a one-click function for the List-Unsubscribe email header field." [[5]](#sources) Whatever tool sends your mail, check that both the visible link and the header work, and that a click leads to suppression.
A plain-language reply. "Remove me", "stop", "not interested, please don't email again" and "take me off your list" are opt-outs. Do not wait for the person to use a link. A reply that asks you to stop is a request to stop, and it is worth honoring the same way a click is.
An angry reply. "Never email me again", a swear word, a threat to report you. Suppress first and answer second, if you answer at all. Do not argue and do not send a "sorry to see you go" sequel that adds one more message to the inbox of someone who is already annoyed.
A reply that is not an opt-out. "Not now, try next quarter" and "wrong person, talk to our head of ops" are different. The first is a deferral and the second is a redirect. Neither is a request to stop contact for good. Record them, but do not put them on the suppression list unless your written definition says so. Be strict about the line: if the wording is ambiguous, ask a person to read it rather than guessing in either direction.
A reply also stops a sequence in some tools. On LinkedIn, for example, a reply stops that lead's emails. [[6]](#sources) Stopping a sequence is not the same as suppressing a contact. Keep the two separate: a suppression entry should apply to every campaign, not only the one that was running.
How quickly to act
Yahoo's sender best practices say: "Honor unsubscribes within 2 days". [[7]](#sources) Treat that as the outer limit, not the target. The better target is that no further email goes out once the opt-out has been seen.
The delay between "the person opted out" and "the list knows about it" is made of several smaller delays:
- The time for the sending tool to record the event.
- The time for that event to reach your own system or CRM.
- The time until the next scheduled send that checks the list.
Smartlead, for instance, sends sent, reply, bounce, unsubscribe and category-change events back to Outlevo by webhook. [[8]](#sources) That includes unsubscribe events. Opt-outs that arrive another way, such as a note a rep types into a CRM, depend on how that CRM talks to your sending tool. Count a gap like that when you decide how fast you really act.
Replies need a person. Someone must read them, classify them and suppress the contact. Give that job an owner and a daily time slot, and write down who covers when the owner is away.
Steps
1. Write the opt-out definition
Put the four kinds of signal above in a short document. Say which ones suppress, which ones do not, and who decides the ambiguous cases. Keep it to a page.
2. Choose one list and one owner
There should be one suppression list for the workspace, not one per tool, mailbox or campaign. One person owns it. That person approves changes, reviews additions weekly and is the only one who can remove an address.
Removal deserves a rule of its own. A contact should leave the list only if they ask to be contacted again, in writing, and you keep that message.
3. Store the address, and the domain when it applies
Suppress the exact email address every time. Add the domain only when the person says so, for example "none of us want these emails", or when your own policy treats a company-wide objection that way. Suppressing a whole domain on one person's word may be too broad. Suppressing only the address may leave you emailing their colleague with the same message. Write down which rule you use.
Also record the reason and the date: link click, reply, forwarded complaint, manual add. Without this, nobody can later tell whether an old entry is safe to review.
4. Make the list span every mailbox, domain and campaign
Sending capacity grows by adding mailboxes and domains. Builder includes 1 domain and 2 mailboxes, and Growth includes 2 domains and 4 mailboxes. [[9]](#sources) Each added mailbox is another place where an opt-out can be recorded but not seen by the others.
The test is simple. If a contact opts out through the link in mailbox A, can mailbox B, on a different domain and in a different campaign, send to them tomorrow? If the answer is yes or "I am not sure", you do not have one list.
New domains need warming before they send. The domain warm-up guide covers that. Do the suppression check at the same time. A freshly warmed domain with an empty local list is the easiest way to email someone who already said no.
5. Close the re-entry routes
An opt-out can be recorded correctly and the address can still come back through a side door. The next section lists the common ones.
6. Put the rule where the approver can see it
An approver cannot check what is not written down. The section on the approver check below shows what to look for.
7. Test before the real send
Send a test opt-out through each path you support: link click, reply, manual add. Then check that the address cannot be queued in a new campaign from a different mailbox. If you build your own opt-out sync through the API, test keys act on a sandbox with 100 fake companies, so you can build without sending anything or spending credits. [[10]](#sources)
Where suppressed contacts come back
Imports
A CSV import can bring in up to 200,000 rows of companies and deals. [[11]](#sources) A file that size can include companies you have already suppressed, especially if you suppress by domain. Ask, before any import goes into a live campaign: is the file checked against the suppression list, and who checked it? If the answer is that the sending tool will deal with it, confirm that in the tool rather than assuming.
CRM syncs
An optional HubSpot contact import brings in email, name, job title and email opt-out, but only after an admin turns contact import on with a stated purpose. [[12]](#sources) That opt-out field is useful. It also means opt-outs recorded in HubSpot and opt-outs recorded in your sending tool are two lists unless you reconcile them.
On the write side, Outlevo writes to HubSpot only in properties it owns and never edits standard HubSpot fields. It writes nothing until an owner or admin approves the field mapping. [[12]](#sources) This means your own standard fields stay yours. If you keep an opt-out flag in a standard field, a person on your team still has to keep it in step with the suppression list.
Manual one-to-one email
A rep who emails someone from their inbox sits outside every campaign rule. Outlevo's Gmail extension includes a recipient guard that warns before you email a contact Outlevo should not reach. [[13]](#sources) Make it part of the rep's routine, and tell reps that a warning is a reason to stop, not to click through.
Other channels
An opt-out on email is an opt-out on LinkedIn too, unless the person said otherwise. Keep the list shared across channels. A person who asked you to stop emailing should not receive a connection invitation the following week.
Downstream tools
If you forward events to other systems, remember that delivery is not instant. Outlevo webhooks cover contact, lead and campaign events. Each delivery is signed and retried for up to 12 hours. [[14]](#sources) A downstream system can be behind the source by that much when something fails. Delivered events cost 1 credit each. [[14]](#sources) Plan for both when you decide what to forward.
Verification and enrichment
Adding new data for a contact you already suppressed does not make them contactable. A verified address, a new job title or a fresh signal changes nothing about their opt-out. If you use an email verification tool, compare email verification tools before choosing one, and keep verification and suppression as separate lists. A "valid" result means the mailbox exists, not that the person wants to hear from you. Deliverability tooling is covered in email deliverability tools.
What to check
Use this list before you approve a campaign. Outlevo sends nothing outside a policy that a person approved, and policies set who can be contacted, on which channels, how often and with what budget. [[15]](#sources) That gives the approver a single place to read the rules before anything goes out.
In the policy:
- Under who can be contacted, does the policy say that suppressed contacts are excluded? If it does not say so, ask before approving.
- Are all channels in the campaign listed, and does the exclusion apply to each of them?
- Is the contact frequency stated, so that a follow-up sequence cannot outrun an opt-out?
In the setup:
- Is there one suppression list, with a named owner?
- Do all mailboxes and domains in the campaign read from it?
- Does every email carry a visible unsubscribe link and a working one-click header? [[4]](#sources) [[5]](#sources)
- Is someone assigned to read and classify replies daily?
In the data:
- Was the contact file checked against the suppression list before it was loaded?
- Was any CRM contact import turned on with a stated purpose, and does it bring the CRM's opt-out field with it? [[12]](#sources)
- Do manual senders use the Gmail extension, so the recipient guard warns them before they email a contact Outlevo should not reach? [[13]](#sources)
After approval:
- Every external action is checked against the approved policy before it runs, and recorded in a ledger. [[15]](#sources) Use the ledger to confirm after the first send that no suppressed address was contacted.
- Know where the kill switches are. Kill switches pause a campaign, a channel or the whole workspace at once. [[15]](#sources) If you find that a suppressed contact was emailed, pause first and investigate second.
The public API has resources named suppressions, compliance, policies, imports, contacts and mailboxes among its 227 paths. [[16]](#sources) If your team prefers to audit with code, those are the resources to read. The developer hub has the reference.
When a suppressed contact is emailed anyway
It will happen once in a while. Handle it in this order:
- Pause the campaign or channel involved.
- Confirm the address is on the list and find out why the send went out: import, sync, a second mailbox, or a manual email.
- Fix the route, not just the entry. Adding the address again without closing the route means the same fault will recur.
- If the person complained or replied, answer briefly, confirm they are suppressed and do not ask for anything.
- Note the incident, the cause and the fix in the same place as your opt-out definition.
Next step
Take your current campaigns and run the cross-mailbox test: opt out a test address in one mailbox and see whether every other mailbox and campaign rejects it. Then read the "who can be contacted" part of your policy and check that suppressed contacts are named as excluded. Fix whichever of these fails first.
To understand how policy approval and the ledger work together, read how Outlevo works. To connect your sending tool, see the Smartlead integration.
Sources
- FTC: CAN-SPAM Act compliance guide for business
- ICO: Electronic mail marketing (PECR)
- GDPR Article 6(1)(f): lawfulness of processing
- Google: Email sender guidelines
- RFC 8058: Signaling One-Click Functionality for List Email Headers
- LinkedIn integration
- Yahoo: Sender best practices
- Smartlead integration
- Managed mailboxes integration
- REST API and SDK integration
- CSV and Excel integration
- HubSpot integration
- Gmail extension integration
- Webhooks integration
- How Outlevo works
- Outlevo API reference