PRACTICAL OUTREACH
Cold Email Handoff Checklist: Who Owns Replies?
A cold email campaign can be technically well configured and still fail operationally. Replies may sit in an unattended inbox, opt-outs may reach the wrong person, or a bounce report may never reach whoever controls the sending domain.
This cold email handoff checklist helps founders, sales teams and agencies define ownership before a campaign starts.
Why handoffs create sending problems
Cold email work often involves several people: a founder approves the offer, a sales operator builds the list, an agency manages the sequence, and an IT administrator controls DNS or Microsoft 365.
That gap creates predictable problems:
- Positive replies are not assigned quickly.
- Bounces continue because nobody owns list suppression.
- Opt-out requests are forwarded manually or overlooked.
- A mailbox restriction is discovered only after a campaign stops sending.
Microsoft documents that Exchange Online can throttle, reject or restrict outbound sending when limits or suspicious activity are detected. Google also expects senders to monitor authentication, spam feedback and unsubscribe implementation. These are not tasks that should be left to an informal “someone is checking it” arrangement.
Assign five owners before launch
Write down the owner for each function. One person can hold several roles, but every role needs a named backup.
1. Campaign owner
The campaign owner controls the audience, offer, copy, sequence and stop conditions. They decide which segments are appropriate and pause the campaign when the offer, list or targeting changes.
2. Reply owner
The reply owner monitors the mailbox or shared inbox. Their job is to classify replies into interested, not now, referral, automatic reply, objection, unsubscribe and unrelated message categories. Define a response-time target that fits your sales process and document what happens when the owner is unavailable.
3. Suppression owner
The suppression owner maintains the exclusion process. This includes opt-outs, hard bounces, repeated soft bounces, complaints, role accounts that should not be contacted and addresses that the client or sales team has manually excluded.
Do not keep suppression data only inside one sending tool. If you change platforms, use multiple domains or work with an agency, the suppression rules must move with the campaign. A central suppression register can reduce the risk of re-importing an address that already opted out.
4. Infrastructure owner
The infrastructure owner controls DNS, mailboxes, authentication records, provider access and account recovery. They should know which domains send campaign mail, which provider signs DKIM, which SPF mechanisms are authorised and where DMARC reports are reviewed.
Google’s sender guidance requires authentication and alignment for relevant traffic, while Microsoft recommends SPF, DKIM and DMARC configuration and warns that Exchange Online is not designed for unrestricted bulk mailing. These checks require access and technical judgment, so they should not be assigned only to a copywriter or sales assistant.
5. Deliverability monitor
The deliverability monitor reviews bounces, deferrals, spam complaints, provider dashboards, sending volume and mailbox health. This role has authority to pause sending without waiting for a sales meeting.
Build a handoff record, not a chat message
A useful handoff should be understandable to someone who did not attend the setup call. Keep it in a shared document or ticketing system rather than relying on a chat thread.
Record at least:
- Sending domains, mailboxes and providers.
- DNS and authentication owner.
- Campaign owner and reply owner.
- Where replies, bounces and complaints are reviewed.
- Where opt-outs and exclusions are stored.
- Daily or weekly sending limits and pause conditions.
- Who receives provider alerts.
- Who may change copy, targeting, volume or infrastructure.
- The escalation path for a blocked mailbox, unusual bounce pattern or suspected compromise.
Also record the status of each handoff item: ready, needs approval, blocked or not applicable. “Configured” is not the same as “verified.” For example, a DKIM record may exist in DNS while the sending platform is using a different domain or selector.
Separate operational rules from legal review
Unsubscribe handling is both an operational and a legal concern, but those are not identical questions. The United States CAN-SPAM framework requires accurate header information, an opt-out mechanism and prompt handling of opt-out requests; it also says businesses cannot transfer legal responsibility simply by hiring another company.
UK readers need to consider PECR and related data-protection guidance. The ICO explains that electronic direct marketing rules can differ depending on the recipient and type of message, including distinctions involving business-to-business activity. Canada and other European countries have their own requirements and should not be treated as copies of US or UK rules.
Use a documented suppression workflow regardless of jurisdiction, but obtain appropriate legal advice for the countries and recipient types involved. Permission to process business contact data is not automatically permission to send every form of marketing email.
At minimum, the handoff should specify:
- Who receives an opt-out request.
- How quickly it is recorded.
- Which systems receive the suppression update.
- How the address is prevented from re-entering future campaigns.
- Who checks that the message contains the required identification and opt-out information for the relevant market.
For a broader overview of jurisdictional issues, see our guide to cold email compliance.
Quick checklist before sending
- Name a campaign owner, reply owner, suppression owner, infrastructure owner and deliverability monitor.
- Test the reply route from an external address and confirm who receives it.
- Send a test opt-out and verify that it reaches the suppression process.
- Confirm that bounces are visible to the person responsible for list hygiene.
- Record pause conditions, including unusual complaints, authentication failures and provider restrictions.
- Check that every person with access knows how to pause sending.
- Schedule a review after the first small batch and after any provider, domain or mailbox change.
Common mistakes include giving an agency access without defining client responsibilities, allowing a salesperson to change sending volume without infrastructure review, and treating a campaign dashboard as a complete monitoring system. A dashboard can show activity while replies, opt-outs or provider alerts remain unattended.
If your team needs help assigning these responsibilities, checking the sending setup or monitoring campaigns across domains and mailboxes, a managed cold email service can provide the operational layer and documented handoffs. Review our managed cold email service guide to understand what support may be appropriate.