AI agents for GTM and RevOps · Part 11 of 13
Rolling out an AI SDR: volume, domains and deliverability
What Google, Yahoo and Microsoft ask of senders, what their rules mean for your main domain or a separate one, and a ramp that adds volume only while spam reports, bounces and unsubscribes stay under its gates.
The short version
An AI SDR writes to people who didn’t ask to hear from you, and the spam reports it earns can lower the reputation of the domain it sends from. So meet the mailbox providers’ rules before the first send, choose the domain knowing Google counts its subdomains with it, and add volume a step at a time, only while the numbers stay under gates you wrote down first. Three sections:
What the mailbox providers ask
Google, Yahoo and Microsoft publish what they ask of senders, and they ask more of bulk senders.
Google (Gmail)
- Every sender
- SPF or DKIM; spam rate under 0.3%
- Who is bulk
- close to 5,000 a day to personal Gmail, counted for the whole primary domain; for good, once crossed
- Bulk senders add
- SPF and DKIM; DMARC, p=none will do; one-click unsubscribe, honoured within 48 hours
- Spam rate
- target under 0.10%, ceiling 0.30%; counted daily, on mail that reached the inbox
Yahoo
- Every sender
- SPF or DKIM; spam rate under 0.3%
- Who is bulk
- a significant volume; no number given
- Bulk senders add
- SPF and DKIM; DMARC, p=none will do; one-click unsubscribe, honoured within 2 days
- Spam rate
- under 0.3%, counted on mail delivered to the inbox
Microsoft (Outlook)
- Every sender
- enforcement targets large senders first
- Who is bulk
- a domain sending over 5,000 a day
- Bulk senders add
- SPF, DKIM and DMARC, p=none at least; failing mail is rejected with 5.7.515
- Spam rate
- no figure given
Google’s guidelines say it plainly: “Don’t send messages to people who didn’t sign up to get messages from you. These recipients might mark your messages as spam, and future messages to these recipients will be marked as spam.”
Gmail Help, “Email sender guidelines”A cold message goes to someone who didn’t sign up, so every spam report it earns counts against the sending domain, at any volume. Write only to people with a real reason to hear from you (part 5 writes down who). Give every message a one-click unsubscribe, since Google notes that unwanted messages without one are more likely to be reported as spam, and honour each unsubscribe within 48 hours (part 8 sets out the rule).
Your main domain or a separate one
In February 2026, someone starting cold email for a small SaaS business asked on Hacker News whether to send 30 to 50 a day from the main product domain or a separate outreach domain; two AI assistants had given opposite answers. The providers’ rules don’t decide it, but they show what each choice carries.
example.com and its subdomains
Product mail, from example.com
Marketing, from news.example.com
The AI SDR, from outreach.example.com
One count toward 5,000 a day to personal Gmail. Crossed once, the whole domain is a bulk sender for good.
example.net, a separate domain
The AI SDR, from example.net
Its own count toward 5,000 and its own reputation. A new domain: no history yet.
On your main domain or a subdomain of it, the AI SDR’s mail joins one count with your product and marketing mail: Google’s own example adds 2,500 messages from a domain to 2,500 from its promotions subdomain and calls the sender bulk. On the main domain itself, its spam reports can lower the reputation of a domain that may also carry your invoices and password resets; one reply to the question says cold mail “hurt the deliverability of our transactional emails”. Yahoo asks senders to keep types of mail apart, by IP or DKIM domain: “Sending unsolicited commercial email can negatively affect your reputation.”
A separate domain has its own count, and Gmail tracks feedback per domain, so it builds its own reputation. But it starts with no history, needs its own SPF, DKIM and DMARC, and answers to the same rules.
A ramp with gates
Each mailbox has a ceiling. A Google Workspace user can send 2,000 messages a day, to at most 2,000 outside addresses (500 of each on a trial account), counted over a rolling 24 hours. A Microsoft 365 mailbox can send to 10,000 recipients a day and 30 messages a minute. These are the most a mailbox may send, not a pace to aim for. The 30 a day per inbox in Instantly’s guide is Instantly’s own convention.
Google’s guidance: “Start with a low sending volume to engaged users, and slowly increase the volume over time.” For an AI SDR, start with the contacts who have the strongest reason to hear from you. Google warns that suddenly doubling your volume can bring rate limits or a drop in reputation; if mail starts bouncing or being deferred, it says to reduce volume until the errors fall. Write the ramp and its gates down before the first send, and change one thing at a time, as in support part 11: more volume, a new mailbox or a new segment, one per week.
| Example ramp | A day | Gates |
|---|---|---|
| Week 1 | 20 | passed |
| Week 2 | 30 | passed |
| Week 3 | 45 | passed |
| Week 4 | 60 | bounces 3 in 100 |
| Week 5 | 45 | passed |
| Week 6 | 60 | passed; next, 90 |
Gates, checked each week
- Spam reports
- under 0.1%: at these volumes, none
- Bounces
- under 2 in 100
- Unsubscribes
- under 2 in 100, each honoured within 48 hours
- Errors
- no 4.7.28 or 5.7.515
Any gate missed: back one step until the cause is found.
Count these yourself from day one. Postmaster Tools’ dashboards “might not include all data on days when your outgoing email volume is low”, and their spam rate covers only DKIM-signed mail that reached a personal Gmail inbox, leaving out company inboxes on Google Workspace. Take bounces and deferrals from your sending tool, count unsubscribes and replies asking you not to write again, and enrol your DKIM domain in Yahoo’s Complaint Feedback Loop, which sends you a copy of each spam report from Yahoo users. Leave opens out: “Google doesn’t track open rates.” Part 12 shows how to count it all.
When a gate fails, go back a step and find the cause before climbing again. If Gmail answers 4.7.28, you went over its quota: Google’s page says to send nothing for at least 10 minutes. Outlook’s 5.7.515 means the domain failed authentication, so fix SPF, DKIM or DMARC first.
Next in this series
Part 12: measuring an AI SDR. See all 13 parts.
Sources
- Gmail Help, “Email sender guidelines”, read on 21 October 2026.
- Gmail Help, “Email sender guidelines FAQ”, read on 21 October 2026.
- Gmail Help, “Postmaster Tools dashboards”, read on 21 October 2026.
- Google Workspace Help, “Gmail sending limits in Google Workspace”, read on 21 October 2026.
- Yahoo Sender Hub, “Sender Best Practices”, read on 21 October 2026.
- Yahoo Sender Hub, “FAQs”, read on 21 October 2026.
- Microsoft Defender for Office 365 Blog, “Strengthening Email Ecosystem: Outlook’s New Requirements for High-Volume Senders”, 2 April 2025, updated 29 April 2025, read on 21 October 2026.
- Microsoft Learn, “Exchange Online limits”, updated 19 October 2026, read on 21 October 2026.
- Instantly, “How AI SDRs Work: Technical Architecture Explained”, 26 June 2026, read on 21 October 2026.
- Hacker News, “Outreach domain for personalized cold emails? LLMs don’t agree”, and its first reply, 20 February 2026, read on 21 October 2026.
