Guides

Outbound exclusion rules: who you must never email

A checklist for the exclusion section of an outbound policy: customers, open deals, recent losses, competitors, partners and opt-outs.

An outbound mistake does not have to be bad copy. A good email can still go to the wrong person: a paying customer offered a discount, a prospect in the middle of a negotiation, someone who asked to stop. An exclusion section exists to rule those sends out before a campaign starts, and an approver can sign it off as a single page.

This guide is a checklist for writing that page. For each group of people you should not contact, it covers what the group is, where the data comes from, and how to keep the list current.

Who this is for

This is for the person who signs off on an outbound policy: a head of sales, a RevOps lead, a founder, or a compliance owner. It is also for the person who writes the policy and has to hand it over for approval.

You do not need to be technical. You do need to know which systems hold your customer, deal and opt-out data. If a CRM holds them, you need to know who administers it.

Exclusions belong inside the policy itself. Outlevo sends nothing outside a policy that a person approved. [[1]](#sources) A policy sets who can be contacted, on which channels, how often and with what budget. [[1]](#sources) "Who can be contacted" is the exclusion section. Writing it as part of the policy puts it in front of the same approver who signs off on volume and channels.

Every external action is checked against the approved policy before it runs, and it is recorded in a ledger. [[1]](#sources) For an approver, that ledger is the audit trail: when someone asks why a contact was emailed, there is a record to open.

Steps

Steps 1 to 6 cover the six groups, in order. For each one, write down three things: the definition, the source, and the person who owns the refresh. Steps 7 and 8 add a safeguard for one-off emails and a plan for mistakes.

1. Current customers

Definition. Any company with a paying relationship today. Decide whether the rule works at company level or contact level. Company level is safer: it keeps a new sales rep from emailing a different person at a company that already pays you.

Where the data comes from.

  • If you use HubSpot, Outlevo reads your companies with name, domain, owner and lifecycle stage. [[2]](#sources) The lifecycle stage is the field that tells you who is a customer.
  • If you use Salesforce, Outlevo reads accounts, opportunities and their stages. [[3]](#sources) Write down which stage or field your team treats as "customer", because the approver should not have to guess. The Salesforce connection is a pilot: it needs the Outlevo package in your org, which Outlevo installs with you, and there is no AppExchange listing. [[3]](#sources)
  • If you have no CRM connection, a CSV import takes up to 200,000 rows and maps deal fields such as stage, amount, outcome and loss reason. [[4]](#sources) You can load customers and lost deals that way.

How to keep it current. A customer list that is correct on the day you write the policy goes stale quickly. Name the owner of the lifecycle stage or customer field in your CRM, and make "mark as customer" part of closing a deal. When the CRM is the source, the exclusion is only as current as that field.

Connecting and syncing a CRM uses no credits. [[2]](#sources) [[3]](#sources) Cost is not a reason to sync less often.

2. Open opportunities

Definition. Any company with a deal in progress, in any pipeline. Check open deals closely, because the contact may sit in a different system from the one the outbound team uses.

Where the data comes from.

  • In HubSpot, Outlevo reads deals with pipeline, stage, amount and closed-lost reason. [[2]](#sources)
  • In Salesforce, it reads opportunities and their stages. [[3]](#sources)
  • By CSV, open deals can be imported alongside won and lost ones. [[4]](#sources)

How to keep it current. List every pipeline that counts, not just the main one. A renewal pipeline or a partner pipeline can hold open deals that outbound should never touch.

Salesforce sends no webhooks to Outlevo. A rep's Accept or Reject on the Account is read by the 15-minute sync. [[3]](#sources) Do not assume an Accept or Reject is seen the moment a rep makes it. Say so in the policy, and ask reps to tell the campaign owner when a hot deal opens.

3. Recent losses

Definition. Companies you tried to win and lost. Some of them should wait before they hear from you again. Others should stay excluded for good, for example when the closed-lost reason was a conflict or a direct request not to be contacted.

Where the data comes from. The closed-lost reason is a field Outlevo reads from HubSpot deals. [[2]](#sources) CSV imports map a loss reason column too. [[4]](#sources) That reason is what lets you split "lost on price" from "asked us to stop".

How to keep it current. Pick a waiting period and write it into the policy as a number of days. This guide does not give a number, because there is no one right answer, and the approver should choose one for your sales cycle. Then decide who can lift the exclusion early. A good rule is that only the deal's previous owner can ask for it, in writing, with a reason.

Treat the loss reason as data that needs a clean-up. If reps leave it blank, you cannot tell a polite no from a hostile one, and the safest choice is to exclude every blank-reason loss until someone fills it in.

4. Competitors

Definition. Companies that sell what you sell. Emailing a competitor wastes a send and can hand them a copy of your messaging. Include their domains and, where it matters, the domains of their parent companies and brands.

Where the data comes from. This is a list your team maintains by hand. Keep it as a plain list of domains with a named owner and a review date, and put it in the policy document itself so the approver sees it.

How to keep it current. Review it whenever your market changes: a new entrant, an acquisition, a rebrand. Ask your sales reps, since they hear about competitors on calls before anyone writes it down. Competitor domains also turn up as a lost-deal reason in your CRM, so scan the closed-lost reasons for names that are not on the list yet.

5. Partners, resellers and referral sources

Definition. Companies you work with or that send you business: resellers, agencies, technology partners, investors, and customers' advisers you have a relationship with. A cold email to one of them reads as careless, and it can damage a relationship worth more than a single deal.

Where the data comes from. Like competitors, this is a list the team maintains by hand. Ask whoever owns partnerships to supply it, and name that person as the owner in the policy.

How to keep it current. Tie updates to onboarding. When a new partner signs, adding their domain to the exclusion list is a step on the same checklist as sending them a welcome pack.

6. Suppressed contacts and past opt-outs

Definition. Anyone who has asked not to be contacted, anyone whose address bounced, and anyone you have decided to stop emailing. This group has outside rules attached, so it needs the most care.

What the outside rules say.

  • The FTC's CAN-SPAM guide says: "The law makes no exception for business-to-business email." [[5]](#sources) (checked 2026-10-22)
  • 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." [[6]](#sources) (checked 2026-10-22)
  • Yahoo's sender best practices say: "Honor unsubscribes within 2 days". [[7]](#sources) (checked 2026-10-22)

The rules for emailing companies differ by place. The ICO's PECR guidance says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[8]](#sources) (checked 2026-10-22) GDPR Article 6(1)(f) refers to processing that is "necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[9]](#sources) (checked 2026-10-22) Recital 47 says processing of personal data for direct marketing "may be regarded as carried out for a legitimate interest". [[10]](#sources) (checked 2026-10-22) These quotes are not legal advice. Have counsel read the rules that apply to the markets you sell into.

Where the data comes from.

  • Smartlead sends sent, reply, bounce, unsubscribe and category-change events back to Outlevo by webhook. [[11]](#sources) That is where opt-outs and bounces arrive from a sending tool.
  • If HubSpot contact import is on, it brings in email, name, job title and email opt-out. [[2]](#sources) An admin must turn it on first, with a stated purpose. [[2]](#sources) Write that purpose in the policy so the approver and the admin agree on it.
  • On LinkedIn, a reply stops that lead's emails. [[12]](#sources) A reply is not always an opt-out, but it is a signal that the sequence should stop, and the policy should say so.
  • The public API has resources named suppressions, compliance, policies and ledger. [[13]](#sources) If your team keeps opt-outs in another system, those are the places to look for loading and reading suppression data in code. The full list is on the API reference.

How to keep it current. Do not rely on one source. A person may opt out through a reply to a rep, an unsubscribe link, a call to support, or a CRM field. Name every route in the policy and name who is responsible for moving each one onto the suppression list. For the wider mechanics of unsubscribes and list hygiene, see Cold email opt-outs and suppression lists.

Keep opt-outs on the list permanently. A suppression list that expires entries is a list that will email the same person again.

7. Add a last line of defense for one-off emails

Campaign exclusions do not cover a rep writing a single email. The Gmail extension has a recipient guard that warns before you email a contact Outlevo should not reach. [[14]](#sources) It drafts replies in Gmail's compose and never sends from Gmail. [[14]](#sources) If your reps email from Gmail, ask them to install it. An owner or admin can turn the extension off for the whole workspace, which signs everyone out. [[14]](#sources)

8. Plan for the mistake

Assume that one day a person you should have excluded gets an email. The policy should say who stops the send and how.

Kill switches pause a campaign, a channel or the whole workspace at once. [[1]](#sources) Write down who may press which one. Who holds each switch is a rule your team agrees and writes into the policy. One option is that a campaign owner pauses their own campaign and only an admin pauses the workspace. Then write what happens next: remove the contact, find the source of the gap, fix the list, and record it.

What to check

Use this list before the approver signs. Each item should have a yes, a name, and a date.

Coverage

  • Customers, open deals, recent losses, competitors, partners and suppressed contacts each have a written definition.
  • Each group has a named source: a CRM field, a CSV, a webhook, or a hand-kept list.
  • Each group has a named owner for the refresh.
  • Rules apply at company level where a company-level exclusion makes sense, and at contact level for opt-outs.

Sources

  • The HubSpot or Salesforce field that marks a customer is written down. [[2]](#sources) [[3]](#sources)
  • Every pipeline that holds open deals is listed. [[2]](#sources)
  • The field mapping has been approved by an owner or admin. Outlevo writes nothing to HubSpot until that approval, and it writes only to its own properties, never to standard fields. [[2]](#sources)
  • If contact import is on, the stated purpose is written in the policy. [[2]](#sources)
  • If Salesforce is a source, the team knows the connection is a pilot that needs the Outlevo package in your org. [[3]](#sources)
  • The competitor and partner lists exist, have an owner, and carry a review date.

Opt-outs

  • Every route by which someone can opt out is listed, with who moves it onto the suppression list.
  • The unsubscribe link and one-click unsubscribe requirements are met in every campaign. [[6]](#sources)
  • Someone checks that unsubscribes are processed inside the 2-day window Yahoo names. [[7]](#sources)
  • Opt-outs never expire.

Testing

  • Before any real send, rehearse the campaign in the sandbox. Test keys act on a sandbox with 100 fake companies, so you can build without sending anything or spending credits. [[15]](#sources) The developer hub covers the sandbox.
  • Pick a customer from your real CRM and confirm that the company appears on the exclusion list written in the policy.

Response

  • The kill-switch owner is named for campaign, channel and workspace. [[1]](#sources)
  • The steps after an error are written: stop, remove, find the cause, fix, record.
  • A review date for the whole exclusion section is set.

Common gaps

Check the section against these gaps before it goes to the approver:

  • Keep the list out of one person's head. If the customer list is a spreadsheet nobody owns, it will be out of date by the next campaign. Give it an owner.
  • Exclude by domain, not only by address. Where the group is a company, a new contact at an excluded company walks straight through an address-only rule.
  • Keep opt-outs outside the sending tool too. If you ever change tools or add a channel, a list kept only in one tool stays behind. Keep a copy that does not depend on one vendor.
  • Give the loss reasons an owner. If reps leave them blank, the waiting-period rule cannot work.
  • Cover the ads side. The same idea applies to paid audiences. Outlevo's Google Ads integration says that below Google's targeting threshold (accounts at least 90 days old with $50,000 lifetime spend), the list can still keep those accounts out of your campaigns. [[16]](#sources) If you run ads, say in the policy whether customers are kept out of them too.

Next step

Write the one-page version first. For each of the six groups, put down the definition, the source, the owner and the review date. Then send it to your approver with the checklist above, and use the sandbox to rehearse it before the first real send.

If you want to see what Outlevo can read about your accounts before you write the policy, run the free ICP assessment. It reads up to 5 public pages of a website. [[17]](#sources) To see how policies, approval and the ledger fit together, read How Outlevo works. If your CRM is HubSpot or Salesforce, the HubSpot and Salesforce pages list exactly what is read and written.

Sources

  1. How Outlevo works
  2. HubSpot integration
  3. Salesforce integration
  4. CSV and Excel integration
  5. FTC: CAN-SPAM Act compliance guide for business
  6. Google: Email sender guidelines
  7. Yahoo: Sender best practices
  8. ICO: Electronic mail marketing (PECR)
  9. GDPR Article 6(1)(f): lawfulness of processing
  10. GDPR Recital 47: legitimate interests of the controller
  11. Smartlead integration
  12. LinkedIn integration
  13. Outlevo API reference
  14. Gmail extension integration
  15. REST API and SDK integration
  16. Google Ads integration
  17. Free ICP assessment

Related

See what Outlevo finds on your own website

Free, no sign-up, about a minute.