Skip to content
Skip to content

Roll It Out in Stages, Not All at Once

Email automation goes wrong when businesses enable everything on day one and discover the failure modes in front of customers. Four stages, each of which only proceeds when the previous one is demonstrably working.

Do not skip stage one. Businesses that automate before documenting their own answers end up with a system confidently sending responses nobody approved.

Four-Stage Rollout Checklist

Each stage has an exit condition. Do not skip ahead.

0 of 28 complete0%

Your ticks are saved in this browser, so you can work through the list over several sessions.

01Stage 1 · Prepare

0/7

Write your answers down before automating them.

02Stage 2 · Triage only

0/7

Classification and routing. Nothing goes outbound.

03Stage 3 · Draft with approval

0/7

A human reviews and sends every message.

04Stage 4 · Narrow automated sending

0/7

Optional. Only for genuinely routine, low-risk categories.

A general rollout framework. Specific steps vary by platform. Where an inbox carries personal, health or legally sensitive information, assess your privacy obligations before granting any third-party access.

The Three Rules

Everything in this checklist follows from three principles that keep an email rollout out of trouble.

Write your answers before automating them

A system can only be as good as the answers it is given. Businesses that expect AI to infer their pricing, policies and tone end up with responses that sound plausible and are subtly wrong, which is considerably worse than a slow reply.

Nothing goes outbound until triage is proven

Start with classification only. If it cannot reliably tell an enquiry from an invoice, it certainly should not be drafting replies. Triage-only carries essentially no external risk and produces most of the early insight.

A human stays accountable for what goes out

Drafting with approval is not a training-wheels phase to grow out of. For most businesses it is the right permanent operating mode, because it captures nearly all the time saving while keeping a person responsible for every outbound message.

The Four Stages

Each stage has an exit condition. Do not advance until the current stage is demonstrably working on real mail.

1

Prepare

Document your categories, your top questions and the approved answers. Decide what must never be automated. Usually one to two weeks of effort.

2

Triage only

Classification and routing with no outbound messages. Run for two weeks and measure accuracy before proceeding.

3

Draft with approval

The system prepares responses; a human reviews and sends every one. Track edit rates to find where drafting is weak.

4

Narrow automated sending

Only for tightly defined, low-risk categories, and only once drafting has proven reliable in those categories specifically.

The Mistakes That Cause Real Damage

Four failure modes seen repeatedly in email automation rollouts, all of which are avoidable with sequencing.

Enabling automated sending too early

The most damaging mistake, because the errors are visible to customers and cannot be recalled. Automated sending should be the last stage, restricted to narrow categories, and enabled only after drafting has proven accurate in exactly those categories.

  • Never enable automated sending during initial rollout
  • Restrict it to categories with one unambiguous correct answer
  • Require a demonstrated accuracy record in that category first
  • Keep an obvious route for recipients to reach a person

Granting full mailbox access without scoping

Email automation needs mailbox access, and it is frequently granted at a far broader scope than required, full access to every mailbox in the organisation rather than the one shared inbox in scope. Scope narrowly and review what was actually granted.

  • Grant access to the specific mailbox in scope, not the whole tenancy
  • Use a dedicated service account rather than a staff member’s credentials
  • Review the permission scopes actually requested before approving
  • Document how access is revoked when the engagement ends

No measurement of whether it is working

Without tracking classification accuracy and how heavily drafts are edited, nobody can say whether the system is helping. Teams end up arguing from anecdote, and a system that has quietly degraded goes unnoticed for months.

  • Track classification accuracy on a sample every week
  • Track how much reviewers edit drafts before sending
  • Track response time before and after, using the same measure
  • Review the categories where errors would be most costly

Never revisiting it after go-live

Email content drifts. New products, new policies, seasonal patterns and new customer questions all appear, and a system configured against last year’s mail becomes gradually less accurate. Without scheduled review, nobody notices until quality is visibly poor.

  • Schedule a monthly review for the first six months
  • Feed newly recurring questions into the approved answer set
  • Update answers whenever pricing or policy changes
  • Assign a named owner: an unowned system decays

Next Steps

AI Email Readiness Assessment

Check whether your inbox is a good candidate before rolling anything out.

Assess readiness →

AI Email Security Checklist

The access, privacy and security controls to settle before granting mailbox access.

Open the checklist →

Inbox Overload Scorecard

Diagnose the underlying process problem before automating on top of it.

Score your inbox →

Frequently Asked Questions

How long does a staged rollout take?

Four to eight weeks end to end for most businesses. Preparation is typically one to two weeks and depends almost entirely on how quickly you can get subject-matter input on the approved answers. Triage-only should run for a full two weeks so it sees a representative sample of your mail. Drafting usually needs two to four weeks before edit rates settle. Automated sending, if you enable it at all, comes after that. Businesses that already have documented answers and clear categories move considerably faster.

What accuracy should triage reach before moving to drafting?

Aim for around ninety per cent correct classification on your main categories before advancing, and pay particular attention to the categories where a misroute would be costly, a complaint classified as a general enquiry, for example. Perfect accuracy is not the goal and not achievable. What matters is that errors are the low-consequence kind and that misclassified messages still reach a person promptly rather than disappearing into a queue nobody watches.

How do we know if drafting is good enough?

Track how much reviewers change drafts before sending. If most go out with only minor edits, drafting is working. If reviewers routinely rewrite from scratch, the system is producing more work rather than less, and the cause is almost always missing or unclear source answers rather than the technology. Break the edit rate down by category. You will usually find drafting is strong for two or three categories and poor for one, which tells you exactly where to focus.

Should we tell staff before or after switching it on?

Before, clearly and specifically. Staff who discover email automation by accident assume the worst about what it means for their roles, and a team that quietly distrusts the system will route around it. Explain which categories it handles, what still comes to them, why it is being introduced, and give them a straightforward way to flag when it gets something wrong. That feedback loop is genuinely the most valuable source of correction in the first month.

What if it misclassifies something important?

It will, which is exactly why triage-only comes first and why misclassified messages must still reach a person. Design the queue so nothing can sit unseen: set an ageing threshold that escalates anything unactioned, and review the exception queue daily during rollout. A misclassification that gets noticed and corrected within an hour is a minor annoyance. One that sits in an unwatched folder for a week is how a complaint becomes a formal complaint.

Can we roll back if it is not working?

Yes, and you should confirm exactly how before you start. Because the staged approach never removes the underlying mailbox or the human process, reverting means switching off the automation and returning to manual handling. The mail is still there and nothing has been destroyed. Document the rollback steps during stage one, and make sure someone other than the person who set it up knows how to execute them.

Want Your Rollout Reviewed?

Send us your categories and approved answers before you switch anything on. We will tell you what we would change, whether or not you are a customer.