Deliverability

Guardrails that keep your domain out of the spam folder.

Sending volume is easy. Staying deliverable is the hard part — so the limits, the pacing, the suppression, and the compliance headers are built into the engine instead of being your job to remember.

Every burned domain has the same story: someone found a tool that could send faster than their reputation could survive. It works for six weeks and then nothing lands, and the domain you spent years building is worth nothing.

Mercury is deliberately harder to abuse. The limits below are not advanced settings buried in a menu — several of them cannot be turned off at all.

What it does

Hard contact limits

One campaign email per lead per day. One campaign call per lead per day. Across every campaign in the workspace, not per campaign. This is a rule, not a preference.

Your mailbox, your reputation

Mercury sends through your own Microsoft 365 account via Microsoft Graph. No shared IP pool, no relay service you are sharing with strangers whose sending habits you cannot see.

Per-mailbox caps, warm-up, and human pacing

Early access

New mailboxes ramp gradually instead of starting at full volume. Sends are spaced with natural variation rather than fired in bursts, and each mailbox has its own hourly and daily ceiling.

Sending windows in the recipient's timezone

Early access

Business-hours delivery based on where the lead is, not where your server is.

Suppression, unsubscribe, and do-not-call

Early access

A workspace suppression list that every channel checks before it acts. One-click unsubscribe headers on every campaign email. Hard no outcomes from AI calls write to the same list, so a prospect who opts out on the phone stops receiving email too.

Stop-on-reply, everywhere

The best deliverability feature is not emailing people who already answered. Replies — including ones sent from Outlook — freeze the sequence immediately. Bounces stop the lead and record the reason.

Domain health check at setup

Early access

Mercury inspects your SPF, DKIM, and DMARC records when you connect a mailbox and tells you what is missing before you send anything.

How it works

  1. 01

    Connect your mailbox

    Mercury checks your domain records and flags problems before you send.

  2. 02

    Warm up

    New mailboxes ramp toward their ceiling over the first weeks.

  3. 03

    Send inside the rails

    Caps, pacing, windows, and per-lead limits apply to every campaign automatically.

  4. 04

    Stay clean

    Replies stop sequences, bounces stop leads, opt-outs stop everything.

What this replaces

The separate warm-up subscription, and the quarterly conversation about why nothing lands anymore.

Questions people ask

Will Mercury warm up my domain for me?
Mercury ramps your sending volume gradually and paces messages like a person would. It does not run an artificial inbox network that emails other tools seed accounts — those schemes are increasingly detected and increasingly counterproductive.
Can I raise the sending limits?
Per-mailbox caps are configurable within what your plan allows. The per-lead contact limits are not — they protect your prospects, your domain, and every other customer sending from the platform.
Does Mercury add an unsubscribe link?
Yes, with a standards-compliant List-Unsubscribe header on campaign email. In most jurisdictions it is legally required for commercial mail, and it is better than the alternative, which is a spam complaint.
What happens when an email bounces?
The lead is marked bounced, their sequence stops, and the reason is recorded. Repeated hard bounces from a list are a signal to clean the list, and Mercury shows you the rate.
Do voice calls follow the same rules?
Yes. One call per lead per day, the shared suppression list, and do-not-call handling apply to the AI voice agent exactly as they apply to email.