Agent 03 · AI SDR Engine
Inbox Operator: cold email deliverability that lands in primary, not spam
The unsexy plumbing layer that decides whether anything else in your AI GTM engine matters. Most teams skip it. Their reply rates tell on them.
You can have the smartest Sequence Composer in the world. If the email lands in spam, none of it matters. Inbox Operator is the agent that owns the wire — part of the complete AI GTM engine guide.
What Inbox Operator owns
- Provisioning dedicated sending domains (separate from your primary brand domain).
- Configuring SPF, DKIM, DMARC, MX, and BIMI records.
- Running 14–21 day automated warmup loops before any inbox sends real cold mail.
- Rotating across inboxes and domains as volume scales.
- Monitoring deliverability per provider (Gmail, Outlook, Yahoo) and bounce rates per inbox.
- Auto-rotating or pausing inboxes when reputation drops, before the damage spreads.
The authentication requirements aren’t arbitrary — they’re published. Google’s email sender guidelines mandate SPF, DKIM, and (for bulk senders) DMARC, plus a spam-complaint rate under 0.3%. Inbox Operator configures every sending domain to clear that bar before the first cold send.
Why this is the agent founders skip and regret
The economics are brutal: 1 day of bad deliverability burns the warmup investment of the previous 3 weeks. Recovery takes another 3–6 weeks. Meanwhile your sequences are running and your prospects are silently not seeing them.
Founders skip Inbox Operator because the work is invisible when it’s done right. There is no flashy dashboard. No “wow” moment in the demo. Just the absence of a problem the team didn’t know they were going to have.
Stack & integration
Built on Smartlead (or Instantly / Mailreef) for the sending infrastructure, plus custom monitoring code that watches placement-rate signals across providers and pulls inboxes that drop below threshold. Sending domains are provisioned via Cloudflare or Vercel — DNS records are versioned in your repo.
Common failure modes
- Using primary brand domain for outbound (kills delivery for the whole company).
- Skipping warmup to ship faster (burns the domain in week 1).
- Monitoring blended deliverability instead of per-provider (Outlook drops invisibly).
- No bounce-rate threshold (one bad list segment poisons the inbox).
FAQ
Why can't I just use my real domain for outbound?
You can, and Google will eventually flag your domain for cold sending volume. Once flagged, every email from anyone at your company (sales, support, exec) starts landing in spam. Inbox Operator uses dedicated sending domains so your primary brand domain stays clean.
How many sending domains do I need?
Depends on volume. Rule of thumb: 30–50 emails/day per inbox, 3 inboxes per domain, 1 domain per 100–150 emails/day in steady state. We provision and warm a pool sized to your sprint plan.
How long does warmup actually take?
14–21 days of automated warmup before you can send cold at full volume. Inbox Operator runs the warmup loop in parallel with the rest of the sprint, so you’re ready to scale on day 14.
What about Microsoft 365 / Outlook prospects?
Outlook has stricter authentication signals than Gmail (SPF/DKIM/DMARC enforcement is harder). Inbox Operator monitors per-provider placement, not just blended. If Outlook rates drop, it auto-rotates inboxes before damage spreads.
Sources & further reading
- [1]Google — Email sender guidelines
Google's official requirements for SPF, DKIM, DMARC, spam rate, and bulk sender authentication — the spec Inbox Operator configures against.
- [2]DMARC.org — DMARC overview
Authoritative reference on DMARC alignment and policy, one of the records Inbox Operator provisions per sending domain.
Ship Inbox Operator before you ship outreach
14-day sprint warms the inboxes in parallel with the rest of the build. Ready to scale on day 14.
Book live demo on your dataRelated: Intent Watcher · Sequence Composer · Reply Triager