Choosing an email service provider: the criteria that affect deliverability

Choosing an email service provider is usually framed around templates, automation, and integrations, but the decision that determines whether your mail actually reaches inboxes comes down to a shorter, less visible list: how the platform handles authentication, IP allocation, and sending reputation.

Shared IP vs dedicated IP

Most ESPs default new accounts to a shared IP pool - you send from the same IP range as other customers on the platform. This is usually the right choice at low-to-moderate volume: the IP already has sending history, and the ESP actively manages the pool's reputation across all its tenants. A dedicated IP only makes sense once you're sending consistently enough (commonly cited as tens of thousands of emails a month) to build and maintain its own reputation - an underused dedicated IP behaves worse than a well-managed shared one, because there isn't enough volume to establish a track record.

Authentication support

Check, before signing up, whether the platform:

• Lets you publish your own domain's DKIM signature (custom DKIM), rather than signing on the platform's shared domain - custom DKIM means your sending reputation builds on your own domain, not the platform's.
• Supports a custom MAIL FROM domain for SPF/DMARC alignment rather than defaulting to the platform's bounce domain.
• Gives you visibility into bounce and complaint rates at the account level, not just aggregate campaign stats - this is the leading indicator of a reputation problem before it becomes a deliverability one.

Warm-up handling

Some platforms warm a new sending domain or IP automatically with ramped sending limits; others leave ramping entirely to you. Either is workable, but know which one you're getting - a platform with no ramping and no warning will happily let you send full volume on day one, which is how a new domain gets filtered within its first week.

Compliance features

For bulk senders specifically, one-click unsubscribe (List-Unsubscribe header) and clear suppression-list handling are now baseline expectations under Google and Yahoo's 2024 sender requirements, not optional extras - check the platform supports both out of the box.

What not to do

• Don't choose based on price per send alone without checking whether dedicated IPs, custom DKIM, or warm-up support are gated behind a higher tier you'll need anyway.
• Don't assume a platform's reputation protects you indefinitely on a shared IP - your own complaint and bounce rate still affects your deliverability within that pool, and a platform can throttle or suspend an account that's dragging the pool down.
• Don't switch ESPs as a first response to a deliverability problem - the new platform inherits the same list and content issues, and a platform switch resets whatever sending history you'd built.

A comparison framework, not a specific platform ranking

Rather than ranking named platforms (which changes constantly as pricing and features shift), use this framework to evaluate whichever ESPs you're considering:

Email account types, briefly, since the choice intersects with this

Broadly, the accounts you're sending from fall into three categories: a personal webmail account (fine for low volume, not built for programmatic sending), a business mailbox on a provider like Google Workspace or Microsoft 365 (suited to moderate volume with good built-in reputation), and a dedicated transactional/marketing ESP (built specifically for programmatic, higher-volume sending with the authentication and reputation tooling that implies). Matching the account type to the actual volume and purpose avoids both over-engineering a low-volume need and under-provisioning a genuinely high-volume one.

A word on consumer webmail as an "ESP" for comparison purposes

Some comparisons of email service providers lump in consumer webmail (Gmail, Yahoo Mail, Outlook.com) alongside dedicated marketing and transactional platforms, since all of them technically let you send email. For a business sending any meaningful volume, consumer webmail isn't a real ESP alternative - it lacks the authentication controls, sending limits are tuned for personal use rather than programmatic sending, and most consumer providers will flag or suspend an account sending at bulk marketing volume regardless of content quality. The comparison is only useful for understanding what a dedicated ESP adds on top of a basic mailbox, not as a genuine option to weigh against one.

Whichever ESP you choose, MailPilot warms the mailbox or domain against a real seed-inbox network before it carries volume and tracks SPF, DKIM, DMARC and per-provider inbox placement daily, independent of which platform is doing the sending.