For agencies
Inboxes for cold email agencies
One order per client, on domains nobody else sends from. A client's bad week stays theirs, and onboarding the next one is a new order rather than a rebuild.
Agency ops hub on warminboxes.com ↗
Orders are placed on Warm Inboxes, run by the same team as this site.
Why agencies order per client
Agencies rarely lose a client to bad copy. They lose one to a shared fleet: a new client hands over a scraped list, bounces climb on Tuesday, and by Thursday three other clients are asking why replies dropped. What decides whether anyone else notices is whether that client's sending ever touched a domain another client depends on.
The fix is structural and cheap if it is done on day one. Each client gets their own domains, their own mailboxes and their own order, so the blast radius of any one client is that client.
A client, from onboarding to offboarding
| Stage | What you do | Why |
|---|---|---|
| Onboard | Segment their list, size the fleet, place one order in a folder named for them | The fleet matches their market, and nothing is shared from the start |
| Launch | Start on prewarmed inboxes | Campaigns run the week the contract is signed, not three weeks later |
| Scale | Add fresh inboxes on the client's own branded domains | Lower cost per inbox at volume, warming while the prewarmed fleet sends |
| Keep a reserve | A few spare prewarmed inboxes per client | A tired inbox is swapped the same morning, not a paused campaign |
| Offboard | Export their replies and opt-outs, then end their order | Nothing else renews, breaks or loses a domain |
Sizing a typical client
A client who wants 500 cold emails a day needs this, depending on where their prospects sit:
| Platform | Inboxes for 500 a day | Domains or tenants |
|---|---|---|
| Google Workspace | 34 | 12 domains |
| Microsoft 365 | 63 | 1 domain |
| Azure, full tenant of 100 | 250 | 3 tenants |
| Fresh Azure, 25 per tenant | 84 | 4 tenants |
Rounded up to whole inboxes and whole domains. The calculator does the exact arithmetic for any volume, including the domain cost.
Run their list through the ESP segmenter during onboarding and size against the split it shows. Most B2B lists justify a mix.
Rules worth putting in the onboarding document
- The cap is policy, not a dial. A client asks for a push, the cap goes up for a week and never comes back down. More volume means a bigger order.
- One tracking domain per client, or none. A shared tracking domain re-joins everything you separated.
- Their suppression list plus yours. Their opt-outs are theirs; your global list applies to every client. The suppression checker runs a list against both.
- Every list verified before upload. The email verifier and CSV cleaner are free.
- One warmup per inbox. Fresh inboxes need your own warmup tool, from about $97 a month, for 14 to 21 days before cold sends. Run one warmup, not two, and count it inside the daily limit.
Built for running many clients
- Each domain in its own isolated workspace, so isolation is real at the infrastructure level, not just a folder name.
- You are admin on every tenant, so a client's mailboxes never depend on someone else answering a message.
- Connected to your sending tool for you if you want, and on Smartlead exported straight into the client workspace you name. The Smartlead layout covers it step by step.
- API and MCP access, so onboarding the tenth client is a script rather than an afternoon.
Questions
Should every client have their own domains?
Yes, always. The domain is the unit of reputation. The moment two clients send from one domain, one client's list quality can damage the other's placement, and no sequencer setting can separate what the receiver already sees as one sender.
Can I order for many clients from one account?
Yes. Place one order per client, in a folder named for them. Renewals stay legible, exports land in the right sequencer workspace, and ending a client is ending one order.
Can I automate client onboarding?
Yes. Everything the dashboard does is also available over the API and an MCP server, so a new client can be ordered and set up from your own tooling or an AI agent.
What daily cap should I promise a client?
The one the fleet can hold for months: about 15 per Google inbox and 8 per Microsoft inbox. Write it into the onboarding document so a push for more volume becomes a bigger order, not a higher cap.
How do I spot a problem before the client does?
Watch bounces by domain and replies by mailbox every week, keep Google Postmaster Tools on every domain with Gmail volume, and run a weekly blacklist check. A slipping inbox is then a Monday item rather than a client email.
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: Agency ops hub ↗