Smartlead Per-Domain Throttling for Cold Email: 2026 Operator Guide
By Puzzle Inbox Team · May 22, 2026 · 7 min read read
Smartlead per-domain throttling for cold email is the single biggest deliverability lever most teams ignore. Here is how to configure it without tanking volume.
Smartlead per-domain throttling for cold email caps sends per recipient domain so you don't trip enterprise spam filters.
Smartlead per-domain throttling for cold email exists because hitting a single recipient domain with 200 messages in an hour from your sending pool is the fastest way to land on Microsoft's tenant-level blocklists. The feature lives under campaign settings, defaults to unlimited, and is the first thing experienced operators change after importing a list.
The mechanic is simple: Smartlead inspects the recipient domain on every outbound message and enforces a ceiling per hour, per day, or per campaign. When the cap hits, messages queue rather than sending, spreading the load across days.
Why the default is wrong for almost every campaign
The unlimited default exists because Smartlead doesn't know your list shape. If you imported 10,000 leads with 4,000 of them at @microsoft.com, the default sends as fast as your pool allows, which Microsoft's filters interpret as a directed spam attack. Reply rates collapse within 48 hours, and your sending domains pick up M365 reputation hits that take weeks to recover.
The fix is to set per-domain throttling based on recipient concentration. Pull a histogram of your list by recipient domain. Any domain holding more than 1% of total volume needs explicit throttling.
Recommended throttling values by recipient type
For enterprise tenants (microsoft.com, google.com, salesforce.com): 5-10 messages per day maximum across your entire sending pool. For mid-market shared M365 tenants: 15-25 per day. For Google Workspace SMB: 20-40 per day. For unique domains with single mailboxes: no cap needed. These numbers come from observing reply rate degradation across 2026 campaigns, not Smartlead documentation.
Pair these with your warmup configuration so throttled campaigns don't starve mailboxes of send volume needed to maintain reputation.
How throttling interacts with sending pool size
Per-domain throttling is independent of mailbox count, which trips up teams. Adding 50 more inboxes does not raise your per-domain ceiling. The throttle is recipient-side, not sender-side. If you need to push more volume into a single recipient domain, the answer is more days, not more mailboxes. Smartlead documents this in their API but not their UI, which is why operators discover it the hard way.
This is also why Clay-driven hyper-targeted campaigns work better than broad blasts in 2026. When your list naturally diversifies across thousands of recipient domains, per-domain throttling barely activates. See Clay workflows for list construction patterns.
The hidden interaction with reply handling
Throttling applies to initial sends but not to follow-ups by default. If you have a 5-step sequence and 4,000 microsoft.com leads, your follow-ups will hammer Microsoft on day 4 even though initial sends were properly throttled. Enable "throttle follow-ups" in advanced settings, or stagger your campaign launches so follow-ups distribute across the week.
Operators running pre-warmed pools from Puzzle Inbox report cleaner throttling behavior because the inboxes have established M365 trust, but the recipient-side ceiling still applies regardless of sender reputation.
Diagnostic: is your throttling actually working
Check the campaign analytics view and filter by recipient domain. If your top 5 recipient domains show send volumes proportional to their share of the list, throttling is off or misconfigured. If the top 5 show flattened, capped volume curves with longer campaign duration, throttling is working. Reply rate per recipient domain should also flatten rather than spike-and-die.
For multi-workspace setups, throttling does not coordinate across workspaces by default. Two separate Smartlead workspaces hitting the same recipient domain will double your effective volume. Consolidate or use the unified workspace feature.