Email Warm-Up Report Template for Agency Clients
A useful client warm-up report needs 7 days of mailbox data: spam rate, ready status, rescued warm-up mail, DNS health, and the next action. If you only report activity counts, clients miss the mailbox that is quietly failing. Use this weekly format to show status, explain risk, and export the same data by API.
Agency reporting should prove control without promising inbox placement. Warm-up is one signal among DNS, sending volume, list quality, copy, replies, bounces, and complaints. If you manage many client mailboxes, pair this report with a broader cold email deliverability checklist and a mailbox-by-mailbox warm-up view.
BobWork Email Warm-up measures spam landings directly in receiving mailboxes, not with third-party seed lists. The email warm-up API can export mailbox stats and DNS checks into your own client sheet, dashboard, or reporting database.
What goes in an email warm-up report?
Your report should answer five client questions quickly:
- Are the mailboxes connected?
- Are they warming every day?
- Are they landing in Inbox often enough?
- Are any warm-up emails being rescued from Spam?
- Which mailboxes are ready for outbound?
Do not lead with total warm-up emails sent. Volume is useful, but it is not the outcome. A mailbox sending 210 warm-up emails a week with a bad spam rate is not healthy. A mailbox sending fewer emails during ramp-up may be fine.
Use one row per mailbox. Roll up by domain only after you show the mailbox view. One mailbox can fail while other mailboxes on the same domain stay healthy.
A good weekly client table has these columns:
| Column | What it shows | Client wording |
|---|---|---|
| Client | Account or brand name | Which client owns the mailbox |
| Domain | Sending domain | Which domain carries reputation risk |
| Mailbox | Sender address | Which sender is being warmed |
| Days warming | Calendar days since warm-up started | How mature the mailbox is |
| 7-day spam rate | Share of that sender's warm-up mail found in Spam | Main risk signal |
| Warm-up received | Warm-up emails received in 7 days | Sample size behind the status |
| Rescued mail | Warm-up emails moved from Spam to Inbox | Whether repair actions were needed |
| Ready | Yes or no | Whether outbound can start |
| DNS | SPF, DKIM, and DMARC status | Whether the domain is configured |
| Action | Next step | What you will do this week |
Keep the wording plain. Clients do not need every IMAP event. They need to know whether you will start sending, keep warming, slow down, or fix setup.
Which weekly thresholds matter?
Your report needs thresholds. Without them, clients read every yellow cell as a failure.
The table below uses BobWork's warm-up metrics and common sender practice. Do not mix warm-up spam rate with recipient complaint rate. Warm-up spam rate is placement of your warm-up mail in receiving mailboxes. Complaint rate is when real recipients mark your messages as spam.
Google's sender guidance says to keep spam rates below 0.10% and avoid reaching 0.30% or higher in Postmaster Tools. Yahoo's sender guidance lists a spam-rate threshold under 0.3% for bulk senders. Microsoft states requirements for high-volume Outlook.com senders, but does not state a numeric complaint threshold on its public page.
| Metric | Healthy | Watch | Stop or fix | How to report it |
|---|---|---|---|---|
| Health score | 85-100 | 60-84 | Under 60, or Blocked | Show status, not just score |
| 7-day warm-up spam rate | 0-5% | Above 5% | Above 10% for readiness | Show trend and action |
| Ready for outbound | 7+ days, spam rate ≤10%, 30+ received | Missing one condition | Blocked login or weak sample | Show Yes, Not yet, or Blocked |
| Warm-up received | 30+ in 7 days | Under 30 | Zero or login failed | Show sample size |
| Rescued warm-up mail | Low and stable | Rising week over week | Rising with spam rate above 5% | Explain as repair signal |
| DNS checks | SPF, DKIM, DMARC pass | One missing | SPF, DKIM, or DMARC failed | Show record status |
| Warm-up volume | Ramp as planned | Unexpected drop | No sends or no receives | Show reason |
| Real outreach | Typically 30-50/day/mailbox | More than plan | Sudden spikes | Show planned cap |
BobWork's readiness gate is strict enough for reporting. A mailbox is ready for outbound only after 7 or more days warming, a 7-day spam rate at or below 10%, and at least 30 warm-up emails received.
For a new domain, use more patience. We recommend 2-3 weeks before full cold outreach. For an existing domain, 7 days can be enough if DNS is correct and the mailbox passes the ready gate. The daily plan in how long to warm up before cold email helps when a client asks why a new domain is still waiting.
What should clients see?
Clients need a status report. Operators need a control report. Do not put every internal detail in the client version.
The client version should show fewer columns and stronger wording. Use statuses like Healthy, Watch, Not ready, Ready, and Blocked. Add one short note per risky mailbox.
The operator version should show the details that help your team fix problems. Include login state, permission failures, DNS status, provider type, pool mode, time zone, ramp cap, spam rate, rescue count, and last successful send.
This split prevents two reporting failures. You avoid hiding real risk behind a polished summary. You also avoid making the client manage details they cannot act on.
Use this pattern:
| View | Audience | Include | Exclude |
|---|---|---|---|
| Client summary | Founder, marketing lead, account owner | Status, ready count, risky count, action | Raw logs, API errors, provider noise |
| Client mailbox table | Client and account manager | Mailbox, domain, ready, spam rate, DNS, action | Hidden headers, IMAP folders, peer details |
| Operator report | Deliverability team | Full mailbox stats, login failures, pool mode, DNS checks | Sales commentary |
| Escalation note | Client plus operator | One issue, impact, fix, owner, due date | Long explanations |
If you warm many mailboxes, also separate by domain. A domain-level roll-up helps clients see whether risk is isolated or systemic.
For bigger fleets, this pairs well with a private pool. BobWork uses a shared warm-up network by default, and any account can switch to a private pool per account from Mailbox pool → Pool mode. A private pool needs at least two mailboxes. For 50+ mailboxes, see when to switch to a private warm-up pool.
When is a mailbox ready?
The most important weekly line is the ready count.
Clients usually ask whether they can start sending. Answer with a number, then name the blockers.
For example:
| Status | Count | Meaning | Action |
|---|---|---|---|
| Ready | 14 | Passed days, spam-rate, and received-mail gates | Eligible for controlled outbound |
| Not ready | 5 | Still warming or too little received mail | Continue warm-up |
| Watch | 2 | Spam rate rising or health score 60-84 | Hold outbound, monitor next week |
| Blocked | 1 | Login or permission failed | Reconnect mailbox |
Do not mark a mailbox ready just because it has been warming for a week. Time alone is weak. A mailbox needs enough received warm-up mail and acceptable placement.
Ready also does not mean unlimited sending. Keep real outreach conservative. We recommend 30-50 cold emails per day per mailbox, and adding mailboxes rather than pushing one sender harder. During active campaigns, keep warm-up running at about 10-15 emails per day.
If your client asks why you need more mailboxes, use the math. A 500-email-per-day campaign should not run through five mailboxes at 100 each. It is safer to spread volume across more mailboxes and domains. The calculator in how many mailboxes for cold email gives a practical planning view.
Ready status should also include DNS. A mailbox with failed DKIM or missing DMARC should not be presented as ready, even if warm-up placement looks acceptable.
How should you explain rescued mail?
Rescued mail is useful, but it is easy to oversell.
In BobWork, 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 own hidden header is touched. For Zoho API senders, a known subject is used. Real mail is never read, moved, or answered.
That means rescued mail is safe to report as a warm-up repair action. It does not mean you rescued a client's real prospect replies. It also does not guarantee future inbox placement.
Use this wording:
| Client question | Good answer | Avoid saying |
|---|---|---|
| What is rescued mail? | Warm-up mail that landed in Spam and was moved back to Inbox | We fixed all spam placement |
| Is any real mail touched? | No, only warm-up mail identified by the engine | We scan all inbox mail |
| Is rescue bad? | A few rescues can happen; trend matters | Any rescue means the domain is damaged |
| What action follows? | Watch trend, pause above 5% spam rate, fix DNS if needed | Keep sending normally regardless |
Rescue count is most useful when paired with spam rate. Ten rescued emails on a large sample can be less worrying than three rescued emails on a tiny sample. Always show the denominator.
A simple note works best:
> Rescued mail increased from 2 to 9 this week, and the mailbox spam rate is above 5%, so we are pausing outbound for a few days and keeping warm-up active.
If a mailbox turns red, use the health score as the entry point. BobWork scores mailboxes from 0 to 100: Healthy is 85 or higher, Watch is 60-84, At risk is under 60, and Blocked means login or permission failed. The guide to why a mailbox is red in warm-up explains the operator checks.
How do you export reports?
Screenshots are fine for a one-off client update. They do not scale.
For agency reporting, export the same fields every week. Store them in a sheet, data warehouse, or client portal. The format matters more than the tool.
Use one row per mailbox per reporting period. This keeps history clean and makes trend charts easy.
Recommended export columns:
| Field | Type | Example use |
|---|---|---|
| week_start | Date | Group reports by week |
| client_name | Text | Filter client dashboards |
| domain | Text | Group domain risk |
| mailbox | Identify sender | |
| provider | Text | Compare Gmail, Zoho, Yahoo, and others |
| days_warming | Number | Check maturity |
| health_status | Text | Healthy, Watch, At risk, Blocked |
| health_score | Number | Trend health over time |
| spam_rate_7d | Percent | Main placement risk |
| received_7d | Number | Sample size |
| rescued_7d | Number | Spam rescue trend |
| ready_for_outbound | Boolean | Client-ready status |
| spf_status | Text | DNS status |
| dkim_status | Text | DNS status |
| dmarc_status | Text | DNS status |
| next_action | Text | Account manager note |
BobWork's REST API is free. It uses personal keys with the bwk_ prefix, Bearer authentication, and a limit of 120 requests per minute per key. Each account can have up to five personal keys. The API includes endpoints for mailboxes, warm-up stats, domain checks, mailbox connection, campaigns, and contacts.
A practical export job does this once a week:
- Pull active mailboxes.
- Pull warm-up stats for each mailbox.
- Pull daily domain checks for SPF, DKIM, and DMARC.
- Calculate client statuses.
- Save one immutable weekly snapshot.
- Send the client summary from that snapshot.
Do not rebuild last week's report from live data. Warm-up state changes every day. A client report should be a historical record.
If you prefer no-code reporting, pull the API into a spreadsheet or internal dashboard. If you run an agency platform, map BobWork mailbox IDs to your client IDs once, then reuse that mapping every week.
What should you send weekly?
Use this checklist before you send the first weekly report. It keeps the report short and prevents awkward client questions.
| Step | Action | How to verify |
|---|---|---|
| 1 | List every client mailbox | One row per mailbox, no shared aliases |
| 2 | Group by domain | Each mailbox has a sending domain |
| 3 | Check SPF, DKIM, and DMARC | DNS status shows pass or a named failure |
| 4 | Pull 7-day spam rate | Every active mailbox has a value or a reason |
| 5 | Pull received warm-up count | Ready mailboxes have at least 30 received |
| 6 | Mark ready status | Ready only if all gates pass |
| 7 | Count rescued mail | Report count and sample size together |
| 8 | Add next action | Every Watch, At risk, or Blocked row has an owner |
| 9 | Save a snapshot | The week's data is stored before sending |
| 10 | Send a plain summary | Client gets counts, risks, and actions |
Also check provider rules before clients scale. Google publishes email sender guidelines, Yahoo publishes sender best practices, and Microsoft publishes requirements for Outlook.com senders. For unsubscribe headers, the one-click standard is RFC 8058.
These documents are not warm-up manuals. They are sending rules. Mention them when a client wants to jump from warm-up into larger outbound volume.
The report should fit in an email. Attach the table or link to a dashboard, but put the answer in the message body.
Use this structure:
| Section | Example |
|---|---|
| Summary | 18 mailboxes warming, 12 ready, 4 not ready, 2 watch |
| Wins | DNS fixed on 3 domains; 6 mailboxes moved to ready |
| Risks | 2 mailboxes above 5% spam rate; outbound paused |
| Next actions | Keep warm-up running, reconnect 1 blocked mailbox, review volume Friday |
| Client decision | Approve 30 emails/day from the 12 ready mailboxes |
Keep the tone calm. A warm-up report should not dramatize normal ramp-up. It should surface problems early and show the fix.
Here is a short template:
| Line | Text |
|---|---|
| Opening | This week's warm-up status: 12 of 18 mailboxes are ready for controlled outbound. |
| Detail | The remaining 6 are still warming or need fixes. Two are on Watch because 7-day spam rate rose above 5%. |
| Action | We are pausing outbound on those two, keeping warm-up active, and checking DNS again tomorrow. |
| Ask | Please keep the approved sending cap at 30 emails per day per ready mailbox this week. |
For accounts created from 10 November 2026, BobWork Email Warm-up includes up to 3 mailboxes free, no credit card, and no time limit. It uses a shared warm-up network by default, or a private pool per account if you prefer. The free shared network handles warm-up conversations, spam rescue, DNS checks, and readiness status automatically, while the API lets you export the same data into client reports. Outlook and Microsoft 365 are not supported yet.
Frequently asked questions
What should an email warm-up report include?
Include 7-day spam rate, ready status, warm-up emails received, rescued warm-up mail, health score, SPF, DKIM, DMARC, days warming, and the next action. Keep it weekly, not daily, so clients see direction instead of noise.
Is rescued mail a bad sign?
Not always. Rescued mail means warm-up messages were found in Spam and moved back to Inbox. A few rescues can happen during ramp-up. A rising rescued count, especially with spam rate above 5%, means you should pause or slow that mailbox.
How often should agencies send warm-up reports?
Weekly is usually enough. Daily reports create false alarms because small sample sizes swing quickly. Send urgent notes only for blocked logins, failed DNS, high spam rate, or a mailbox that should not start outbound yet.
When is a mailbox ready for cold outreach?
In BobWork, a mailbox is ready after 7 or more days warming, a 7-day spam rate at or below 10%, and at least 30 warm-up emails received. You should still keep real outreach conservative.
Can I export warm-up reports by API?
Yes. BobWork has a free REST API with personal keys, Bearer authentication, 120 requests per minute per key, and endpoints for mailboxes, warm-up stats and domain checks. You can export the data into your own spreadsheet or client portal.
Should clients see every mailbox detail?
Show enough detail to prove control, but not every operational event. Clients need status, risk, and action. Keep full logs, API errors, login failures and raw mailbox notes in an internal operator view.
Warm up your mailboxes free
Connect Gmail, Google Workspace, Zoho or Lark. Your mailboxes warm on a shared network, or in a private pool of your own, starting today.