Five lessons, about seventy minutes. Inbox management is the single most requested thing in VA job posts, and it is where a new assistant is either trusted within two weeks or quietly replaced. This module is how you land on the right side of that.
Adaeze — the therapist from module 1 — has agreed to a trial. Her first message to you is this:
"Great, let's start Monday. My email login is adaeze@[her practice].com and the password is Sunshine2019! — the code will come to my phone so message me when you're logging in and I'll send it across."
This is the most dangerous moment in a new client relationship, and it will feel like the opposite. It will feel like trust. Here is why you should not accept it, and what to say instead.
Think about what happens if something goes wrong three months from now. A client's account gets phished. Money moves that should not have moved. A confidential file goes somewhere it should not. There is exactly one login, it was used by two people, and the logs cannot tell anyone apart.
You will be asked to prove it was not you. You will not be able to. Not because you did anything — because the setup made it impossible to demonstrate.
And a second, quieter cost. Every time Adaeze has to stop a session to send you a two-factor code, you have handed her a task. You were hired to remove those. Within a fortnight she will start feeling that you are more effort than help, and she will not be able to say why.
Password sharing is not trust. It is an absence of a system, and you are the one it will fail.
Gmail and Outlook both let an account owner grant another account delegate access. The delegate reads the inbox, replies, and files things — using their own login, with their own password and their own second factor. Nothing is shared.
What a delegate can do: read, reply, send, archive, and move messages to trash. What a delegate cannot do: change the password, touch account settings, permanently delete, or use chat and video calls as the owner. That boundary is not a limitation, it is the point — it is what protects you.
Three limits worth knowing before you promise anything, because getting caught out by these in week one is a bad look:
"Thanks Adaeze — I'd rather not use your password, for your protection and mine. If either of us ever needs to prove who did what, a shared login makes that impossible.
Better option: add me as a delegate on your email. Takes about two minutes in settings, I'll send the steps. I get in with my own login, you keep your password, and you never have to send me a code again.
Two things to know: I'd be working in a browser rather than the phone app, and people can see a reply came from me on your behalf. Happy either way — say the word if you'd rather I just had a bookings@ address instead, and I'll set that up."
Read what that message actually does. It refuses something, but the refusal is framed entirely as her protection. It names the exact benefit she cares about — no more codes. It discloses the two downsides before she can discover them. And it offers an alternative, so she is choosing between two options rather than being told no.
You have also, in your first week, demonstrated the thing module 1 said gets you paid: you thought about a risk she had not thought about, and you brought her a solution rather than a problem.
Some will insist on the password. If it is a small, short, low-stakes job, you may decide the risk is acceptable — that is your call to make deliberately, not by default. If you do accept it, ask her to change the password when the engagement ends, and put that in writing. If the work involves money, health information or anything legal, hold the line: "I'm not able to work in an account I can't be individually accountable in — but I can set up a bookings address today and we can start this afternoon."
Set up delegation between two email accounts you control — a friend's, a second account of your own, anything. Send one message as the delegate and look at exactly what the recipient sees in the header. You need to have seen this with your own eyes before you describe it to a client, because they will ask and a vague answer costs you the job.
You now have access. Adaeze's inbox has 340 unread messages and she has not told you what to do with any of them.
Almost every beginner does the same thing here: opens the top message, reads it, thinks about it, writes a reply, sends it, feels good, opens the next one. Ninety minutes later they have cleared eleven emails, missed the two that mattered, and have nothing to tell the client.
The fix is one rule, and it is the most useful sentence in this module.
Sort everything before you answer anything.
Sorting and answering are two different kinds of thinking. Sorting is fast, shallow and comparative — you are asking what kind of thing is this, and how does it rank against the others? Answering is slow and deep. Switching between them every thirty seconds is what makes an inbox exhausting.
More importantly: you cannot know what is urgent until you have seen everything. The email that looks alarming at position four is often nothing once you have read the one at position thirty-one that resolves it. Beginners reply to the alarming one and create work.
You can deal with this completely, right now, without the client. Most of the inbox lives here once you know the business.
Reschedule requests · known FAQs · confirmations · routine supplier replies
Needs her decision, but not her writing. You prepare the reply, she approves in one word. This pile is where you become valuable.
A new client enquiry · a partnership request · a rate negotiation
Genuinely needs her, and you cannot draft it. Keep this pile small and ruthless — every item is a tax on her attention.
Something only she knows · a personal matter · a decision with real money attached
No reply needed, ever. Archive, file or unsubscribe. Being decisive here is a skill, not a risk.
Newsletters · receipts · notifications · cold sales pitches · thread already resolved
Four labels in her email client, applied at speed. No replies yet. On a backlog of 340 this takes about forty minutes; on a normal day's forty messages, ten.
Look at the first row and the last. Chinelo asked to move her session, then withdrew it four hours later. An assistant answering top-down would have spent ten minutes rearranging a diary for no reason, and emailed a client twice. The assistant who sorted first spends nothing.
Look at the insurance rejection. It is the fifth item, does not look urgent, uses bland language — and it is the only thing in the inbox with a deadline and money attached. This is exactly the load-bearing email from lesson 1.3. Finding it in the first ten minutes rather than on day four is, on its own, worth more than a month of your fee.
Not the wrong reply. Silence. An assistant who spends her first day reading carefully and sends nothing has, from the client's side, done nothing at all — and clients have no way to see effort, only output. Sort, clear the easy pile, send the summary. Visible progress on day one buys you the patience you will need in week three.
Run the four piles on your own inbox. Time yourself. Notice how many are Kill, and notice at least one message you had been avoiding that turns out to be a thirty-second Handle. If your own inbox is small, use a spam-heavy account — the sorting reflex is what you are building, not the outcome.
Here is the fear that keeps new assistants from sending anything: what if I don't sound like her?
It is a reasonable fear and there is a boring, reliable answer. You do not guess at someone's voice. You go and read it, write down what you find, and follow the notes. An hour of work, once, and then it is a document rather than a talent.
Open her sent mail and read the last twenty replies she wrote herself. Do not read for content. Read for mechanics, and write down what you see:
Put it on one page in a shared document. This is the artefact — and when you eventually hand this client to someone else, or take on a second client, it is what stops you starting from nothing.
Match the register, not the personality. You are not performing Adaeze. You are matching formality, warmth and length so nothing jars. Nobody reading a reschedule confirmation is analysing prose style — they notice only when something feels off, and "off" is almost always a mismatch in these mechanics.
Never fake certainty in her voice. If you do not know whether she takes a particular insurance, do not write a confident sentence about it. Write the reply she would write if she also did not know: "Let me check that and come back to you today." Then check. A voice file governs how something is said. It never authorises you to invent what is said.
"Dear Chinelo,
Kindly be informed that your request to reschedule has been received and duly processed. Your appointment has now been moved to Friday at 2:00pm.
Warm regards,
Adaeze"
Nothing here is inaccurate. But Chinelo, who has been seeing Adaeze for a year, will read it and feel that something has changed — and what she will conclude is that she is now dealing with an office rather than a person.
"Hi Chinelo,
That's no problem — I've moved you to Friday at 2pm.
See you then.
Best,
Adaeze"
Contractions, first name, short, no ceremony. Chinelo notices nothing at all, which is exactly the goal. The best inbox work is invisible.
A language model will happily draft either version above. Paste your voice file into it and the drafts improve immediately — this is one of the genuinely good uses, and module 7 covers the mechanics properly.
But notice what just happened: the value was in the voice file, and a human made that by reading twenty emails and noticing things. The tool applied it. That is the supervision relationship from lesson 1.3, in the most ordinary possible setting, and it is why the assistant who builds the file is worth more than the one who pastes the raw email into a chatbot and hopes.
Build a voice file for someone whose writing you can read — a boss, a lecturer, a group admin, a family member who emails. Use the ten rows above. Then write one short reply in their voice, show it to someone who knows them, and ask whether it sounds like them. Their hesitation tells you which row you got wrong.
By week three with Adaeze you will notice something: you are writing the same six emails over and over. Rates. Availability. Where the office is. What happens if you cancel late. Whether she takes a particular insurance. How to pay.
This is good news, and it is where most of your time savings will come from. But it is also where assistants get themselves into trouble, by templating something that should never have been templated.
Does the answer change depending on facts only the client knows, or on how this particular person is going to feel?
If no to both — template it. If yes to either — it is a Draft, and a human decides.
"What are your rates?" — the answer is the same for everyone and nobody's feelings are engaged. Template. "I've been struggling since our last session, can I move to twice a week?" — the answer depends on her clinical judgement and this person is fragile. Never template, never automate, and be careful even drafting it.
A flat template sounds like a form letter, which loses you the warmth that made the client hire a person. The fix is to build every template with two or three gaps you must fill by hand.
Hi [FIRST NAME],
Thanks for getting in touch — [ONE SPECIFIC LINE RESPONDING TO WHAT THEY ACTUALLY SAID].
I've currently got space on [DAY] at [TIME] and [DAY] at [TIME]. Sessions are 50 minutes and ₦[X].
If either suits, let me know and I'll hold it for you. If neither does, tell me roughly when works and I'll see what I can do.
Best,
Adaeze
The second line is the whole difference. "You mentioned things have been hard since your move — I'm glad you reached out" takes fifteen seconds and makes the other four lines read as a person rather than a system. A template without a hole in it is a form letter with extra steps.
Keep your templates in a shared document the client can see, not locked in your head. Two reasons: she can correct them, and it is visible evidence of work she would otherwise never notice you doing.
The judgement you are really being paid for is knowing when to stop and ask. A simple, defensible standard:
Agree that "line" in your first week — a specific number. "Anything under ₦20,000 I'll just handle and tell you about; anything over I'll ask first." Clients almost never think to set this and are relieved when you do, because it is the thing they were quietly worried about.
When you are genuinely unsure and she is unreachable, there is always one safe move: acknowledge without committing. "Thanks for this — let me look into it and come back to you today." It buys hours, costs nothing, and is infinitely better than either guessing or leaving someone in silence.
Write three templates for a business you know — a school, a shop, a clinic, a church. Mark the holes explicitly in capitals. Then write one sentence for each explaining what would have to be true in a message for you not to use the template. That sentence is your judgement, written down.
You have had a good day. You sorted 340 messages, handled 60, drafted 8, killed 190. Adaeze has no idea. From where she sits, her inbox is quieter and she does not know why, or whether it will still be quiet tomorrow.
This is the gap that gets competent assistants let go. Clients cannot see effort. They can only see output, and only if you show it to them. The end-of-day summary is how you show it, and it takes four minutes.
Three sections, always the same order, always under 150 words. Same order every day matters more than you would think — she learns where to look and stops reading it properly, which is the goal.
Handled (14)
Reschedules for Chinelo, Ify and two others. Rate questions ×3. Confirmed Thursday's supplier order. Cleared 190 newsletters and receipts.
Waiting on you (2)
1. HealthPlan rejected claim 4471 — 14-day deadline, so Friday at the latest. I've drafted an appeal, it's in your drafts. Say "send" and it goes.
2. Speaking invitation for 14 Nov, they need an answer by Friday. Your diary is clear that day. I'd say yes — happy to draft the reply either way.
Tomorrow
Chasing three unpaid invoices, and I'll set up templates for the rate question — it's come up eight times this week.
Never send a question without a recommended answer attached. It is the difference between an assistant and another person who needs managing.
Do not report process — "I spent the morning going through the backlog" tells her nothing she can use. Do not list every single item; count them and name the notable ones. Do not include problems you have already solved, unless she would find out anyway or it might recur. And do not apologise for what you did not finish. State it plainly in Tomorrow and move on.
One thing you must always include, however uncomfortable: a mistake you made. Same day, one line, with the fix already done. "I sent Bola the wrong time for Thursday — caught it, corrected it, she's fine." An assistant who reports her own errors becomes someone whose reports can be trusted entirely. An assistant who hides a small one has taught the client to verify everything, and you will never recover that.
Some clients want this daily; some find daily oppressive and want it Friday. Ask in week one: "Would you rather have a short end-of-day note, or one summary on Fridays?" Then stick to whatever they choose, on time, including the days when there is almost nothing to report. Consistency is what is being tested at rung two. A summary that arrives every day for three weeks and then stops tells the client, accurately, that your attention has moved elsewhere.
Write an end-of-day summary for your own day today, in the three-section format, under 150 words. Include one thing you did not finish and one thing you got wrong. It will feel strange to write about your own day this way, which is the exercise — the format is a habit of thought before it is a message.
You are given one week of Adaeze's real inbox: sixty messages, downloadable, exactly as messy as it sounds. Two clients have written three times about the same thing. One message is genuinely urgent and does not look it. One is from someone in distress. One is a supplier chasing an invoice that was already paid. Two are near-identical enquiries from the same person under different addresses.
The clock is the point. An hour is enough if you sort first and too little if you do not, which is the lesson working rather than being explained.
Not speed, and not writing. Whether you can tell the difference between what is loud and what is load-bearing — and whether, under time pressure with an incomplete picture, you make decisions and write them down instead of freezing or asking permission. That is the whole job, compressed into an hour.
You should now have: a working delegated inbox you have set up yourself, a voice file for a real person, three templates with the holes marked, and one end-of-day summary you have written for your own day. Module 3 takes the calendar, and it assumes you already understand how a Draft reaches a client — because half of calendar work arrives as email.