Every dashboard action is an MCP tool your agent can call.Read the docs
Send & Retain

Email deliverability, built into every send

Domain authentication, suppression, and address checks run before each email leaves. Unsafe email is stopped, not just reported.

Start for free

✓Free to start. Unlimited contacts on every tier.

Delivery checks
Deliverability

Refuse unsafe sends first

Details

not yet sent

To[email protected]

From[email protected]

Templatewelcome

Sourceapi

ProviderSend & Retain

Checks before dispatch

  1. DomainSPF · DKIM · DMARC
  2. RecipientAddress verified
  3. SuppressionNo active block
  4. RouteProvider healthy
Controls run again at dispatch

[ 01 / 04 ]Domain setup

How do I set up my sending domain?

Your agent does most of it. You add the DNS records at your DNS host.

  1. Ask your agent to add the domain

    Try: "Set up sending for acme.com and give me the DNS records."

  2. Add the DNS records

    You get several (DKIM CNAMEs, MX and SPF on a mail-from subdomain, and a tracking CNAME). Add them at your DNS host.

  3. Verify

    Once DNS has propagated, your agent checks the records and marks the domain verified.

  4. Add a sender and send a test

    Create a from-address on the verified domain and send yourself a test.

[ 02 / 04 ]Send checks

What runs before every email sends?

01

Verified domain and sender

The from-address must be on a verified domain, or the send is refused.

02

Suppression check

Unsubscribes, hard bounces, and complaints, checked right before it sends.

03

Address verification

A new address is checked once before its first send, so a dead mailbox never bounces.

04

Pause switch and daily cap

Re-checked right before it sends, so even queued email stops when you pause.

05

Unsubscribe headers

A hosted unsubscribe page and one-click unsubscribe headers on every email.

[ 03 / 04 ]Complaints

What happens when someone marks my email as spam?

They're suppressed for good. Nobody, not you, not your agent, not support, can remove a complaint suppression.

  • Hard bounces and complaints suppress future email automatically.
  • If a send count can't be read, the send is refused rather than waved through.
  • The pause switch also stops email that was already queued.
Delivery checks
Deliverability

Refuse unsafe sends first

Details

not yet sent

To[email protected]

From[email protected]

Templatewelcome

Sourceapi

ProviderSend & Retain

Checks before dispatch

  1. DomainSPF · DKIM · DMARC
  2. RecipientAddress verified
  3. SuppressionNo active block
  4. RouteProvider healthy
Controls run again at dispatch

[ 04 / 04 ]Related

Where do these checks matter most?

Transactional email API

Receipts and resets that have to land.

Email analytics

The delivery events behind every bounce and complaint.

Contacts

Where suppression and consent live.

Migrate

Move platforms without gambling your domain's reputation.

Questions people ask us

Protect your domain before the first email leaves.

Verify a domain, send a test, and watch every check run.

Start for freeRead the docs