Why Volume-Priced AI SDRs Burn Your Domain

BOSRAI sells an AI SDR and sends email for its customers, so it has a stake in this argument and its own weak points, which are in the last section. Every threshold below comes from Google, Yahoo, Microsoft or M3AAWG, with links at the bottom. Vendor guidance is labelled as vendor guidance.

Most of the damage an outbound tool can do to you does not show up on an invoice. It shows up months later, when your invoices, contracts and replies to real customers start landing in spam, because the domain they come from spent a quarter sending too much to people who did not want it.

That damage has a mechanism, and the mechanism has become much less forgiving since 2024.

The rules changed, and they now reject rather than filter

Google. Since February 2024, Google's sender guidelines ask every sender to authenticate with SPF or DKIM and keep user-reported spam rates in Postmaster Tools below 0.3 percent, with a recommended target below 0.10 percent. Google says spam rates above 0.1 percent already hurt inbox delivery for bulk senders. A bulk sender is anyone sending close to 5,000 messages or more to personal Gmail accounts in a day, subdomains count toward the parent domain, and once you are classed as a bulk sender, that status does not expire. Bulk senders must also pass SPF, DKIM and DMARC and support one-click unsubscribe as defined in RFC 8058.

From November 2025, Google said it was ramping up enforcement on non-compliant traffic, including temporary and permanent rejections. That is the important change. A message that used to go to spam can now simply be refused.

Yahoo. Yahoo's requirements, enforced from February 2024, mirror Google's: authentication for everyone, a complaint rate below 0.3 percent, and for bulk senders DMARC, one-click unsubscribe and unsubscribes honoured within two days. Yahoo declines to publish a volume threshold for who counts as a bulk sender.

Microsoft. Outlook.com, Hotmail and Live treat a domain sending 5,000 or more messages a day as high volume. Those senders must pass SPF and DKIM, publish DMARC at least at p=none, and align one of them with the From domain. Mail that fails is rejected with error 550 5.7.515. Microsoft announced the requirements in April 2025, and outside reporting says rejection replaced the original plan of routing to junk from May 2025.

Reputation is shared, slow and increasingly invisible

A domain's reputation is the history of how people treated its mail. Google's own descriptions of its former reputation tiers were blunt: mail from a domain rated Bad is almost always marked as spam or rejected.

Three properties make that history dangerous for outbound.

It is shared. M3AAWG's Sender Best Common Practices, updated in August 2026, warn that when a shared domain is blocked because of one sender's poor practices, delivery for unrelated senders on it can suffer, and that sharing an IP means sharing its reputation. Every user of a shared sending domain inherits everyone else's behaviour.

It recovers slowly. Google does not publish how long reputation takes to recover. The closest it gets is that a sender who lost eligibility for mitigation must keep its spam rate below 0.3 percent for seven consecutive days to regain it, and that its dashboards can take up to a week to update.

It is getting harder to see. Google has announced it will retire the domain and IP reputation dashboards in Postmaster Tools, saying reputation changes are slow to reflect and are only one of many factors. The number you used to check is going away.

What volume pricing rewards

Look at how sales tools charge. Some charge per email sent. Some charge per LinkedIn or email sender connected. Some charge credits consumed per action. Our AI SDR pricing index lists the units for 16 vendors.

None of that is sinister. But it means the vendor's revenue grows with the thing that grows your risk. A tool paid per send has no commercial reason to tell you to send less, and the features that would protect you, lower caps, slower warm-up, pausing on complaints, cost it money. That is the conflict worth naming before you sign, because it is invisible in a demo.

How much is too much

There is no official number of cold emails per mailbox per day. There is guidance.

M3AAWG, the industry body that writes sending best practice, advises starting low and slow, suggests six weeks of warm-up as an average for a new sending domain, and asks senders to keep volume consistent rather than letting it vary abruptly.

Vendor guidance, all from companies that sell sending tools:

The spread is itself the lesson: even vendors whose revenue depends on volume recommend daily numbers most people would call small.

More volume, fewer replies

Volume does not only risk the domain. It tends to lower the result.

Woodpecker's analysis of more than 20 million emails found reply rates of 5.8 percent for campaigns under 50 contacts against 2.1 percent for campaigns of 500 to more than 1,000. Belkins, analysing about 7.5 million cold emails sent through 2025, reported an average reply rate of 0.45 percent and that lower send volumes produced higher reply rates. Instantly's 2026 benchmark, drawn from its own platform, puts the average at 3.43 percent. These studies measure differently and should not be compared with each other, but they point the same way.

And AI makes volume cheap

Barracuda, working with researchers at Columbia University and the University of Chicago, reported that by April 2025 about 51 percent of spam was generated by AI, used mainly to produce volume and test variations of wording. When writing a thousand messages costs nothing, the only remaining brake on sending them is the sender's judgement or the tool's design.

One thing we did not find, and want to be clear about: no mailbox provider has said it filters AI-written sales email as such. The risk is not that the writing is detected as AI. It is that AI makes it trivially easy to send the volume and sameness that the existing rules already punish.

A checklist before you let any tool send for you

1. Authenticate everything. SPF, DKIM and DMARC on every sending domain, aligned with the From address.
2. Never send outbound from the domain that sends your invoices. Use a separate domain or subdomain, remembering that Google counts subdomains toward the parent.
3. Cap per mailbox and spread across mailboxes, well inside the vendor guidance above.
4. Warm new mailboxes and domains over weeks, not days.
5. Honour one-click unsubscribe and remove the person everywhere.
6. Stop on bounces and complaints automatically. A human noticing next week is too late.
7. Ask the vendor what it does when your complaint rate rises. If the answer is nothing, the pricing model has already told you why.

Where BOSRAI stands, including the weak points

BOSRAI prices on verified contacts, not on emails sent or senders connected. That removes the direct incentive to push sends, but it is still a volume unit, and a customer who wants to email all 25,000 contacts on a plan can try. So the protection has to be in the product:

• Per-mailbox daily caps, with volume spread across every connected mailbox.
• Gradual warm-up. A newly connected mailbox starts at 5 emails a day and ramps to its cap over 21 days. That is faster than M3AAWG's six-week average for a new domain, which is a reason to connect a domain that already has some history.
• Automatic pause of a mailbox when bounces rise, and catch-all addresses parked rather than guessed at.
• One-click unsubscribe and List-Unsubscribe headers on every message, honoured immediately.
• Plain text with a plain HTML twin, the way a person's mail looks, and no tracking pixel at all for contacts in France and Italy.

The weak point is the one M3AAWG describes. The sending address BOSRAI includes so customers can start on day one sits on a shared domain, so its reputation is shared. That is why each of those shared addresses is capped low, and why we tell customers that real volume belongs on their own mailbox and their own domain. If you are evaluating any AI SDR, ask the same question of it: whose domain is this going out from, and who else is on it?

Sources

Mailbox providers: Google email sender guidelines, Google sender guidelines FAQ, Gmail enforcement update, Postmaster Tools reputation dashboards, Postmaster Tools changes, Yahoo sender best practices, Yahoo sender FAQ, Microsoft on error 550 5.7.515, Microsoft announcement, April 2025, dmarcian on Microsoft enforcement, RFC 8058.

Industry practice: M3AAWG Sender Best Common Practices, August 2026, M3AAWG Sending Domains Best Common Practices.

Vendor guidance and research: Instantly account limits, Smartlead on daily volume, lemlist on daily volume, Woodpecker on daily volume, Woodpecker cold email statistics, Belkins cold email response rates, Instantly cold email benchmark 2026, Barracuda on AI-generated spam.

All sources read 14 September 2026.