An email deliverability consultant is an outside specialist you bring in when your mail is not reaching the inbox and your own team has run out of explanations. The search is common among ecommerce stores, software companies, publishers and agencies that have seen open rates collapse, been blocked by a major mailbox provider or are about to move a large programme to a new platform. Hiring the right person can save weeks of guessing. Hiring the wrong one can cost money, delay the real fix and, in the worst cases, make things worse by following tactics that break provider rules. This guide explains what a consultant or audit actually covers, what you should prepare, how to write a scope, which questions to ask, what a good deliverable looks like, which promises should worry you and how to judge the result. We also run a deliverability audit ourselves, so you should weigh our view accordingly. The principles below apply to any provider. For the wider buying picture, see what a deliverability service includes.
What a deliverability consultant does
A consultant reads the signals mailbox providers use to judge you and tells you which are weak and what to change. In practice that is a mix of technical review, data analysis and advice on practices.
- Authentication and DNS review. SPF, DKIM, DMARC, reverse DNS, TLS and the alignment between your visible From domain and the domains that sign and send. See authenticating your sending domain.
- Reputation analysis. Blocklists, provider dashboards such as Google Postmaster Tools, complaint and bounce patterns, and trends by mailbox provider. See Postmaster Tools setup.
- List and acquisition review. Where addresses come from, how consent is collected, how old segments are handled and how bounces and complaints are processed.
- Content and template review. Links, images, tracking domains, wording, structure, unsubscribe handling and rendering.
- Infrastructure and sending patterns. IP and domain strategy, warm-up, throttling, stream separation and retry behaviour. See separating transactional and marketing streams.
- Remediation planning. A prioritised list of changes, who should make them and how to know they worked.
- Incident support. Help understanding block messages, contacting providers appropriately and getting through delisting processes. See why emails get blocked.
Audit, consulting retainer or managed service?
| Engagement | Typical shape | Best when |
|---|---|---|
| One-off audit | Fixed scope, a report and a call | You want a diagnosis and can make the changes yourself |
| Short project | A defined problem such as a platform move or warm-up plan | You have a specific event with a deadline |
| Retainer | A set amount of advice or review each month | You have an ongoing programme and an in-house team that needs guidance |
| Managed service | The provider runs part of the programme for you | You lack in-house capacity and the risk of mistakes is high |
Most teams do best starting with an audit. It gives you a baseline, shows whether the problem is technical or behavioural and lets you judge the consultant before committing to more.
What to prepare before you talk to anyone
- A clear problem statement. Which providers are affected, which streams, since when and what changed around that time.
- Sending overview. Domains, subdomains and IPs, sending platforms, approximate volumes and the types of mail.
- Authentication details. Your current DNS records and DMARC policy. Run the free checker first.
- Data exports. Bounce, complaint and engagement data by provider and campaign, and any block messages.
- List sources. How people get on your list and how consent is recorded.
- Examples. Recent messages that landed in spam and ones that did not, with full headers. See how to read email headers.
- Access plan. Who can grant read access to your platform and DNS, and what you are comfortable sharing.
How to write the scope
A scope that you can hold someone to has five parts.
- Objectives. Plain statements such as "identify the cause of Gmail spam placement for our marketing stream" rather than "improve inbox rate".
- Activities. What will be reviewed or tested: DNS, headers, sample messages, platform settings, list processes.
- Deliverables. A written report, a prioritised action list, a call to walk through it, a follow-up review after changes.
- Timeline. Start, delivery date and the point of follow-up.
- Boundaries. What is not included, such as implementing changes in your platform or contacting your customers.
Questions to ask a consultant
- What would you look at in the first week, and what do you need from us?
- How do you separate infrastructure problems from list or content problems?
- Can you show an anonymised report so I can see the level of detail?
- What happens if the root cause is outside your control?
- Which sending platforms have you worked with?
- Who will do the work, and who is my contact?
- How do you treat access to our systems and data, and how is it removed afterwards?
- What would you refuse to do?
The last question is revealing. A responsible consultant will decline to help with purchased lists, deliberately hidden unsubscribe options, rotating domains to dodge blocks or similar tactics. Our guide to Gmail and Yahoo bulk sender requirements shows the baseline that any recommendation should meet.
What a good deliverable looks like
- Findings written in plain language, each tied to evidence from your data or configuration.
- A severity or priority for each finding and an estimate of effort.
- Specific changes, such as the exact DNS adjustment or the process to adopt, not just "improve authentication".
- An explanation of what the consultant could not determine and why.
- A plan for measuring the result, including which metrics should move and over what period.
- A follow-up review after you have made the changes.
Red flags
- Guaranteed inbox placement, a fixed percentage or a promised delisting date.
- A recommendation before looking at your data.
- "Secret" techniques or mailbox-provider contacts that bypass filters.
- Advice to use purchased or scraped lists, warm-up networks or fake engagement.
- Reluctance to put the scope in writing.
- Pressure to sign before you have seen a sample deliverable.
Judging the result
Deliverability changes slowly. After fixes, mailbox providers take time to update their view of you, so judge outcomes over weeks rather than days. Track the same measures before and after: bounce rate, complaint rate, Postmaster reputation, spam placement tests on your own mailboxes and engagement by provider. See bounce rate guidance. If a consultant's advice is sound but results lag, check whether the underlying causes, such as list quality, have actually been addressed. Our reputation monitoring can help you watch the trend, and the reputation guide explains the signals.
Do some of it yourself first
Much of the first week of any engagement is spent finding basic faults. If you complete the checks in the deliverability service guide beforehand, you will pay for deeper analysis, not for discovering that a DKIM record is missing.
Get a clear diagnosis first Our deliverability audit reviews authentication, reputation and sending practices and gives you a prioritised list of fixes.
References and further reading
Frequently asked questions
What does an email deliverability consultant do?
They review authentication, reputation, list and content practices and sending patterns, identify why mail is missing the inbox and give a prioritised remediation plan.
Should I start with an audit or a retainer?
An audit is usually best first. It gives a baseline and shows whether the cause is technical or behavioural, and lets you judge the consultant before committing further.
Can a consultant guarantee inbox placement?
No. Providers do not publish their filters and no consultant controls them. Guarantees are a red flag.
What should I prepare before an audit?
A problem statement, a sending overview, DNS records, bounce and complaint data, list source details, example messages with headers and a plan for access.
How long before I see results?
Mailbox providers update their view slowly, so judge results over weeks and compare the same metrics before and after changes.