The decision to delegate email to a virtual assistant usually arrives the same way: not as a strategy, but at 11:40pm on a Sunday, somewhere around the eightieth unread message. Which is a bad moment to design a system, and a very good moment to hand over the whole inbox at once and regret it by Wednesday.
So here is the version that works. What to hand over on day one, the triage that makes it safe, and the rules that keep replies sounding like you rather than like a company that has recently discovered the word “kindly”.
28%
Of the working week that knowledge workers spend reading and answering email, per McKinsey Global Institute. More than a day. Every week. Permanently. The study is from 2012 and nobody thinks the number has fallen since.
McKinsey Global Institute · The Social Economy, 2012
Do not hand over everything on day one
The instinct is to give someone the whole inbox and let them work it out. This fails for a reason that has nothing to do with the assistant’s ability: on day one they do not yet know which of your clients is difficult, which supplier is three weeks late, or that the message from the person with the friendly tone is actually a problem.
You know all of that. None of it is written down. It lives in a decade of context that cannot be transferred in an onboarding call, and it is the thing that makes an inbox legible.
So start with one bucket and widen weekly. Slower for two weeks, permanently faster after that.
The four-bucket triage
Every message that arrives is one of four things. Not five. Four.
| Bucket | What it looks like | Action | Owner from |
|---|---|---|---|
| 01 — File it | Receipts, confirmations, newsletters, cc’d threads | Archive or label. No reply. | Day 1 |
| 02 — Template it | Scheduling, pricing enquiries, document requests, routine questions | Reply from an approved template | Day 1, reviewed |
| 03 — Draft it | Anything needing your specific view, written fresh | Draft, leave for you, you send | Week 2 |
| 04 — Escalate now | Legal, disputed money, unhappy client, anything unusual | Flag to you same day. No reply attempted. | Always yours |
Bucket one is where the volume is and it is completely safe. Most people are surprised how much of the inbox is bucket one — commonly more than half. Handing over only bucket one, on day one, and nothing else, already buys back a meaningful slice of the week at essentially zero risk.
Bucket four is the one to write down carefully, because it is defined by feel and feel does not transfer. Be specific: name the two clients who go straight to you, name the supplier dispute currently running, and add the catch-all — anything you would not want read aloud in a deposition.
Voice rules beat voice examples
The standard advice is to give your assistant a folder of past emails to learn your style from. It half works. What works better, and takes ten minutes, is a list of things you never say.
Prohibitions are precise in a way that examples are not. “Sound like me” is unfalsifiable. “Never open with ‘I hope this email finds you well’” is a rule somebody can actually follow on their first morning.
Five is enough. A realistic set:
- Never open with a pleasantry about the weather or their week. Start with the thing.
- Never use “kindly”, “please be advised”, or “as per my last email”.
- Never apologise for a delay that was under a day.
- Never promise a date without checking the calendar. “Early next week” is a promise.
- Never use three sentences where one works.
Then two positive rules, because prohibitions alone produce writing that is correct and lifeless: sign off the way you actually sign off, and keep the contractions. Nothing signals “a different person wrote this” faster than a sudden outbreak of “do not” where you have written “don’t” for fifteen years.
Delegate access, never share a password
This part is not optional and it is frequently got wrong.
Both Google Workspace and Microsoft 365 support delegated mailbox access. The assistant works inside your inbox under their own login, with their own audit trail, and you revoke it in one click on the day they move on.
Sharing the password gives you none of that. No audit trail, no revocation short of a password change that breaks everything else you have signed into, and a straightforward breach of most security policies you have already agreed to. It takes four minutes to set up delegation properly. Do the four minutes.
The four-week ramp
Widen one step per week. Do not skip ahead because week one went well; week one always goes well.
- Week one — file it. Bucket one only. Archiving, labelling, unsubscribing. You still read everything. The goal is that they learn your categories and you learn how they think.
- Week two — template it. Bucket two, every reply reviewed by you before sending. Expect to edit heavily. This is the week the voice rules earn their keep.
- Week three — release templates. Bucket two goes unsupervised for the categories where you stopped editing. Bucket three starts: they draft, you send.
- Week four — steady state. Buckets one and two theirs. Bucket three drafted for you. Bucket four escalated. A daily fifteen-minute handover covering anything ambiguous.
The rule underneath all four weeks: nothing leaves under your name unread for the first fortnight. After that, templates go unsupervised and freshly-written replies do not — not because your assistant cannot write, but because bucket three is by definition the mail that needed your view, and a good draft of your view is still not your view.
If you are still correcting a category after a month, that is not a training failure. That is a category that should not have been delegated, and moving it back to bucket four is a sensible decision rather than an admission of anything.
What actually changes
Less than people fear, and differently than they expect.
Clients almost never notice. The ones who do rarely mind — what they mind is a slow reply, or a confidently wrong one. If transparency sits better with you, a signature line naming the assistant costs nothing and has never lost anybody a client.
What changes for you is subtler. The inbox stops being the first thing and the last thing. You stop reading the same message four times without acting on it. And the eleven-hour weekly cost of email becomes somebody’s actual job rather than a tax on every other job you have.
The natural next step, once triage is running, is automating the parts of bucket two that never needed a person at all — that is the six automations to build first. And if the bucket-three drafts are mostly proposals, there is a faster structure for those: how to write a proposal in under an hour.
Or skip the design phase entirely and tell us what the inbox looks like. Twenty minutes, and you leave with a scope and a start date.