For Smartlead
Inboxes for Smartlead
Mailboxes exported straight into the Smartlead client workspace you name, laid out so one client's scraped list never reaches another client's domain.
Smartlead setup guide on warminboxes.com ↗
Orders are placed on Warm Inboxes, run by the same team as this site.
Warm Inboxes is a Smartlead Partner on the infrastructure side. It sells the mailboxes, not the seats, and exports them into the Smartlead workspace you name.
The layout that keeps clients apart
Smartlead's client workspaces make running several clients workable. Shared infrastructure underneath them is what makes it dangerous: one domain with inboxes in two workspaces, one tracking domain under everybody. Six layers, per client:
| Layer | Per client | Why |
|---|---|---|
| Domains | Their own, 2 to 3 inboxes each | The unit of reputation. Never shared. |
| Mailboxes | Their own, named for their brand | A mailbox sends for one client only. |
| Smartlead workspace | One per client | Reporting, caps and suppression stay separate. |
| Tracking domain | Their own, or tracking off | A shared tracking domain re-joins what you separated. |
| Suppression list | Theirs, plus your global one | Their opt-outs are theirs; yours apply everywhere. |
| Portal order | One folder per client | Exports land in the right workspace; renewals stay legible. |
The first layer is the one that matters. Get the domains right and the rest follows; get them wrong and no Smartlead setting can separate what the receiver already sees as one sender. A new client is a new folder, a new order and a new workspace, with nothing in common with the last one.
Two ways into Smartlead
We export them. Save your Smartlead login once in the portal under sequencer keys, name the workspace on the order, and the mailboxes arrive in it connected. The login is used for every export after that and never shown back.
You import them. If you would rather not store a login, take the credentials from your portal and do it yourself:
- Connect by provider over OAuth. Google mailboxes through the Google path, Microsoft 365 and Azure through the Microsoft path. No stored password, nothing breaks on rotation.
- On Microsoft over IMAP and SMTP, enable SMTP AUTH first. It is off by default on recent tenants and fails looking like a wrong password.
- Bulk import, one file per client. The sequencer CSV converter shapes the credentials for Smartlead. One file per client keeps an account out of the wrong workspace.
- Set display name, signature and daily cap on every mailbox, across the import in one pass.
- Point tracking at the client's own domain, or turn it off.
The daily cap per mailbox
| Platform | Cold emails per inbox per day |
|---|---|
| Google Workspace | 15 |
| Microsoft 365 | 8 |
| Azure, full tenant of 100 | 2 |
| Fresh Azure, 50 per tenant | 4 |
| Fresh Azure, 25 per tenant | 6 |
For an agency the number to watch is not the cap but the creep. A client asks for a push, the cap goes up for a week, and it never comes back down. Make the cap a policy in the onboarding document and size the client's fleet for the volume they actually want with the calculator.
Seeing a problem before the client does
Smartlead's API exposes per-mailbox and per-campaign stats: bounces by domain, replies by mailbox, the account whose numbers moved this week. Pair that with Google Postmaster Tools on every domain sending to Gmail and a weekly blacklist check. When one mailbox slips, pause it so the campaign reroutes, run its bounces through the bounce analyzer to see whether it is the list or the domain, and keep a few spares per client so it is an inconvenience rather than a paused campaign.
What it costs per client
| Billing | Per inbox | Pack of 3 |
|---|---|---|
| Monthly | $8 | $24 |
| 2-Month | $7 | $21 |
| Quarterlybest value | $6 | $18 |
| Billing | Per tenant | Per inbox |
|---|---|---|
| Monthly | $69 | $0.69 /inbox |
| 2-Month | $60 | $0.60 /inbox |
| Quarterlybest value | $50 | $0.50 /inbox |
A typical client launch is a prewarmed order to start sending this week and a fresh order on their own brand to scale on. Microsoft 365 is priced the same as Google; fresh inboxes are on the pricing page.
Questions
Can you load the inboxes into Smartlead for me?
Yes. Save your Smartlead login once in the portal under sequencer keys and name the client workspace on the order. The build ends with the mailboxes exported into that workspace, connected.
Do I have to store my Smartlead login?
No. You can import the mailboxes yourself from the credentials in your portal instead. The steps are the same either way.
What cap should I set per mailbox?
15 a day on Google Workspace, 8 on Microsoft 365, and 2 to 6 on Azure: 2 on a full tenant of 100, which every prewarmed tenant is, and up to 6 on a lighter fresh one. The same figures the calculator sizes fleets on.
Should I run Smartlead warmup?
On fresh inboxes, yes, or a separate warmup tool: we do not warm fresh inboxes, so they need 14 to 21 days of warmup before cold sends and warmup kept running after, counted inside the daily limit. Prewarmed inboxes arrive with their warmup done.
Is Warm Inboxes a Smartlead partner?
Yes. Warm Inboxes is a Smartlead Partner on the infrastructure side: it sells the mailboxes, not Smartlead seats.
Ready when you are
Prewarmed to send the day it arrives, or fresh on your own domain for less. Pick either in the app; if you are not sure which, send us the volume and the market on WhatsApp and we will size it with you.
More detail on warminboxes.com: Smartlead setup guide ↗