EMAIL SETUP
Cold Email Setup Checklist: Before Your First Campaign
The tools are connected and the first campaign is nearly ready. Before you press send, test what happens when someone replies, opts out, or makes an enquiry. Those checks are easier to fix now than halfway through a live sequence.
Use this as a practical launch checklist. It doesn’t replace checking the laws and provider rules that apply to your audience, and it doesn’t promise inbox placement. The aim is to find the gaps your team can fix before sending.
Who are you contacting, and why?
Before a US, Canadian, or European launch, record the recipient country, language, local time zone, and eligibility review. Separate EU/EEA countries from the UK; a generic Europe label is too broad for permission checks. Verify the collection history and provider rules, and make sure the person handling replies and opt-outs can cover the intended working hours. Assign domain, DNS, mailbox, integration, and campaign-pause owners.
- Write down the business need your offer addresses and why each audience segment is relevant.
- Document the source of contact data and whether you may use it for the planned outreach.
- Keep excluded contacts and previous opt-outs out of new imports.
Review the message honestly
Use an accurate sender identity and subject line. Make the commercial purpose clear, avoid unsupported claims, and provide a clear opt-out. US commercial-email obligations include a valid postal address and timely opt-out handling; B2B email isn’t automatically exempt. Review the FTC's CAN-SPAM guide and obtain advice for other applicable jurisdictions.
Write audience rules a teammate can follow, then try them on a few records. Check the source date, whether the role fits, and whether somebody is already speaking to the account. Keep previous objections and opt-outs out of the import. A working address is useful, but it doesn’t establish that your offer is relevant or that you may send it.
Draft the introduction before buying more sending capacity. Explain the task you help with, identify the business clearly, and ask for a manageable next step. If you can’t explain why this group might care without inventing a problem, change the audience brief. More mailboxes won’t make that first message easier to justify.
Who owns the setup, and does authentication work?
- Record who controls domains, DNS, mailboxes, and the sending platform.
- Use multi-factor authentication where available and share access through appropriate account roles.
- Keep transactional business mail separate in your operational planning; do not use extra domains to evade provider enforcement.
Check authentication on an actual message
Inventory every legitimate sender before changing SPF. Enable DKIM signing, review DMARC alignment, and inspect a test message's authentication results. A DNS record alone doesn’t prove that your platform signs mail correctly.
Gmail requirements vary by sending volume. Consult Google's current sender guidelines for authentication, transport, complaint, and unsubscribe requirements.
Before committing to accounts, read the guides to domains and mailboxes and email providers. Start with a permitted use and a workload the team can manage. A theoretical sending maximum won’t tell you whether the setup fits your business or whether anyone has time to handle the replies.
Will replies and stop requests reach the right place?
- Reply to a real test message and confirm the intended person receives it.
- Follow the unsubscribe link and verify the address is suppressed from future sends.
- Check provider-required one-click unsubscribe support separately from the visible body link.
- Make sure a new campaign import does not reactivate suppressed recipients.
Test a written stop request as well as the link. Can a person recognise it, exclude the contact, and cancel the next step? Import your test contact again and check that it stays excluded. If tomorrow’s sync would make the person active, the opt-out process still needs fixing—even if today’s confirmation page looks fine.
Decide who reads delivery failures and replies the tool can’t classify. Make it clear where those events appear and who covers absences. A connected mailbox is only part of being ready: someone needs to act on what arrives. That responsibility should be agreed before the campaign starts, not after an unanswered enquiry sits in the queue.
Check the queue and the enquiry journey
Review account limits and recipient-provider responses. Investigate persistent bounces, complaints, or deferrals before increasing volume. There is no universal daily number or warm-up schedule that guarantees placement.
Connect the website and the enquiry flow
- Use campaign parameters after a question mark, not inside a URL fragment.
- Test the landing page on a phone and submit an authorized test enquiry.
- Check the acknowledgement, team alert, stored enquiry, and attribution independently.
- Never put subscriber email addresses or other personal information in analytics campaign tags.
Trace an authorised enquiry through the landing page, acknowledgement, team notification, and saved record. Check the destination too: a submitted message in the browser does not establish that sales received it.
Keep the sign-off specific: what was tested, when, what remains unresolved, and who will fix it. Note which changes need another test. If a key check fails, pause that part of the launch—especially when it handles someone’s request to stop.
Quick checklist before you approve launch
Separate attempted sends, accepted mail, human replies, qualified conversations, and customers. Treat recorded opens cautiously; Apple Mail Privacy Protection limits what senders can learn about reading activity.
Launch gate
Don’t launch until authentication, replies, opt-outs, ownership, message review, and enquiry handling have each been checked. Keep the evidence and assign an owner to unresolved issues.
A launch sign-off sheet
| Check | Evidence before approval |
|---|---|
| Audience and message | A reviewed segment, source, exclusions, and accurate message. |
| Authentication | A received test message checked for the intended sending route. |
| Reply handling | A controlled reply reaches its owner and stops follow-ups. |
| Unsubscribe | A test opt-out remains suppressed after reimport. |
| Enquiry flow | A controlled form submission reaches the expected team and acknowledgement inboxes. |
| Decision | Named approver, unresolved issues, and a documented go/no-go choice. |
For example, authentication may pass while an opted-out test contact becomes active after an import. Keep the campaign paused until that is corrected. Save who tested each check and when, and repeat the relevant ones after a change to DNS, the sending tool, or the form integration. You want a sign-off that explains the working setup, not just a row of green ticks.
If one of these checks is holding up your launch, TransmitInbox can help work through it. Tell us which tools you’re using and where the test fails so we can discuss the setup work you need.
Before release, check mobile readability, the exact CTA destination, and missing merge-field fallbacks using received messages. Give campaign approval and exception handling named owners.
Source references
Editorial review: October 14, 2026 · TransmitInbox team. Consult the linked documentation for current requirements.