The Smartlead warmup settings, from Smartlead's own page
Smartlead documents its warmup in the help centre article on its smart-adjusting algorithm. Three settings carry the whole thing: total_warmup_per_day, which Smartlead recommends at 20 to 40 (a new account is capped around 40); daily_rampup, the 2 to 3 extra emails a day the ramp adds; and the algorithm itself, which adjusts the volume from the results. Smartlead puts full ramp at 14 to 30 days.
- For a new mailbox: start at the bottom of the range, keep daily_rampup at 2 to 3, and let the algorithm work. Setting 40 on day one on a domain with no history is what the ramp exists to prevent.
- For an aged mailbox with history: the top of the range is reasonable, and the ramp finishes faster.
- For any mailbox: do not start campaigns until the ramp has run, and test placement before the first send. The ramp completing is not a readiness signal; it is a volume schedule ending.
What the pool does to your reputation
A shared pool is every other Smartlead customer's mailbox, and reputation is judged by the company a mailbox keeps. Two things follow. The pool contains senders you would not choose to be paired with, and you cannot see or choose who they are. And pool warmup is templated, bot-to-bot engagement on a schedule, which is the pattern Google and Microsoft built filters to recognize. Warmup they can detect can count against the domain. That is the whole reason a dedicated warmer exists, and it is the honest answer to “when should I add one”: when the case is hard enough that the pool's weakness shows.
When to add a dedicated warmer
- A brand-new domain. No history to build on; the quality of the first three weeks of engagement decides the domain's standing.
- A domain recovering from spam. Recovery needs the correction pool warmup does not document: mail moved out of spam and marked important.
- A large mailbox set. Thirty mailboxes warming with identical pool behavior look like one script with thirty accounts; thirty AI personas look like a team.
- A placement test that shows spam at one provider. The pool is running and one receiver still says no. That is a reputation problem at that provider, and the fix is stronger engagement there.
Running MailStrike alongside Smartlead
- 1
Connect the mailboxes Smartlead sends from
One-click OAuth for Google Workspace and Microsoft 365, or SMTP and IMAP. Authentication is checked on connection. Each mailbox gets its own AI persona with its own reply rate, dwell time and active hours.
- 2
Set the daily warming volume, keep Smartlead's campaigns running
The plan default is 30 a day per mailbox, full volume by day 21. Warming mail goes only to the MailStrike network and is labelled and archived on arrival.
- 3
Decide about Smartlead's warmup toggle
Both can run; the warmup volumes add up. Most teams turn the pool warmup off once the MailStrike ramp is under way and leave Smartlead to the sequences.
- 4
Read Flashman, then scale the campaigns
Flashman's daily summary recommends a send volume per mailbox; raise Smartlead's limits as it rises, and run a placement test before a large send.
Smartlead sends from the mailbox over its own connection and MailStrike warms it over its own; there is no Smartlead integration in MailStrike and none is needed. The mailbox's provider limits are on the sending-limits pages; none of them is where a campaign actually stops.
Test placement, not the ramp
Smartlead's SmartDelivery placement tests are seven free, then a paid add-on. MailStrike includes placement tests in every warming plan, and the Free Deliverability Test reports inbox, promotions or spam per provider before you commit a list. Whichever you use, run one before the first big send: the ramp finishing tells you the schedule ended, not where the mail lands.
The short version
Smartlead's best warmup settings are the ones its own article gives: 20 to 40 a day, a ramp of 2 to 3 a day, 14 to 30 days to full volume, started low on a new domain. What the settings cannot change is the shared pool and its templated pattern. Add a dedicated warmer when the case is hard, and run it on the same mailboxes with Smartlead untouched.
Questions people ask about Smartlead warmup
What are the best Smartlead warmup settings?
Smartlead's own documentation gives the shape: a total_warmup_per_day of 20 to 40 (a new account is capped at around 40), a daily_rampup of 2 to 3 more per day, and 14 to 30 days to reach the full volume. Start a new mailbox at the bottom of that range, let the ramp add 2 to 3 a day, and do not start campaigns until the ramp has run. The settings Smartlead does not expose, who is in the pool and how the content is written, matter more than the numbers.
How does Smartlead's warmup work?
Your mailbox exchanges warmup mail with a pool of other Smartlead accounts, and a smart-adjusting algorithm raises or lowers the daily volume from the results. It is the same shared-pool model as the other sequencers: engagement from whoever else is on the platform, on a schedule.
How long does Smartlead warmup take?
Smartlead documents 14 to 30 days to full ramp at a daily_rampup of 2 to 3. It does not publish a readiness signal beyond the ramp completing, so test placement before the first send.
What is the Smartlead warmup pool?
The other Smartlead customers' mailboxes your warmup mail is exchanged with. It is shared, and Smartlead does not document who is in it. Reputation is judged by the company a mailbox keeps, which is the shared pool's structural weakness.
When should I add a dedicated warmer to Smartlead?
When the case is hard: a brand-new domain, a domain recovering from spam, a large mailbox set, or a placement test that shows spam at one provider despite the pool warmup running. MailStrike warms the same mailboxes with an AI persona each, with spam rescue and threads written per mailbox, and runs alongside Smartlead's sending with nothing to integrate.
Can I use MailStrike and Smartlead together?
Yes. Both connect to the same Google Workspace or Microsoft 365 mailbox independently. MailStrike warms; Smartlead sends. If both warmups run, the volumes add up, so keep the total where a real person's correspondence would sit; most teams switch the pool warmup off once the MailStrike ramp is under way.