Automatic suppressions
Hard bounces, complaints, provider blocks, unsubscribes, and manual blocks stop future sends to risky recipients.
Deliverability that pauses the risky project, not your whole account.
NoticeAPI reads every bounce and complaint, suppresses the recipients behind them, and ramps new senders up as they build a track record. When reputation slips, sending pauses; once the window clears, healthy senders recover on their own.
- Automatic suppressions
- Hard bounces, complaints, provider blocks, unsubscribes, and manual blocks stop future sends to risky recipients.
- One project pauses, not the rest
- NoticeAPI tracks bounce and complaint rates against plan thresholds and pauses only the affected project during routine incidents.
- Warm-up ramp
- New accounts start with conservative daily sending caps that grow as healthy traffic builds history.
Deliverability controls, not deliverability tricks
Autopilot is a safety system for legitimate transactional and marketing email. It does not promise inbox placement or hide bad traffic; it gives teams real feedback and pauses sends when reputation is at risk.
Pausing is the easy part. Recovery is built in.
Every send feeds one loop that protects production senders: bounce and complaint rates, warm-up ramps, suppressions, automatic pauses, and self-service recovery.
See autopilot behaviorBounces
Bad addresses get suppressed
Hard bounces feed recipient suppression so future sends fail fast.
Complaints
High-risk signals stay reviewed
Complaints and repeat incidents remain blocked until an operator confirms the sender is safe.
Ramp
New senders start conservatively
Daily volume caps grow as healthy production traffic builds history.
Recovery
Healthy senders get a path back
A cleared bounce window starts a small server-controlled probe. Healthy delivery evidence expands capacity automatically.
Protect the route before traffic grows.
- 1
Verify the sender domain
Production sending starts with DNS records for domain ownership, plus SPF and DKIM.
- 2
Send through the shared pipeline
REST, SDK, SMTP, broadcasts, and automations all feed the same health and suppression layer.
- 3
Watch bounces and complaints
Delivery events update metrics and create suppressions so bad recipients stop being retried.
- 4
Recover by risk level
First-time bounce incidents enter controlled probes after the window clears. Healthy outcomes restore capacity; complaints and repeat incidents stay under review.
Controls grouped by the failure they prevent.
One project pauses, not the rest
NoticeAPI tracks bounce and complaint rates against plan thresholds and pauses only the affected project during routine incidents.
Warm-up ramp
New accounts start with conservative daily sending caps that grow as healthy traffic builds history.
Guided recovery
Metrics shows the signal, next evaluation, controlled probe budget, and whether recovery is automatic or needs operator review.
Questions before you ship.
Does autopilot guarantee inbox placement?
No. It monitors real delivery risk, suppresses bad recipients, ramps volume, and pauses unsafe traffic. Inbox placement still depends on sender quality, recipient engagement, and mailbox provider decisions.
Do sandbox sends pause my account?
No. Sandbox and simulator paths are for safe testing. Production traffic is what feeds the account health thresholds.
What happens when a project is paused?
Production sends for the affected project fail with project_paused while sandbox stays available. First-time bounce incidents recover through automatic cooldown and controlled probes; complaints and repeat incidents require operator review.
Read the implementation.
Autopilot docsThresholds, warm-up ramps, account pause behavior, and recovery steps.Domain verificationProve ownership, publish SPF and DKIM, and bring production sender domains online, with DMARC covered as guidance.Suppressions APIManage the recipient safety layer from code.Plan limitsCompare quotas, domains, contacts, and included features.
Test it. Then send for real.
Simulator outcomes are free. Move to a verified domain when the path is ready.