You send a carefully written sequence to a relevant list. The offer is clear, the subject lines are sensible, and the sales team is ready for replies. Yet almost nobody responds. Then you discover that the sending domain was never properly authenticated, the database contains invalid addresses, and the campaign volume jumped on day one.
That outcome isn't usually caused by one bad email. Email deliverability is a connected sequence of infrastructure, data and sending decisions. A failure in one part affects the others, creating more bounces, complaints, filtering and wasted sales capacity. A delivered message isn't necessarily visible in the inbox, and an opened message isn't necessarily a qualified conversation.
This checklist puts the work in a practical order. It starts with authentication, moves through infrastructure and data quality, then covers sending behaviour, engagement, copy and complaint handling. Use it alongside Mailbeam's guide to fixing deliverability issues when diagnosing a live programme.
1. Authentication Protocols
Mailbox providers need evidence that your organisation is allowed to send from its domain. SPF, DKIM and DMARC provide that evidence, but they solve different parts of the problem.
SPF identifies the sending services authorised for your domain. DKIM adds a cryptographic signature to the message. DMARC tells receiving providers how to handle messages that fail authentication and checks whether the authenticated domain aligns with the visible From domain. A message can pass one technical check and still fail DMARC alignment.
Google's requirements make this a launch prerequisite. Since 1 February 2024, all senders emailing personal Gmail accounts have needed at least SPF or DKIM, valid forward and reverse DNS records, and a user-reported spam rate below 0.3%. Bulk senders, defined by Google as those sending 5,000 or more messages per day to Gmail accounts, need SPF, DKIM, DMARC alignment and one-click unsubscribe for promotional messages. Google's sender guidelines also advise keeping complaints below 0.1%, which is the safer operating target.
Configure for visibility before enforcement
Publish DMARC with p=none first. Review aggregate reports to identify legitimate services, forgotten vendors and unauthorised traffic before moving towards quarantine or reject. Keep a record of every service that sends from the domain, including CRM platforms, marketing tools, support systems and outbound infrastructure.
Audit DNS records regularly. An old SPF include, missing DKIM key or misaligned return path can undermine a campaign that otherwise looks healthy. Test authentication before launch with a DNS or mail diagnostic tool, and make sure every sending provider has its own documented configuration.
Practical rule: Don't approve a campaign until the sending domain, visible From address, SPF, DKIM and DMARC alignment have been tested together.
2. IP Rotation and Sending Infrastructure
Sending infrastructure determines how mailbox providers see your volume and reputation over time. It also determines how quickly your team can isolate a problem when one campaign starts generating complaints.
Shared IP pools reduce operational overhead, but your reputation is partly connected to other senders using that pool. Dedicated infrastructure gives you more control, yet it also gives you full responsibility for building and protecting its reputation. IP rotation can distribute activity, but rotating addresses won't fix poor targeting, unauthorised sending or complaint-heavy campaigns. It may only spread the problem across more infrastructure.
H2 uses Smartlead.ai infrastructure for campaign sending, including IP rotation. That can help operators separate campaigns and investigate sending patterns, but the platform still needs accurate domain configuration, controlled volume and clean recipient data. A mail service provider can explain how rotation works, which domains share infrastructure and how complaints are handled.
Match infrastructure to the operating model
Separate different sending purposes where the risk and urgency differ. Transactional messages, customer communications and prospecting campaigns shouldn't all depend on the same sending path. Document which campaign uses which domain, inbox or IP so the team can trace a sudden change in bounces or complaints.
Before changing infrastructure, check:
- Provider controls: Confirm how the provider manages abuse, complaints, suppression and shared pools.
- Reputation visibility: Review available authentication, complaint, bounce and provider-level diagnostics.
- Rotation logic: Understand whether rotation follows a predictable schedule and how a damaged IP is removed.
- Troubleshooting ownership: Assign a person who can pause campaigns, contact the provider and document remediation.
A step-by-step Amazon SES SMTP guide can help teams understand the mechanics of SMTP-based sending. The right setup is the one your team can monitor and operate consistently, not the one with the most complex architecture.
3. Warm-Up Sequences and Sender Reputation Building
A new domain or inbox has little sending history. Treating it like an established sender and launching a large prospecting sequence immediately creates an abrupt pattern that mailbox providers may distrust.
Warm-up should build a predictable record with recipients who are likely to recognise and value the messages. Existing customers, subscribers, partners and genuine business contacts are more useful early recipients than a large cold segment. Their replies and positive interactions give the sending identity a credible operating history.
H2's Fully Managed Outbound programme includes domain and inbox readiness before campaign launch. Smartlead.ai also provides warm-up automation used by H2 clients. Automation can control schedules, but it can't make an irrelevant message wanted. A warm-up tool is operational support, not a substitute for audience quality.
Use warm-up as a quality gate
Start with a small, controlled audience and increase volume only when authentication, bounce behaviour and complaints remain stable. The exact pace depends on domain history, provider, audience and message type. Don't copy a generic schedule without checking the signals from your own sending environment.
During warm-up, record:
- Volume by sender: Track each domain, inbox and IP separately.
- Recipient response: Review replies, positive engagement and unexpected objections.
- Negative signals: Pause the next increase if bounces, complaints or filtering worsen.
- Message quality: Use early conversations to refine the offer, targeting and call to action.
A warm-up sequence should answer a commercial question as well as a technical one. If the first recipients don't understand why you're contacting them, scaling the campaign will increase workload for sales and support without creating useful demand. Send steadily, learn from real responses and scale only when the whole system is behaving well.
4. Domain Reputation Monitoring and Remediation
Authentication proves that a message is authorised. Reputation reflects what recipients and mailbox providers think of the sender's behaviour. That reputation can deteriorate even when DNS records are correct.
Monitor complaint rates, bounces, provider responses, authentication results and blocklist status by domain and campaign. Don't rely on an account-level average. A healthy campaign can conceal a problematic segment, vendor or sending identity, while an overall delivery figure can hide messages accepted by the receiving server but classified away from the visible inbox.
The distinction matters. Recent benchmark data reported global inbox placement at about 83.5%, with 9.8% of messages accepted by mailbox providers but not visible in the inbox and 6.7% reaching spam folders, as described in Sales.co's deliverability research. Technical delivery alone doesn't tell the sales team whether prospects saw the message.
Build a remediation playbook
Set alerts for changes rather than waiting for a campaign report. When a signal moves in the wrong direction, pause the affected segment, inspect the data source and review the message that caused the change. Don't rotate domains or IPs as a first response. That can make attribution harder and leave the underlying problem unresolved.
Useful actions include:
- Segment reporting: Break results down by provider, domain, campaign, vendor and acquisition source.
- Complaint investigation: Identify whether recipients objected to targeting, frequency, consent or message content.
- Blocklist review: Check relevant reputation services and contact the sending provider when infrastructure is implicated.
- Documented recovery: Record the cause, pause decision, corrective action and conditions for restarting.
For a more detailed process, use H2's guide to email deliverability issues. The best monitoring setup gives marketing, sales and RevOps the same view of risk, so nobody keeps increasing volume while another team is investigating complaints.
5. Database and List Enrichment Quality Control
A verified email address can still belong to the wrong person. Enrichment adds job role, company context, technology information and other fields that determine whether a prospect belongs in a campaign. If those fields are wrong, your messages become irrelevant even when they reach the inbox.
H2's enrichment process combines public company information, LinkedIn, Hunter, RocketReach and other sources, then validates records before outreach. The point isn't to collect the largest possible number of fields. It's to establish enough reliable context to make a sound decision about fit, message and timing.
Full Scale is a useful example of the operational value of this approach. H2 analysed and scored 50,000 companies, with the client reporting savings of 5,000 hours and $125,000. Those figures describe that specific engagement, not a universal result. The relevant lesson is that scoring and exclusion happen before outreach, reducing the amount of poor-fit data passed to sending and sales teams.
Create confidence rules for every field
Mark fields as high, medium or low confidence. A critical campaign aimed at a narrow role shouldn't treat an unverified title as equivalent to a confirmed one. Compare sources where the account fit matters, and manually review a sample before launch.
Remove records that lack essential context. That may include a missing company, unclear role or no defensible reason for contact. Recheck data when a campaign has been delayed, because a well-researched record can become stale before the first send.
A larger database doesn't create a stronger campaign if the team can't explain why each recipient belongs in it.
Keep source information with the record. When a recipient complains or a salesperson challenges a lead, the team should be able to see which source supplied the title, company detail or buying signal. That traceability connects deliverability to workload, because it lets operators fix the failing data source instead of repeatedly cleaning the same symptoms.
6. List Hygiene and Contact Verification
List hygiene starts before the sending platform. It covers invalid addresses, duplicates, outdated contacts, role accounts, opt-outs and records that no longer meet the campaign's audience rules.
Verification tools can identify syntax problems, domain issues and some mailbox risks, but no tool can prove that a person wants your message. Use verification to remove technical risk, then use qualification and suppression rules to control relevance. H2 includes contact verification in its Fully Managed Outbound process and uses tools such as ZeroBounce, NeverBounce, Hunter and RocketReach in data workflows.
The sequence matters. Verify immediately after enrichment, before warm-up and again before a delayed campaign launches. If you clean the list only after a bounce-heavy send, the infrastructure and domain have already absorbed the negative signal.
Keep a permanent suppression layer
Maintain a master suppression list across every sending domain, inbox and campaign. An unsubscribe from one campaign should prevent future sends from another. Complaining recipients should be removed immediately, not merely excluded from the current sequence.
Use clear rules for common risk categories:
- Invalid addresses: Suppress addresses that fail verification or generate permanent bounce evidence.
- Role accounts: Remove generic addresses unless the campaign specifically targets that function.
- Stale records: Store verification dates and recheck records that have been inactive for a long period.
- Duplicates: Deduplicate at person and account level so several teams don't contact the same buyer.
- Unclear fit: Hold records with missing or contradictory company and role data for review.
H2's email verification guide provides further practical context. List quality is not just a marketing hygiene task. It protects sending reputation, reduces wasted research and gives salespeople a better chance of receiving replies from people who can act.
7. Engagement-Based Segmentation and Send Timing
A prospect replies to a referral within an hour, while a cold contact from the same account ignores three emails in a row. If both stay in one sequence, the team creates extra work for sales, weakens relevance and learns the wrong lesson from campaign results. Engagement-based segmentation fixes that by treating deliverability as a chain of infrastructure, data and sending decisions, not a subject line trick.
Start with relationship strength. Recent responders, referred contacts and people who have already interacted with your company should move into a separate path with lighter automation and clearer ownership. That group can handle more direct asks because the context already exists. Cold outreach needs a different threshold. Account fit, role relevance and a timely business reason to reach out are enough to justify research and a first email, but they do not prove active intent.
This is also where teams often blur signals. A social interaction, a website visit or a technology match may justify the next step, but each signal should change the workload and owner, not just trigger another automated send.
H2's campaign management uses replies, objections and engagement patterns to refine targeting. Clay workflows can combine enriched data with engagement signals so the next action reflects what the prospect has done.
Send-time testing should follow the same logic. Test by time zone, market and audience type, then judge performance by qualified conversations, booked follow-up activity and whether the right owner can act on the reply. Open rates on their own do not tell you whether timing improved pipeline quality. Gmail's sender guidance recommends sending to recipients who want the messages and periodically removing contacts who do not engage.
A practical segmentation model usually includes four operating groups:
- Warm audience: Use direct context, shorter paths and restrained frequency.
- Cold audience: State why you are reaching out, match the message to role and account context, and make it easy to decline.
- Non-engaged audience: Cut volume, test a re-engagement note or suppress the record.
- Responders: Stop automation and route the conversation to sales, support or the account owner.
Good timing helps. Relevance decides whether the email earns attention.
8. Frequency Capping and Cadence Optimisation
A campaign can be fully authenticated, well targeted and still create inbox fatigue. The break usually happens when infrastructure, data and team activity stop lining up. Marketing sends a nurture touch, sales adds a manual follow-up, customer success reaches out on the same account, and the recipient experiences one company with no sense of cadence.
Frequency capping fixes that at the operating level. Set limits per contact across sequences, tools and teams, then tie those limits to who owns the next step. A reply, a meeting, an objection or a clear opt-out should shift the record out of automation and into a human workflow immediately. If no one owns that handoff, cadence keeps running long after the conversation has changed.
The schedule itself should stay simple. Start with an initial email, wait several days, send a follow-up that adds context, then leave space before any later touch. Keep the intervals aligned with buying cycle, role and message value. A founder, a technical evaluator and a procurement contact should not inherit the same pattern just because they sit in one account.
What matters is not how many touches the sequence completed. It is whether the volume produced qualified conversations without creating extra cleanup for sales, support and RevOps.
Useful controls usually sit in four places:
- Cross-campaign frequency: count every message to the same person, regardless of tool or team.
- Stage and ownership: suppress active opportunities, open support threads and booked meetings.
- Response quality: slow or stop sends when follow-ups produce silence, soft objections or low-fit replies.
- Complaint movement: pause the segment if complaint levels start moving toward the practical target discussed in Validity's 2025 benchmark.
Good cadence protects reputation, but it also protects workload. It gives the right person a fair chance to respond without making persistence their burden.
9. Content and Copy Testing for Engagement
A campaign can be technically clean and still fail the inbox test that matters. The message arrives, gets opened, and goes nowhere because the recipient cannot quickly tell who sent it, why they were chosen, or what would make a reply worth their time. That gap shows up later as weak conversations, extra triage for sales, and copy changes made too late.
Treat copy testing as part of deliverability operations, not as a separate creative exercise. Infrastructure gets the message accepted. Data decides whether it reached the right person. Copy determines whether the send earns a useful response and whether the team should keep that segment live.
The safest way to test is to change one meaningful variable at a time. Change the problem frame, the opening line, the proof point, the call to action, or the reason for the follow-up. Then review replies, objections, unsubscribes, and meeting quality together. Opens can still help with context, but they are an incomplete signal, especially given mailbox privacy behaviour. H2's cold email open rate guidance is useful for that context.
Clarity usually beats cleverness.
State who you are, why the recipient fits, and what kind of response would help. Keep subject lines honest. Cut exaggerated claims, unnecessary links, and decorative formatting that makes the message harder to classify. In practice, a plain email that matches the research gives sales and RevOps cleaner signals than a polished message that creates vague interest and no qualified next step.
H2's outbound work includes copy testing and campaign optimisation based on replies, objections, and sales feedback. The Ravn campaign shows that process, with messaging refined through campaign responses before scaling. Its reported result was $4 million in new pipeline, attributed to the campaign by co-founder Micah Lisonbee. That outcome came from one client engagement, not from a repeatable formula.
A useful testing record does not need a complex dashboard. It needs enough detail for the team to decide ownership and next action:
- Audience definition: who received the variation and why
- Message variable: what changed between versions
- Behavioural response: whether recipients replied, objected, clicked, or unsubscribed
- Sales value: whether the response became a qualified conversation
- Next decision: whether to revise, pause, or scale the variation
10. Complaint and Unsubscribe Management
Complaints are direct evidence that recipients or mailbox providers consider the messages unwanted. Gmail advises senders to stay below 0.1% user-reported spam and prevent the rate from reaching 0.3%. At 50,000 delivered emails, those rates represent 50 and 150 complaints respectively, as explained in Validity's historical deliverability analysis. The difference is operationally significant because each complaint can influence how future mail is filtered.
Google says bulk senders whose spam rate reaches 0.3% may lose access to delivery mitigations and remain ineligible until the rate stays below that threshold for seven consecutive days. Treat 0.1% as the practical ceiling, not as a target to approach casually.
Make suppression immediate and global
Use a clear unsubscribe route in every promotional email and test it before launch. For bulk Gmail sending, implement one-click unsubscribe as part of the sending configuration. Process opt-outs promptly, then apply them across all domains, inboxes and tools. A recipient shouldn't need to unsubscribe from several separate sequences.
Review complaints by campaign, message, audience and acquisition source. If one segment rises, pause that segment rather than reducing volume everywhere. Investigate whether the cause was poor data, unclear identity, unexpected frequency, weak relevance or a missing opt-out path.
A complaint is not a lead-quality issue to file away. It's a stop signal for the sending system.
Document the investigation and corrective action. H2's outbound programmes include complaint and unsubscribe processing, and teams can also adjust their privacy settings when they want to control future communications. Respectful suppression protects the domain, reduces internal follow-up work and leaves the team with a cleaner audience for future campaigns.
10-Point Email Deliverability Best Practices Comparison
| Item | Implementation Complexity | Resource Requirements | Expected Outcomes | Ideal Use Cases | Key Advantages |
|---|---|---|---|---|---|
| Authentication Protocols (SPF, DKIM, DMARC) | Medium, DNS changes and key management | DNS access, testing tools, periodic monitoring | Improved inbox placement; reduced spoofing; DMARC reports | All sending domains before campaign launch | ISP compliance; stronger sender credibility; anti‑spoofing |
| IP Rotation and Sending Infrastructure | High, manage multiple IPs, warm‑up and routing | Multiple IPs (dedicated/shared), monitoring tools, cost | Stable deliverability; reduced throttling; isolate issues | High‑volume senders; agencies; multi‑client environments | Avoids rate limits; targeted troubleshooting; reputation control |
| Warm‑Up Sequences and Sender Reputation Building | Medium, staged volume increases and monitoring | Time (2–4 weeks), warm audiences, monitoring | Faster inbox placement for new IPs/domains; fewer bounces | New domains/IPs, migrations or reactivations | Safely builds reputation; validates setup before scaling |
| Domain Reputation Monitoring and Remediation | Medium, tool setup and analyst interpretation | Monitoring subscriptions, alerting, analyst time | Early problem detection; targeted remediation; protected placement | Ongoing campaigns; shared IP environments; enterprises | Data‑driven alerts; reduces emergency downtime; protects long‑term deliverability |
| Database & List Enrichment Quality Control | Medium, multi‑source integration and validation | Paid enrichment APIs, validation workflows, manual checks | Better targeting; higher reply rates; fewer wasted sends | Account‑based marketing; highly targeted B2B campaigns | Enables precise personalization; prioritizes high‑value prospects |
| List Hygiene and Contact Verification | Low–Medium, integrate verification APIs | Verification API costs, processing time, tooling | Lower bounce rates; fewer spam‑trap hits; improved deliverability | Any sender before launches; large lists or purchased data | Reduces wasted sends; protects sender reputation; cost‑effective |
| Engagement‑Based Segmentation & Send Timing | Medium, data analysis and automation | Historical engagement data, CRM/ESP integration | Higher open/reply rates; stronger ISP engagement signals | Senders with engagement history; re‑engagement strategies | Boosts engagement; prioritizes warm prospects; optimizes timing |
| Frequency Capping & Cadence Optimization | Low–Medium, rule configuration and coordination | Automation rules, campaign coordination, monitoring | Lower complaints/unsubscribes; sustained engagement | Multi‑campaign programs; brand protection scenarios | Prevents recipient fatigue; protects reputation; consistent follow‑ups |
| Content & Copy Testing for Engagement | Medium, A/B testing framework and analysis | Testing infrastructure, larger sample sizes, analytics | Identifies higher‑performing messages; increased replies | Scaling campaigns; diverse buyer personas | Finds winning copy; improves response rates; reusable templates |
| Complaint & Unsubscribe Management | Low, automated suppression and workflows | Suppression lists, automation, compliance processes | Reduced complaint rates; legal compliance; preserved reputation | All senders, especially regulated jurisdictions | Ensures compliance; removes complainers quickly; protects deliverability |
Turning the Checklist Into a Routine
These practices work best as an operating rhythm, not as a one-time technical project. Before every launch, confirm that the sending domain is authenticated, the visible From domain aligns with SPF or DKIM, DNS records are current and unsubscribe handling works. Then verify the audience after enrichment, remove duplicates and invalid records, check suppression lists and approve the first sending segment.
After launch, monitor complaints, bounces, authentication and provider-level signals. Review them by domain, inbox, campaign and audience rather than relying on one blended dashboard. If complaints rise or a segment produces weak engagement, pause that segment, investigate the cause and restart only after the targeting, frequency, data or message has changed.
Run a weekly review with marketing, sales and RevOps. The agenda should include:
- Infrastructure: Authentication results, DNS changes, provider issues and sending ownership.
- Data quality: Verification age, duplicate records, missing fields and suppression coverage.
- Campaign behaviour: Volume changes, cadence, replies, objections and unsubscribe movement.
- Commercial results: Qualified conversations, meetings and opportunities created from each segment.
- Team workload: Unanswered replies, routing failures, manual research and follow-up capacity.
Don't judge deliverability by delivery rate alone. A mailbox provider may accept a message without placing it somewhere the recipient will notice. A 2025 analysis cited in the verified research found that only 60% of tested messages reached a visible Gmail mailbox location across Primary, Promotions, Updates and spam, which is why replies and qualified conversations need to sit alongside placement diagnostics.
Your first action this week is simple. Choose the domain that sends your most important campaign, audit SPF, DKIM and DMARC alignment, and confirm who owns the findings. Then check the suppression list and pause any segment that can't explain why its recipients are relevant.
If you want a second opinion, H2 offers a 15-minute introductory call to discuss your business, audience and current challenge, alongside a free GTM strategy. Its Fully Managed Outbound service can cover sending infrastructure, deliverability, data enrichment, verification, copy, testing, reply handling and meeting booking, while custom GTM systems and private workshops support teams that want to build the capability internally.
H2 helps B2B teams connect deliverability decisions with better targeting, cleaner data and more qualified sales conversations. Visit H2 to discuss your sending setup, audience and outbound workflow, and book a 15-minute introductory call.
