An inbox management SOP is the one page that lets an assistant run your email without you reading it first. It needs five parts: a label set, routing rules, drafting conventions, escalation triggers and an end-of-day report. Copy the version below, change the names, and start in draft-only mode.
What does an inbox management SOP need to cover?
Five things, in this order. Labels tell the assistant where a message goes. Routing rules tell them what to do with it. Drafting conventions tell them how to write. Escalation triggers tell them when to stop. The end-of-day report tells you what happened, so you can stay out of the inbox and still be in charge.
Skip any one of them and the SOP fails predictably. No labels and nothing is findable. No routing rules and everything comes back to you as a question. No drafting conventions and replies sound like someone else. No escalation triggers and the assistant either guesses or interrupts constantly. No report and you go back to checking, which was the whole problem.
Admin work of exactly this kind is the largest single category of assistant workload. The Wishup 2026 industry report puts administrative assistants at 31.5 percent of the market, with admin and marketing together above 62 percent, which is why inbox and calendar are almost always the first hand-off.
What labels should the assistant use?
Eight, numbered so they sort in order. Resist adding a ninth.
| Label | What goes here | Who acts |
|---|---|---|
| 01 Action you | Needs your decision, your signature or your relationship | You |
| 02 Action assistant | Reply, book, chase, file, look up | Assistant |
| 03 Waiting on | Sent, awaiting a reply, with a chase date | Assistant chases |
| 04 Scheduled | Turned into a calendar item or a task with a date | Nobody until the date |
| 05 Read later | Useful, not urgent. Newsletters, reports, FYI threads | You, weekly |
| 06 Clients | Named client threads, kept for reference | Both |
| 07 Finance | Invoices, receipts, payment questions | Assistant prepares, you approve |
| 08 Escalated | Hit an escalation trigger, flagged and summarized | You, same day |
Everything else gets archived. Archive is not deletion and search still finds it, so the assistant should archive confidently rather than hoarding in case you want it.
What are the routing rules?
One line per message type. This is the part people over-think; keep it blunt.
| Message type | Action | Reply target |
|---|---|---|
| Meeting request | Check calendar, propose two slots, book, add to 04 | Same pass |
| Existing client question, routine | Draft answer from the knowledge doc, label 02 | Same day |
| New inquiry | Reply with qualifying questions or book the call, log in CRM | Within 2 hours |
| Invoice or receipt | File, add to the finance sheet, label 07 | Same day |
| Supplier or vendor chase | Reply with status, set a chase date, label 03 | Same day |
| Anything with money, legal, press or a VIP | Summarize in three lines, label 08 | Immediate |
| Newsletter, report, FYI | Label 05, no reply | Weekly digest |
| Cold sales pitch | Archive. Unsubscribe if it repeats | Never |
| Assistant is unsure | Label 08 with a one-line question | Immediate |
Set three passes a day and write the times in the SOP: 8am, 1pm and 4:30pm in your local time. Between passes the assistant works on tasks generated by the inbox rather than watching it.
How should the assistant draft in your voice?
Six conventions cover almost everything.
- Three sentences or fewer unless the topic genuinely needs more. Long replies invite long replies.
- Answer first, context second. Yes, Thursday at 2pm works. Here is the dial-in.
- Your greeting and sign-off, copied exactly from your last 20 sent messages.
- No new commitments. Dates inside the agreed booking window are fine. Prices, scope and deadlines are yours.
- Reply in the thread, never a new message, and never change the subject line mid-thread.
- On behalf of, at first. Sign as the assistant writing for you until you move a category to direct sending.
Build the voice guide backwards. Give the assistant 20 of your sent replies, ask them to write the rules they can see, then correct their version. It is faster than describing your own writing and much more accurate.
What does the copyable SOP look like?
Here is the whole thing. Change the bracketed parts.
INBOX MANAGEMENT SOP
Owner: [Your name] Assistant: [Name] Backup: [Name]
Access: delegated mailbox access, MFA on, reviewed monthly
Version: [date]
1. PASSES
8:00am full triage to zero
1:00pm new mail only
4:30pm full triage to zero, then end-of-day report
2. LABELS
01 Action you | 02 Action assistant | 03 Waiting on | 04 Scheduled
05 Read later | 06 Clients | 07 Finance | 08 Escalated
Everything else: archive.
3. ROUTING
Meeting request : propose 2 slots, book, label 04
Routine client : draft from knowledge doc, label 02
New inquiry : qualify or book, log in [CRM], within 2 hours
Invoice/receipt : file to [folder], log in [sheet], label 07
Vendor chase : reply with status, chase date, label 03
Newsletter/FYI : label 05, no reply
Cold pitch : archive, unsubscribe if repeated
Unsure : label 08 with a one-line question
4. DRAFTING
Three sentences or fewer. Answer first.
Greeting: [greeting]. Sign-off: [sign-off].
Never commit price, scope, deadline or legal position.
Reply in thread. Keep the subject line.
Mode: DRAFT ONLY until [date], then category by category.
5. ESCALATE IMMEDIATELY IF
Money over [amount] is mentioned
Legal, contract, dispute or regulator
Press, review sites or social complaint
Sender is on the VIP list: [names]
The assistant is not sure
6. SEND WITHOUT APPROVAL (add one at a time)
[ ] Scheduling and rescheduling
[ ] Document and file requests
[ ] Order or job status updates
[ ] Routine client questions from the knowledge doc
7. END OF DAY
Report sent by [time] to [address]. Format below.
8. NEVER
Delete permanently. Share credentials. Forward client data outside
[approved tools]. Reply to anything labeled 01 or 08.What goes in the end-of-day report?
Four blocks, under 200 words, same shape every day. This is the artifact that replaces you reading the inbox.
END OF DAY, [date]
HANDLED (28)
09:12 Booked [client] for Thu 2pm, invite sent
10:40 Replied to 6 order status questions
11:05 Filed 4 invoices, finance sheet updated
14:20 Chased [vendor] on the missing certificate
16:05 Drafted 3 replies, awaiting your approval
WAITING ON YOU (3)
1. [Client] proposal scope question. Needs an answer by Thu.
2. Invoice from [vendor] for $1,480. Approve or query.
3. Draft reply to [name] in the drafts folder.
FLAGGED (1)
[Name] mentioned canceling. Summary in label 08. Suggest a call.
TOMORROW
Recall list, weekly report build, follow up on 2 quotes.Two rules keep the report honest. Timestamps on the handled list, so you can spot-check. And a hard cap on the waiting-on-you section: if it is longer than five items for three days running, the escalation triggers are set too wide and need tightening.
How do you get to zero in the first two weeks?
Week one is archaeology, week two is rhythm.
| Day | What happens |
|---|---|
| 1 | Access granted, labels created, SOP shared, VIP list agreed |
| 2 to 3 | Bulk archive everything older than 90 days, unsubscribe in bulk, label the last 30 days |
| 4 to 5 | First full triage passes. Every reply drafted, nothing sent. First end-of-day reports |
| 6 to 8 | You correct drafts. Each correction becomes a new SOP line the same day |
| 9 to 10 | Move scheduling to send-without-approval. Keep everything else in draft |
| 11 to 14 | Add a second category. Move to spot checks. Book the weekly review |
By day 14 you should be reading one report a day instead of the inbox, and approving a handful of drafts. If you are still reading every message, the escalation triggers are too broad, not the assistant too slow.
On cost, an inbox is rarely a full role on its own. Most owners pair it with calendar, follow-ups and one recurring process to fill a part-time schedule. For a benchmark while you scope the hours, PayScale puts US assistants at $19.45 an hour and the Wishup 2026 cost guide puts managed assistants at $7 to $15.
AssistBPO staffs dedicated, employed assistants who run inbox, calendar and follow-ups in your hours and send the end-of-day report; see email management. Plans depend on hours, desks and coverage. Get a staffing plan within 1 business day.
Frequently asked questions
What is an inbox management SOP?
It is a one-page document that tells an assistant exactly how to run your email: which labels exist, what happens to each type of message, how to draft in your voice, when to stop and ask you, and what to report at the end of the day. Without it, the assistant makes reasonable guesses that are not your guesses, and you end up re-reading everything. With it, you read one report instead of 200 messages.
Should an assistant send email as me or on my behalf?
Start with on my behalf and delegated mailbox access, never a shared password. That keeps an audit trail and makes the relationship clear to recipients. After a few weeks, most owners move routine categories such as scheduling, order status and document requests to sending under their own name, while anything involving money, commitments or sensitive relationships stays on behalf, or stays with you. Review access monthly.
How does the assistant learn my writing voice?
Give them 20 of your sent replies covering your most common situations, then ask them to write the voice guide themselves and send it to you for correction. Their version will be more explicit than anything you would write about yourself. Add your three rules: typical length, greeting and sign-off, and words you never use. Correct drafts for two weeks and the voice settles.
How many times a day should the inbox be checked?
Three passes is enough for most owners: early morning, early afternoon and late afternoon. Continuous monitoring feels responsive and mostly produces switching cost, unless you run a support queue with a published response target, in which case that queue belongs in a help desk rather than an inbox. Set the pass times in the SOP so both sides know when messages get seen.
What if the assistant gets something wrong?
Expect it in the first fortnight and design for it. Draft-only mode means mistakes never reach a recipient. When you correct a draft, write the rule that would have prevented it into the SOP the same day, rather than explaining again next week. A good target is one new SOP line per correction, and no repeated corrections after week three.
