Email Warm-Up for Agencies: Control 20+ Client Mailboxes

For agencies, the safe model is 14 days of warm-up for existing domains, 3–4 weeks for new domains, and 30–50 real outbound emails per mailbox per day. Ignore structure and you mix client data, miss DNS failures, and launch rushed senders. This workflow gives you the account setup, caps, naming, onboarding, and reporting system.

If you are still choosing a tool, start with the agency warm-up pricing and provider comparison. Then use this page to run the process without confusing one client’s reputation with another client’s results.

Agencies rarely fail because they forget to send warm-up emails. They fail because nobody can answer basic questions later: which mailbox belongs to which client, when it started, what cap it uses, what its 7-day spam rate is, and whether the domain is ready for outreach.

Which account model should agencies use?

Choose the account model before you connect the first mailbox. This is where agencies prevent most future reporting problems.

Use one agency-controlled account when you want central control, shared operations, and a single reporting workflow. This fits clients that trust you to manage the sending infrastructure.

Use one account per client when the client needs clean separation. This also makes private pool mode easier to explain, because private pools are account-level.

BobWork Email Warm-up 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.

Private pool is optional. Any account can switch to private pool in the dashboard at Mailbox pool → Pool mode. In private mode, only mailboxes inside that account write to each other. You need at least two mailboxes for private mode.

Use the shared network when you want external mailbox variety. Peers on a different domain or provider are picked twice as often by the engine, which avoids a pattern where only sister mailboxes talk to each other.

Use a private pool when a client requires isolation. Be clear that a private pool is not useful for a single mailbox.

Check provider support before you promise onboarding. BobWork supports Gmail and Google Workspace, Zoho Mail, Lark Mail, Yahoo Mail, iCloud Mail, Amazon SES, SendGrid, Mailgun, and any IMAP+SMTP mailbox. Outlook and Microsoft 365 are not supported yet because Microsoft requires OAuth.

Keep setup guides nearby for common providers: Gmail warm-up and Zoho Mail warm-up cover two frequent agency paths.

How does email warm up for agencies differ?

Agency warm-up is not just more mailboxes. It is repeatability.

Every client should follow the same path: DNS checks, ramp, cap policy, reporting window, ready gate, and pause threshold. Without that, every account manager invents a different definition of safe.

Use this baseline table for agency operations.

Do not treat the editable cap as a volume hack. A mailbox capped at 100 warm-up emails per day is not automatically ready to send 100 cold emails per day.

Warm-up and outbound create different signals. Warm-up creates normal mailbox interactions. Cold outreach adds copy, links, prospect lists, complaints, bounces, unsubscribe handling, and replies from strangers.

If a client wants more volume, add mailboxes. Do not make one mailbox carry the whole campaign. The safer agency model is many steady senders, not one overheated sender.

For broader volume planning, use the cold email per mailbox guide before you promise daily lead targets.

What cap policy should you set?

Set caps before the campaign starts. Do not adjust them during a client call because someone wants more leads tomorrow.

For onboarding, use the default ramp first: 3 emails per day, then +2 per day, capped at 30 per day. Leave weekends at 30%. Let the data settle before changing anything.

Once the client is live, keep warm-up at 10–15 emails per day during campaigns. That gives you ongoing signal without crowding the mailbox.

Keep real outreach around 30–50 emails per mailbox per day when the domain, DNS, copy, and list quality are sound.

Do not combine a high warm-up cap with aggressive outreach. The mailbox has one reputation. Providers see total behavior, not your internal labels.

Use this cap policy across clients:

The free shared network in BobWork Email Warm-up handles peer selection, sending spread, replies, spam rescue, and 24-hour archive automatically. You still need to set sensible caps and decide when each mailbox can send real campaigns.

How should agencies name mailboxes?

Naming is not cosmetic. It prevents wrong reports, wrong caps, and wrong client explanations.

Use one format across your tracker, warm-up dashboard notes, campaign tool, and reporting sheet.

A good agency format is:

ClientCode | Domain | SenderName | Provider | Purpose | StartDate

Example:

ACME | acme.example | Maya | Google Workspace | US outbound | 2026-10-16

Use short client codes. Do not rely on first names. Agencies often have five clients with an Alex, Sarah, or James.

Track the domain separately from the mailbox. Domain-level problems affect several senders at once. If three mailboxes on one domain show rising spam landings, investigate the domain instead of treating them as three unrelated mailbox issues.

At minimum, your tracker should include this:

Keep the tracker boring. A new operator should understand the account without asking in Slack.

What onboarding checklist prevents mistakes?

Do not onboard from memory. Use the same order every time.

DNS comes before volume. SPF, DKIM, and DMARC are not optional for serious sending.

Google’s sender guidelines state that senders should authenticate mail with SPF or DKIM, and bulk senders have extra requirements around DMARC and spam rates. Read the current source at Google’s email sender guidelines.

Yahoo publishes sender expectations, including authentication and complaint control, at Yahoo Sender Hub best practices.

For DMARC, the primary technical reference is RFC 7489. Clients do not need to read the RFC. Your technical owner should understand alignment.

BobWork checks SPF, DKIM, and DMARC daily via DNS and shows the result per domain. It looks for common DKIM selectors including google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu, and zoho.

For manual checks, use the free DMARC checker before you start outreach.

Provider setup has a few agency traps.

For Gmail and Google Workspace, Google sign-in uses the gmail.modify scope. Google may show an unverified-app notice because BobWork has not completed the CASA audit. If the client will not approve that, use IMAP with an app password where allowed.

For Zoho Mail, the Zoho Mail API route works on the free plan through a Self Client code. IMAP is available on Mail Lite and higher.

For Yahoo Mail and iCloud Mail, use IMAP with an app password. For Amazon SES, SendGrid, and Mailgun, use the platform SMTP credentials for sending plus a receiving inbox over IMAP.

What should client reports show?

Do not send clients a wall of warm-up activity. Send a decision report.

The best weekly report answers four questions:

• Is the mailbox ready, watching, paused, or blocked?
• What is the 7-day spam rate?
• Are SPF, DKIM, and DMARC passing?
• What should we do next week?

Use the sender’s warm-up spam rate, not a vague inbox placement claim. In BobWork, spam rate is the share of a sender’s warm-up mail that receiving mailboxes found in Spam over the last 7 days.

That is useful because it is measured directly in receiving mailboxes. It is not a third-party seed-list estimate.

Use plain thresholds in client reports.

Avoid saying inbox rate unless you can prove it across real recipient inboxes. Warm-up data tells you where warm-up mail landed inside the network. Campaign performance still depends on prospects, copy, sending domain, complaints, bounces, and reply quality.

Report spam rate as a trend, not a single dramatic number. A one-day spike can happen. A seven-day pattern is more useful.

A simple good-week summary:

Mailbox maya@acme.example is ready for low-volume outbound. It has warmed for 17 days, received 42 warm-up emails in the last 7 days, and its 7-day warm-up spam rate is 1.8%. SPF, DKIM, and DMARC are passing. Keep real outreach at 35/day this week.

A bad-week summary:

Mailbox alex@acme.example is paused. Its 7-day warm-up spam rate rose to 6.4%. DNS is passing, so we are checking recent campaign volume, bounces, copy, and list source before restarting.

This protects the agency and teaches clients that deliverability is an operating system, not a switch.

How do you keep warm-up separate?

Warm-up should never touch real sales conversations.

BobWork warm-up content uses short office-style notes: 40 openers, 16 replies, and 6 closers. Messages are plain text, with no links and no images, and use first-name greetings.

Received warm-up mail found in Spam is moved to Inbox, marked read, labeled Warm-up, and archived after 24 hours. Only mail carrying the engine’s hidden header is touched. For Zoho API senders, a known subject is used. Real mail is never read, moved, or answered.

That separation matters for agencies because clients often ask whether warm-up can interfere with prospects. The precise answer is simple: warm-up mail is handled by the warm-up engine; real mail is not.

Do not let clients write their own warm-up copy. Someone will add a sales link, a tracking domain, a pitch, or a spammy phrase. Warm-up is not a copy test.

Use campaign tools for campaign tests. Use warm-up to build steady mailbox behavior and detect spam-folder landings.

If real campaigns go to spam, do not blame warm-up first. Work through authentication, domain age, sender volume, list quality, bounces, complaints, copy, links, and recent sending changes. This why emails go to spam guide gives you a structured path.

Run a weekly agency cadence:

• Monday: check blocked mailboxes, DNS failures, and spam-rate outliers.
• Tuesday: review clients approaching the ready gate.
• Wednesday: compare campaign volume against mailbox caps.
• Thursday: inspect domains where multiple mailboxes are degrading.
• Friday: send client summaries and next-week actions.

Do not wait for the client to ask whether a mailbox is safe. Tell them before the campaign starts.

Use three rules across every client. First, no mailbox launches outbound before the ready gate. Second, no mailbox keeps sending when spam rate is above 5%. Third, no domain scales by pressure. Add properly warmed mailboxes instead of doubling one sender overnight.

BobWork Email Warm-up is free for up to 10 mailboxes per account, with no credit card and no time limit. Each active mailbox above 10 is $5/month ($3 each from 10 extra, $2 each from 50 extra), billed by Stripe, prorated, and cancellable any time. Extras pause without billing. If that fits your provider mix, start with the free warm-up tool and document pool mode, caps, DNS status, and 7-day spam rate before the first client report.

Frequently asked questions