
Email service provider matching — usually called ESP matching — means sending each prospect an email from a mailbox hosted on the same provider they use: Google Workspace to Gmail and Google Workspace recipients, Microsoft 365 to Outlook and Microsoft 365 recipients. Sequencers such as Instantly, Smartlead, Lemlist and others now offer it as a setting. Most guides explain the feature. This one focuses on the decision underneath it: how to choose and size the right sending infrastructure so ESP matching actually has inboxes to route through, when matching is worth it, and why it only works after the basics — authentication, list hygiene and sensible volume — are in place.
Email Service Provider Matching: The Short Answer
ESP matching routes each lead to a sending inbox on the same provider as the recipient. To use it you need both Google Workspace and Microsoft 365 inboxes in your pool, sized to the share of your list on each provider, all on secondary domains with SPF, DKIM and DMARC. Matching is a placement lever, not a fix for bad lists or high volume.
Recipient's provider | Matched sending inbox | Notes |
|---|---|---|
Gmail / Google Workspace | Google Workspace | Most SMBs, startups |
Outlook.com / Microsoft 365 | Microsoft 365 | Many enterprises and regulated sectors |
Other / custom gateways | Either, or a third provider | Check MX records; some use security gateways |
How ESP Matching Works in Practice
Identify the recipient's provider. Tools check each lead's domain MX records to see whether mail is hosted by Google, Microsoft or something else.
Route the lead. The sequencer assigns the lead to an inbox on the matching provider.
Send within each inbox's limits. Per-inbox caps still apply.
Fall back sensibly. When no matching inbox has capacity, tools either wait or send from another provider — check your settings.
Instantly's help centre notes that if you don't have enough sending accounts on each provider, matching options shrink — the infrastructure question this guide focuses on.
How to Size a Matched Infrastructure
Work out your list's provider split first, then size each side:
Step | Example |
|---|---|
1. Daily sends needed | 750 sends/day |
2. Provider split of list (from MX lookup) | 55% Google, 40% Microsoft, 5% other |
3. Sends per provider | ≈413 Google, ≈300 Microsoft, ≈37 other |
4. Inboxes at ~25/day | 17 Google Workspace, 12 Microsoft 365, 2 for others |
5. Add 20–25% spare | ≈21 Google, ≈15 Microsoft, 2–3 other |
6. Domains (2–3 inboxes each) | ≈12–18 domains, split by provider |
LiteMail plans assume about 25 sends per inbox per day, a useful benchmark (see plan limits). Size and cost it with how many inboxes you need and the pricing calculator.
When ESP Matching Helps — and When It Doesn't
Situation | Matching value |
|---|---|
Mixed list of SMB and enterprise contacts | High — both providers well represented |
Outlook-heavy industries (engineering, consulting, IT) | High — Microsoft 365 matters |
Almost all recipients on Google | Low — mostly Google anyway |
High bounce rate or unverified list | None until the list is clean |
Missing DKIM or DMARC | None until authentication is fixed |
Volume too high per inbox | Limited — fix volume first |
Industry guides on Outlook-heavy audiences: engineering firms, consulting, IT and MSPs.
Setting Up ESP Matching Step by Step
Add both providers. Provision Google Workspace inboxes and Microsoft 365 inboxes on separate secondary domains.
Authenticate everything. SPF, DKIM and DMARC on every domain; Microsoft 365 DKIM needs CNAMEs plus a portal toggle (guide).
Warm or use pre-warmed inboxes. Pre-warmed Google Workspace and pre-warmed Microsoft 365 accounts start with history.
Connect by OAuth. See Google Workspace + Smartlead and Microsoft 365 + Smartlead.
Enable matching in your sequencer at campaign or workspace level.
Verify your list before launch (verification tools).
Monitor by provider — Postmaster Tools for Gmail, bounce logs for Outlook (Outlook troubleshooting).
Common ESP Matching Mistakes
⚖️Unbalanced pools
10 Google inboxes and 1 Microsoft inbox means Outlook leads queue or get sent from the wrong provider.
🧱Ignoring security gateways
Some companies route mail through gateways; MX may show a gateway rather than Google or Microsoft.
🔐Weak Microsoft setup
Microsoft 365 inboxes without DKIM undermine the point of matching (common mistakes).
📈Matching instead of fixing volume
Matching doesn't excuse high per-inbox volume.
🏠Primary domain use
Matched or not, cold email belongs on secondary domains (domain setup).
How to Find Your List's Provider Split
Before buying inboxes for email service provider matching, measure your list. Look up each recipient domain's MX records: Google-hosted domains point to Google's mail servers; Microsoft 365 domains point to Microsoft's. Many sequencers and data tools do this automatically. Some domains sit behind security gateways, which hide the underlying provider — treat those as "other" and test placement.
Industry (typical tendency — verify with your own data) | Plan for |
|---|---|
Startups, tech SMBs, agencies | Google-heavy pools (Google Workspace for B2B) |
Enterprise, engineering, consulting, IT/MSP | More Microsoft 365 (engineering, IT companies) |
Recruiting | |
Private equity, finance | Often Outlook (private equity guide) |
Then size each side with spare capacity, and use pre-warmed domains if you need the Microsoft side live quickly. If matching doesn't move results, check fundamentals: why cold emails go to spam and Postmaster data. Agencies should size per client (inboxes per client) and keep clients in separate workspaces.
Build a Matched Pool With LiteMail
LiteMail | Google Workspace + Microsoft 365 in one place
Fresh from $2.50/inbox
Both providers, automated DNS, dedicated US and EU IPs
LiteMail provisions both Google Workspace and Microsoft 365 inboxes with SPF, DKIM and DMARC configured automatically — including the Microsoft DKIM step — so you can build a balanced pool for ESP matching and export it by OAuth to your sequencer. Fresh or pre-warmed.
Strengths | Keep in mind |
|
|
Deciding the mix? Read Google Workspace vs Microsoft 365 for cold email, why Microsoft 365 for outbound and Google Workspace pros and cons. For AI-driven outbound, see AI outbound infrastructure.
Match every prospect's provider with authenticated inboxes on both sides. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What is email service provider matching?
It is sending each prospect an email from a mailbox on the same provider they use — Google Workspace to Google recipients, Microsoft 365 to Outlook recipients.
Does ESP matching improve deliverability?
Sequencer vendors report better placement when sender and recipient providers match, but results depend on authentication, list quality and volume.
How do tools know a recipient's provider?
They usually check the recipient domain's MX records to see where mail is hosted.
How many Microsoft 365 inboxes do I need?
Size them to the Microsoft share of your list. A 40% Outlook list needs roughly 40% of daily sends from Microsoft 365 inboxes plus spare.
Which sequencers support ESP matching?
Instantly, Lemlist, SmartReach, QuickMail and others document ESP matching features. Check your tool's help centre.
Is ESP matching worth it for a small team?
If your list is mixed and you send meaningful volume, yes. If nearly all recipients use one provider, focus on that provider.
Can I match providers using one domain?
Use separate domains per provider so DNS and reputation stay clean and easy to manage.
What should I fix before turning on ESP matching?
Authentication, list verification and per-inbox volume. See the deliverability guide.
Match Providers Without the Setup Headache
Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Both providers · Automated DNS · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Google Workspace vs Microsoft 365 · Microsoft 365 Cold Email Setup · Google Workspace Domain Setup · Safe Sending Limits · Inbox Network Size and Reputation · Bulk Email Inboxes


