Agency Email Warm Up: One Account per Client
For agency email warm up, create one BobWork account per client: 3 mailboxes are free, 100 cost $194/month, 200 cost $394/month, and 500 cost $994/month on a new account. If you mix clients in one setup, DNS, pool mode, spam-rate decisions, and reports become harder to audit. This guide shows the per-client model, CSV import, ramp maths, pool choice, and fleet checks.
Use this model when you manage cold email infrastructure for different companies. Each client gets its own mailbox list, domain checks, warm-up pool mode, billing view, and readiness report. For a broader operating model, see our guide to email warm-up for agencies.
This page assumes you have dozens or hundreds of mailboxes to connect. If you only manage one or two inboxes, the same rules apply, but CSV import and private-pool decisions matter less.
What does agency email warm up cost?
BobWork Email Warm-up is free for up to 3 mailboxes on new accounts. That free allowance applies per person or per company domain. Several logins on the same company domain share one free 3. Personal providers like gmail.com count per account.
Extra mailboxes are priced by volume. The rate applies to all paid extras, not only the mailbox above the threshold. That creates two price cliffs: 13 total mailboxes and 53 total mailboxes.
For a new account, the cost is:
| Total mailboxes | Free mailboxes | Paid extra mailboxes | Monthly cost |
|---|---|---|---|
| 3 | 3 | 0 | $0 |
| 5 | 3 | 2 | $10 |
| 10 | 3 | 7 | $35 |
| 12 | 3 | 9 | $45 |
| 13 | 3 | 10 | $30 |
| 20 | 3 | 17 | $51 |
| 25 | 3 | 22 | $66 |
| 50 | 3 | 47 | $141 |
| 53 | 3 | 50 | $100 |
| 100 | 3 | 97 | $194 |
| 150 | 3 | 147 | $294 |
| 200 | 3 | 197 | $394 |
| 300 | 3 | 297 | $594 |
| 500 | 3 | 497 | $994 |
| 1,000 | 3 | 997 | $1,994 |
The 13-mailbox row is cheaper than 12 because the extra-mailbox rate changes from $5 to $3 once you have 10 paid extras. The 53-mailbox row is cheaper than 50 because the rate changes to $2 once you have 50 paid extras.
Paid extras are billed by Stripe, prorated, and can be cancelled any time. Extras pause without billing. Yearly billing is available for extra mailboxes at 10 times the monthly price, which gives two months free.
The default account limit is 200 mailboxes. Larger fleets, such as 500 or 1,000 mailboxes, can get a higher limit on request via info@bobwork.ai. For worked examples, see the 500-mailbox warm-up guide or the 1,000-mailbox cost guide.
Should each client have one account?
Yes, use one account per client when you manage infrastructure for different companies. It keeps the client’s mailboxes, sender domains, DNS checks, pool mode, billing, and warm-up history in one place.
It also makes reporting cleaner. You can show that a client’s domains have SPF, DKIM, and DMARC in place. You can show which mailboxes are healthy, on watch, at risk, or blocked. You do not need to filter a mixed agency dashboard.
Use this structure:
| Client setup | Recommended account model | Why it works |
|---|---|---|
| One client, 3 or fewer mailboxes | One client account | Free on a new account |
| One client, 10–50 mailboxes | One client account | Separate DNS and spam-rate reporting |
| One client, 50+ mailboxes | One client account, consider private pool | Enough internal volume for client-only warm-up |
| Many clients with different domains | One account per client | Keeps domains, billing, and readiness separate |
| One client with many sender domains | One account for that client | DNS checks still show per domain |
The free allowance belongs to the person or company domain, not to one agency operator duplicating the same company identity. If the client should own the setup, have the client’s company domain or authorised owner control the account.
Separate accounts also reduce mistakes. You do not want to pause a mailbox for Client A because Client B’s domain has a DNS issue.
How do you import mailboxes?
For bulk onboarding, use the CSV importer instead of adding mailboxes one by one. In the dashboard, go to Add mailbox → Many mailboxes: upload a CSV.
You can paste rows or upload a file. The CSV columns are:
| Column | Required | What to enter |
|---|---|---|
| Yes | Full mailbox address | |
| app_password | Yes | App password or mailbox password, depending on provider |
| name | Yes | Sender name for that mailbox |
| imap_host | For other domains | IMAP host when the preset cannot fill it |
For Gmail, Yahoo, and iCloud, host settings are filled in. For other domains, add imap_host. Each row receives the same IMAP and SMTP login test as a single mailbox connection.
Already-connected rows are skipped, so a re-upload is safe. Failed rows are listed with the reason. Mailboxes above the free limit need billing active before they connect.
For Gmail and Google Workspace, the recommended route is IMAP with an app password. That requires 2-Step Verification. In Google Account, go to Security → 2-Step Verification, then create an app password if your account is eligible. Google’s app-password help is here: Sign in with app passwords.
BobWork also has one-click Google sign-in, but it is limited. Google caps unverified apps at 100 users, BobWork has not done the CASA audit, and Google shows an unverified-app notice. A Workspace admin can mark the app as trusted in the Admin console. For bulk agency work, app passwords are usually easier to control.
The same CSV approach works for Gmail, Google Workspace, Yahoo, iCloud, and other IMAP + SMTP mailboxes. Zoho Mail can use the Zoho Mail API through a Self Client code, or IMAP on Mail Lite and above. Lark Mail uses IMAP plus a mail-client password.
Outlook and Microsoft 365 are not supported yet because Microsoft requires OAuth. Do not plan a Microsoft 365 agency fleet around BobWork until that support exists. For provider-specific steps, start with the CSV bulk import guide and the Google Workspace warm-up guide.
How fast does the fleet ramp?
Each mailbox ramps on its own schedule. The default warm-up engine starts at 3 emails per day, adds 2 per day, and caps at 30 per day. The cap is editable per mailbox, up to 100.
Weekends run at 30%. Sends are spread across 09:00–18:00 in the mailbox’s own time zone, with decisions every 15 minutes and randomness. A pair of mailboxes never writes to each other twice within 3 hours. Peers on a different domain or provider are picked twice as often.
Here is the weekday ramp before weekend reduction:
| Fleet size | Day 1 warm-up/day | Day 7 warm-up/day | Day 14 warm-up/day | Day 15+ warm-up/day |
|---|---|---|---|---|
| 50 mailboxes | 150 | 750 | 1,450 | 1,500 |
| 100 mailboxes | 300 | 1,500 | 2,900 | 3,000 |
| 200 mailboxes | 600 | 3,000 | 5,800 | 6,000 |
| 300 mailboxes | 900 | 4,500 | 8,700 | 9,000 |
| 500 mailboxes | 1,500 | 7,500 | 14,500 | 15,000 |
| 1,000 mailboxes | 3,000 | 15,000 | 29,000 | 30,000 |
Those numbers are warm-up emails, not cold emails. Warm-up should continue while campaigns run, but not at maximum volume. We publish a practical rule: keep warm-up at 10–15 per day during campaigns, keep real outreach around 30–50 per day per mailbox, and add mailboxes instead of forcing more volume through one inbox.
New domains need more patience. Use 7 days for an existing domain and 2–3 weeks for a new one. If you are planning the first campaign on a new client domain, read the new-domain warm-up plan before setting launch dates.
The warm-up engine handles send spacing, reply generation, spam rescue, and archive timing automatically. About 40% of received warm-up mail gets a reply, threads end after 3 messages, and content is plain-text office talk without links or images.
Shared or private pool?
BobWork uses a shared warm-up network by default. Every active mailbox on the service exchanges warm-up emails with other active mailboxes across accounts. One mailbox is enough to start because it can warm with the wider network.
A private pool is optional. In the dashboard, go to Mailbox pool → Pool mode and switch the account to Private pool. Then only that account’s own mailboxes write to each other. A private pool needs at least two mailboxes.
For agencies, the choice depends on client size and risk preference:
| Client fleet | Pool choice | Reason |
|---|---|---|
| 1 mailbox | Shared network | Private pool cannot run with one mailbox |
| 2–20 mailboxes | Shared network, unless the client requires isolation | More external variety |
| 20–49 mailboxes | Either | Enough internal traffic for some clients |
| 50+ mailboxes | Private pool is often cleaner | The client has enough mailboxes to warm internally |
| Sensitive client list | Private pool | No outside account receives those addresses |
Do not describe private pool as the default. Shared network is the default, and the live network count is shown on the dashboard. Do not rely on a stated network-size number in a client report because it changes.
Private pool is useful when one client has many mailboxes and does not want addresses appearing in cross-account warm-up. Shared network is useful when a client has only a few mailboxes and needs external interaction from day one.
For a deeper safety comparison, use the private pool versus public network guide.
How should domains be spread?
Do not place hundreds of sending mailboxes on one domain. A common agency setup is 2–5 mailboxes per sending domain. That spreads reputation risk and keeps campaign volume easier to control.
Every sending domain needs DNS configured. At minimum, check SPF, DKIM, and DMARC. BobWork checks SPF, DKIM, and DMARC daily via DNS and shows the result per domain. DKIM selectors checked include google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu, and zoho.
Use the same standard for every client domain:
| Record | What to check | Why it matters |
|---|---|---|
| SPF | The sending service is authorised | Helps receivers validate the sending path |
| DKIM | The provider signs mail for the domain | Proves the message was not altered |
| DMARC | Policy exists, at least p=none during setup | Ties authentication to the visible From domain |
| PTR | Valid reverse DNS where applicable | Required by some receiver rules |
| Unsubscribe | Working opt-out for bulk-style mail | Required by major mailbox-provider rules |
Google’s sender guidelines say to keep spam complaint rates below 0.1% and avoid ever reaching 0.3%. See Google’s email sender guidelines. Yahoo’s sender guidance requires SPF and DKIM, DMARC at least p=none, aligned From domains, one-click unsubscribe for bulk, and spam rate under 0.3%. See Yahoo sender best practices.
These are not warm-up scores. They are mailbox-provider expectations for real sending. Warm-up can help create normal mailbox activity, but it cannot fix bad lists, misleading copy, broken DNS, or high complaints.
For DNS setup details, use the SPF, DKIM, and DMARC checklist. For domain count planning, use the 2–5 mailboxes per domain guide.
What should you check weekly?
Fleet reporting should answer three questions: which mailboxes are healthy, which domains have DNS issues, and which mailboxes are ready for outreach.
BobWork’s spam rate is the share of a sender’s warm-up mail that receiving mailboxes found in Spam over the last 7 days. It is measured directly inside receiving mailboxes. It does not use third-party seed lists.
The health score runs from 0 to 100:
| Status | Score or condition | What it means |
|---|---|---|
| Healthy | 85–100 | Warm-up is working normally |
| Watch | 60–84 | Review spam rate, DNS, or provider issues |
| At risk | Under 60 | Pause or reduce sending decisions |
| Blocked | Login or permission failed | Reconnect or fix access |
A mailbox is ready for outbound only when all three checks pass: it has warmed for 7 or more days, its 7-day spam rate is 10% or lower, and it has received at least 30 warm-up emails.
Do not launch every mailbox just because the calendar says day seven. Use the ready gate. For new domains, wait 2–3 weeks before full volume.
If a mailbox rises above 5% spam rate, pause it for a few days. Check DNS, provider warnings, recent campaign copy, bounce patterns, and list quality. If the issue affects one domain, do not punish unrelated client accounts.
Warm-up rescue is deliberately narrow. Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up, and archived after 24 hours. Only mail carrying the engine’s hidden header, or a known subject for Zoho API senders, is touched. Real mail is never read, moved, or answered.
When campaigns begin, keep warm-up running on the same mailbox. The campaign volume should still stay controlled. If you need 500 cold emails per day, you usually need more mailboxes and domains, not one mailbox sending harder. Use the mailbox calculator by daily volume before promising client capacity.
Use this checklist before you connect the next client fleet.
| Step | Action | How to verify |
|---|---|---|
| 1 | Create one warm-up account for the client | The dashboard shows only that client’s mailboxes and domains |
| 2 | Count mailboxes and price the account | Match the count to the cost table above |
| 3 | Spread mailboxes over domains | Stay around 2–5 mailboxes per domain where possible |
| 4 | Set SPF, DKIM, and DMARC on every domain | Domain checks show passing records in the dashboard |
| 5 | Prepare app passwords | Gmail and Workspace accounts have 2-Step Verification before app-password use |
| 6 | Upload the CSV | Add mailbox → Many mailboxes: upload a CSV accepts email, app_password, name, and imap_host where needed |
| 7 | Fix failed rows | The failed-row report shows no remaining login or host errors |
| 8 | Choose pool mode | Mailbox pool → Pool mode shows Shared or Private as intended |
| 9 | Wait for the ready gate | Each mailbox has 7+ days warming, 10% or lower 7-day spam rate, and 30+ received warm-up emails |
| 10 | Start conservative outreach | Real sending stays around 30–50 per mailbox per day, with warm-up kept around 10–15/day |
For a client with hundreds of mailboxes, do not optimise only for the fastest connection path. Optimise for clean ownership, clean DNS, clean reporting, and a conservative ramp.
BobWork Email Warm-up lets you start with 3 free mailboxes per new account, upload bulk mailboxes by CSV, use the shared warm-up network by default, or switch a client account to a private pool. Start at the free warm-up tool, connect one client account, and wait for the ready checks before real outreach.
Frequently asked questions
Should an agency use one warm-up account per client?
Use one account per client when you want separate DNS checks, billing, pool mode, and readiness reporting. It also avoids mixing client mailbox decisions. If a client’s staff log in with the same company domain, they share that company domain’s free mailbox allowance.
How many mailboxes are free for a new client account?
New BobWork Email Warm-up accounts get up to 3 mailboxes free, with no credit card and no time limit. Extra mailboxes are priced by volume: $5 each for 1–9 extra, $3 each from 10 extra, and $2 each from 50 extra.
Can I upload many Gmail or Workspace mailboxes at once?
Yes. Use Add mailbox → Many mailboxes: upload a CSV. Rows use email, app_password,name. Gmail and Google Workspace app passwords need 2-Step Verification. Each row gets the same IMAP and SMTP login test as a single mailbox.
When should an agency use a private pool?
Use the shared network by default if you want one mailbox to start immediately. Switch to a private pool when a client has enough mailboxes to warm internally, especially around 50 or more. Private pools need at least two mailboxes.
How long before client mailboxes are ready?
Use 7 days for an existing domain and 2–3 weeks for a new domain. In BobWork, a mailbox is ready for outbound after 7+ days warming, a 7-day spam rate of 10% or lower, and at least 30 warm-up emails received.
How many cold emails should each warmed mailbox send?
A typical safe range is 30–50 real outreach emails per day per mailbox. Keep warm-up running at 10–15 per day during campaigns. If you need more volume, add mailboxes and domains instead of pushing one inbox harder.
Upload your whole fleet in one CSV
3 mailboxes free, then Pro ($19 a month, up to 10) or Agency ($89 a month, up to 300). Every row gets a real login test, and failed rows tell you why.