AfterDesk
EN
Apply

The toolkit

Email and inbox management

Running someone else's inbox is the most common virtual assistant job and the one clients trust least easily. This course gives you a triage system that survives three hundred messages a day, the free Gmail setup that does the sorting for you, clear rules on what to send and what to escalate, and a handover note that shows exactly what happened while your client slept.

9
lessons
~69
minutes
12
exam questions

Free · No paid tier · No certificate fee

After this course

Everything, and what is in it.

What running an inbox really means

~7 min

The job is decisions, not reading

An inbox is not a reading list. It is a queue of decisions somebody has to make, and your client hired you so they make fewer of them. On any morning, most of what arrives needs no decision from them at all: receipts, newsletters, calendar noise, replies confirming something already agreed. A smaller pile needs a short answer that you can write. A very small pile genuinely needs their judgement. Your value is the sorting, not the typing. A client who opens the inbox and sees eleven messages instead of three hundred and ten will keep you for years. Measure yourself on that number, not on how many replies you sent.

Access without passwords

Ask for delegated access before you ask for a password. Gmail lets an account owner add a delegate: you open their mail from your own logged-in account, you read, reply and archive, and replies show as sent by you on their behalf. Google Workspace administrators can also set up a shared mailbox. Both leave a clean trail, both can be switched off in one click, and neither puts their password on your machine. If a client offers the password anyway, explain delegation first, and say plainly that it is safer for them. Keep two-factor codes on their side, never yours. Use a password manager for anything you do hold, lock your screen, and never open a client inbox on a borrowed computer.

Confidentiality is the whole contract

Everything in that inbox belongs to the client. Salary conversations, unsigned contracts, a supplier dispute, a medical appointment: you will see all of it, and none of it leaves the inbox. Do not forward client mail to your own address to read later. Do not paste client email into a translator, a grammar checker or an AI assistant unless the client has written that it is allowed and named the tool. Do not screenshot anything for a portfolio, a course or a friend. When a task is done, delete local copies of attachments from your downloads folder. If someone outside asks what your client is working on, the honest answer is that you do not discuss client work. Say it once, plainly, and it is never awkward again.

How AfterDesk differs

AfterDesk tasks never give you a client inbox, and you never write to a client's contacts. There is no chat, no calls, no direct thread of any kind. What you may get is the flat version of this work: a set of exported messages to sort and summarise, a batch of replies to draft in a document, a template library to build, a contact list pulled out of a thread. You do the thinking, you upload the file with a note to the operator, and the operator reviews it before anyone sees it. Everything else in this course is for the inbox work you do for other clients directly, where you hold the keys. Both need the same judgement. Only one lets you press send.

Remember

  • Your value is the sorting, not the typing. Count what you removed from their day.
  • Ask for delegated access, not a password. Safer for the client and for you.
  • Client mail never leaves the inbox: no forwarding, no AI tools, no screenshots, no portfolio.
  • On AfterDesk you never touch a client inbox or contact anyone. The operator does.

Triage that survives 300 messages

~8 min

Sort by decision, not by topic

Topic folders feel tidy and do nothing for you. Sort by the decision instead. Every message lands in one of four lanes. Handle: you can deal with it completely, today, without asking. Draft: an answer is needed, you can write it, they approve before it goes. Theirs: only they can decide, so it goes in front of them clean and summarised. Nothing: file it, archive it, or let a filter make it disappear before you ever see it. The question that sorts a message in two seconds is not what is this about, it is who has to decide this. A newsletter and an invoice can share a sender and belong in different lanes. Build your labels around these four and the inbox starts running itself.

The first pass: no replies

Open the inbox and write nothing on the first pass. Scan from newest to oldest, label each message into its lane, archive the nothing pile, and move on. Do not open attachments, do not start replies, do not go looking things up. This feels wrong the first week and it is the single biggest speed gain available to you. Two reasons. Replying puts you in writing mode, and switching between scanning and writing costs more time than either task. And the message you would have spent twenty minutes on at seven o'clock is sometimes cancelled by one that arrives at half past. Three hundred messages take about twenty minutes to label. Then you sit down and work the lanes in order, with the whole picture in front of you.

Touch it once

After the sweep, work each lane top to bottom and finish what you open. If a message is in Handle and the reply takes under two minutes, write it and archive it. If it takes longer, it was mislabelled: move it to Draft. The habit to kill is reading a message, feeling unsure, and leaving it unread to think about later. Unread is not a decision, and tomorrow you will read it again from scratch. If you truly cannot act, that is information: label it Waiting or Theirs with a one-line note saying what is missing. Every message you read twice is a message you have paid for twice. The inbox should empty in one direction only.

Timeboxing the sweep

Agree the rhythm in writing with your client before your first shift. A common shape is three sweeps: one at the start of your shift, one mid-shift, one before you hand over. Between sweeps the inbox is closed. Constant monitoring feels responsive and produces a day with no finished work in it. What matters more than frequency is that the client knows the schedule, so nobody waits on a reply that was never coming for six hours. Then define urgent narrowly with them: a named customer, a specific supplier, anything with a same-day deadline. Everything else waits for the next sweep. Write the rule down where you both can see it, because urgent means different things to the two of you.

What deserves an alert

Some things cannot wait for the handover note, and interrupting your client is a tool you spend carefully. Agree one channel for it and use only that channel. A good alert is short and contains the decision needed, the deadline, and what you have already done. Not a forward with no comment. Not five separate pings in ten minutes: batch them if they arrived together. Interrupt for a missed deadline that is still recoverable, a payment or legal notice, an angry message from a named account, a meeting change inside the next few hours, or anything you suspect is a security problem. If you are alerting more than once or twice a week, the escalation rule is too wide, and you should fix the rule rather than the habit.

Remember

  • Four lanes: Handle, Draft, Theirs, Nothing. Ask who has to decide.
  • Label the whole pile before you write a single reply.
  • Unread is not a decision. Read once, decide once.
  • Three sweeps a day beats all-day monitoring, if the client knows the schedule.
  • An alert names the decision, the deadline, and what you already did.

Labels, filters and search that work

~8 min

Build labels from the four lanes

Keep the label list short enough to use at speed. Start with four: Handle, Draft, Theirs, Waiting. Gmail sorts labels alphabetically, so prefix them with a digit if you want them in working order, and give each a strong colour so you can read the lane from the message list without stopping. Underneath those, add only labels you will actually filter on: one per recurring sender group, one per active project, one for receipts. Resist a label per topic. Twelve labels is a system, sixty is a second inbox. Review the list monthly and delete anything you have not clicked in four weeks. Labels are not filing cabinets, they are handles you grab while moving fast.

Filters do the sorting you repeat

A filter is a rule that runs before you look. In Gmail, open a message of the kind you want handled automatically, use the menu to filter messages like these, adjust the criteria, and choose what happens. Four recipes cover most inboxes. Newsletters and marketing: skip the inbox, apply a Reading label, mark as read. Receipts and invoices: skip the inbox, apply Receipts, never mark as spam. Named important senders: apply a colour and a star, never skip the inbox. Automated notifications nobody reads: skip the inbox and label them. Build filters from what you actually did last week, not from what you imagine arriving. Two new filters a week for a month will halve the volume you personally touch. Never set a filter to delete.

Multiple inboxes on one screen

Gmail has a layout called multiple inboxes that turns your lanes into panels on one screen. In settings, choose it as your inbox type, then define each section with a search query: one for the Draft label, one for Theirs, one for Waiting, and the main inbox for anything not yet sorted. You get the whole workload without clicking between labels, and an empty panel is a visible finish line. Set the section titles in plain words your client would understand, because you will screenshot this view or describe it in a handover. If the screen gets crowded, cut the number of rows per section rather than removing a section. On a small laptop, put the sections below the inbox instead of beside it.

Search operators worth memorising

Search is faster than any folder, once you know six operators. from: and to: narrow by person. subject: searches the subject line only. has:attachment with filename:pdf finds the document somebody swears they sent. after: and before: with a date bracket a period, and older_than:1y takes a year in one step. A minus sign excludes, so from:accounts -label:receipts shows what your filter missed. Quotation marks force an exact phrase. in:anywhere reaches spam and trash when a message has vanished. Combine them freely. When a client asks whether they ever approved something, a good search finds the answer in fifteen seconds, and that one skill will convince them faster than any tidy label scheme.

Archive, do not delete

Archiving removes a message from the inbox and keeps it findable forever. Deleting removes the client's record. You do not know which supplier thread becomes a dispute in eight months, so archive by default and let search do the rest. The exceptions are obvious spam and genuine duplicates, and even those can simply be archived. Never empty a client's trash. Never build a filter that deletes. If the client asks you to clear space, treat that as a conversation to have with them, not an afternoon of quiet deleting. Unsubscribing is different and welcome: use the unsubscribe link on real newsletters they no longer read, one at a time, and note in the handover which ones you removed so nothing disappears without them knowing.

Remember

  • Four lane labels plus a handful more. Twelve is a system, sixty is chaos.
  • Build filters from last week's real messages. Never let a filter delete.
  • Multiple inboxes puts every lane on one screen at once.
  • Six operators beat any folder tree: from, subject, has:attachment, dates, minus, quotes.
  • Archive by default. You do not know which thread matters in a year.

What you send, draft, or escalate

~8 min

The authority document

Before you send a single message on someone's behalf, write down what you are allowed to send. Make a short Google Doc with two columns: kinds of message, and what you do with them. Fill it in with real examples from their last month, not categories in the abstract. Meeting reschedule with an existing contact: send. New customer asking for pricing: draft. Anything from their accountant: leave for them. Get the client to read it and reply in writing that it is right, and keep that reply. This document protects both of you. When something goes wrong, and eventually something will, the question is never who is to blame, it is what did we agree. Review it monthly and move items up as trust builds.

Send, draft, or theirs

Level one is send: routine, factual, reversible, and covered by a rule you already agreed. Confirming a meeting, sending an address, replying that a document arrived, forwarding to the right person internally. Level two is draft: you probably know the correct answer, but it commits your client, sets a price, expresses an opinion, or goes to somebody who matters. You write the whole reply, leave it in drafts, and flag it in your handover so approval takes thirty seconds instead of thirty minutes. Level three is theirs: you do not write it at all, you summarise it. The test between one and two is simple. If the reply would be embarrassing or expensive to take back, it is a draft. When unsure which level applies, treat it as the higher one.

The never-touch list

Some mail you never answer, never draft, and never file away quietly. Anything legal: a demand letter, a dispute, anything with a lawyer copied. Anything that moves money: payment instructions, bank details, invoice changes, refunds. Anything about people: hiring, firing, complaints, salaries, references. Press and interview requests. Messages from the client's family or their doctor. Password resets and security alerts, which you flag rather than click. And any message asking for something urgent and unusual, especially if it appears to come from your client and pushes you to move fast: that is the shape of a fraud attempt, and the answer is always to confirm through a different channel. Put this list in the authority document, word for word, so it is never a judgement call at midnight.

Escalate without dumping

Handing a message up is a piece of work, not an act of forwarding. A dumped escalation reads as three letters and a wall of quoted text. A useful one gives the decision in the first line, then who is asking, what they want, the deadline, what you found when you checked, and two or three options with your recommendation. Three or four sentences is usually enough. If you have drafted a possible reply, say so and where it is. If you already did something, such as buying time with a holding message, say that too so they do not repeat it. Your client should be able to answer with one word. That is the standard: they read six lines, type yes, and the thing is finished.

Widening authority over time

Authority should grow, and it will not grow unless you make it easy. Keep a private note of every draft your client approved without changing a word. After a month, take the three categories with the most untouched approvals and propose moving them to send, with the exact wording you would use. That is a concrete request with evidence behind it, and most clients say yes. The reverse matters too. If a draft comes back edited, read the edit and write down what changed, because the same correction twice is a rule you have not learned yet. Never widen your own authority quietly because it seemed obvious. Sending one message you were not cleared to send costs more trust than a hundred good ones earn.

Remember

  • Write the authority document before your first send, and keep the client's written yes.
  • Send, draft, or summarise. If a reply is expensive to take back, draft it.
  • Never touch legal, money, personnel, press, or security alerts. Flag them.
  • An escalation gives the decision, the deadline, the options, and your recommendation.
  • Grow your authority with evidence, never quietly.

Writing in someone else's voice

~8 min

Read the sent folder first

Before you write anything, spend an hour in their sent folder. Read fifty of their own replies, and read across different recipients: a customer, a supplier, a colleague. You are looking for mechanics, not personality. How do they open, and does it change with the recipient. Do they use first names. Are their sentences short or long. Do they thank people in advance, or not at all. How do they say no. How do they close, and what is the exact sign-off. Do they use contractions, dashes, one-line paragraphs. Notice what they never do, which is usually more distinctive than what they do. Copy ten replies you consider typical into a document as reference. That hour saves you a month of corrections.

Build a voice sheet

Turn what you found into a one-page sheet you keep open while writing. List the greetings they use and who gets which. The sign-off exactly as they type it, including the line breaks. Five phrases they actually use. Five phrases they never use, which for many people includes please be advised, kindly, and hope this finds you well. Their answer to the three situations you will face most: saying no, buying time, asking for information. Typical length in sentences, because most assistants write too much. Their rules about names, titles and how the company is written. Add to it every time a draft comes back edited. When somebody else eventually covers your shift, this sheet is what you hand them, and it is worth more than any briefing.

The line you do not cross

Writing in someone's voice is not pretending to be them, and the difference is not subtle. From a delegated Gmail account, recipients see that the message was sent by you on their behalf, and that is correct and normal. Do not remove it, and do not set up an account that hides it. Never sign a message with your client's name as though they typed it unless they have told you in writing that this is how they want it done, and keep that instruction. Never agree to a contract, a price or a legal commitment in their name. Never use their identity to verify anything, and never confirm a payment change. If a message would only work because the reader thinks the client wrote it personally, it is not yours to send.

Structure carries more than style

Recipients judge a reply on whether it answered them, and only afterwards on how it sounded. Answer the actual question in the first sentence, even when the answer is no or not yet. Put any request for action in its own short paragraph so it survives being read on a phone. If there are dates or numbers, repeat them exactly as the sender wrote them. One topic per email: a reply that answers three questions gets a response to one. Say what happens next and who does it. Then stop. Most drafts get shorter when you delete the first paragraph, because the first paragraph is usually you clearing your throat. Good structure in slightly wrong voice reads as competent. Perfect voice with a buried answer reads as an assistant who missed the point.

When your own voice is better

Not everything should sound like your client. When you write as yourself, clearly as their assistant, use plain professional English and stop performing. Scheduling, chasing documents, confirming details and coordinating logistics are usually faster and clearer coming from you, and many clients prefer it because it protects their own name for the things that need it. Ask which of these they want in their voice and which in yours. AfterDesk works on the same principle: what you upload is a draft, the operator reviews it, and nothing goes out under anyone's name until it has passed that review. The skill is knowing whose name a message needs, not proving you can imitate anyone.

Remember

  • Fifty sent messages tell you more about voice than any briefing call.
  • Keep a one-page voice sheet, and update it every time a draft is edited.
  • On behalf of is honest. Never sign as them without written instruction.
  • Answer in the first sentence. Structure beats style every time.
  • Some messages are better in your own name. Ask which ones.

Templates that do not sound robotic

~7 min

Templates come from repetition

Do not sit down to write templates. Work a normal week and keep a tally of every reply you write more than twice: the same information request, the same booking confirmation, the same polite no, the same document chase. At the end of the week you will have between six and twelve. Those are your templates and nothing else is. For each one, take the best version you actually sent, not a fresh idealised draft, and strip out everything specific into visible gaps like NAME, DATE and AMOUNT in capitals. Capitals matter: a half-filled template is the classic embarrassment, and NAME sitting in the middle of a sentence is impossible to miss on a final read. Templates built this way already sound like the person, because they came from them.

Gmail templates, step by step

Gmail calls them templates and they are off by default. In settings, open the advanced tab and enable templates. Then compose the message, open the three-dot menu at the bottom right of the compose window, choose templates, and save the draft as a new one with a name you will recognise in a list of twenty. To use it, start a reply, open the same menu, and insert. You can also attach a template to a filter so an incoming message of a known kind gets a reply automatically, which is useful for a genuinely fixed acknowledgement and dangerous for anything else. Name templates by situation, not by number: Chasing missing invoice, Declining meeting request, Booking confirmed. You will be reading that list under time pressure.

The two-line rule

A template becomes robotic in one specific way: the reader can tell that nothing in it was written for them. Fix it with two lines. The first line refers to something only their message contains, in your own words, not a quotation. Thanks for sending the revised floor plan, the ceiling heights are what we needed. The last line says what happens next and when, with a real date. Between those two, the body can be entirely standard and nobody will notice. Then read the whole thing once before sending, out loud if you can, because that is when you catch the wrong name, the leftover NAME, the pricing from a different customer, and the cheerful sentence that does not belong in a message about a delay. Two lines and one read-through is the whole discipline.

When a template is wrong

Some messages must be written from nothing. Anything after a mistake, yours or the company's. Any reply to a person who is upset, because a template is exactly what they will smell and it will make them angrier. Anything where the sender has clearly written at length and personally. Bad news of any kind. Any first message to somebody who matters. Anything where a wrong detail costs money. In each of these, the value of the reply is the evidence that a human read theirs. You can still hold a structure in your head, apology, cause, fix, next step, but every sentence gets typed. If you are ever unsure whether a situation deserves a template, it does not.

Maintaining the library

A template library rots. Review it once a quarter: open each one, read it as a stranger, and check the details that expire. Prices, hours, addresses, links, staff names, product names, the sign-off. Delete anything you have not used in three months, because a stale template is worse than none, and the day you reach for it in a hurry it will name someone who left in March. Keep the master list in a Google Doc as well as in Gmail, so it survives an account change and so your client can read it. Show them the library. Most clients have never seen the words their inbox sends on their behalf, and reading it is often the moment they realise how much of their day you are carrying.

Remember

  • Templates come from replies you already wrote twice. Nothing else qualifies.
  • Leave gaps in capitals so a half-filled template is impossible to miss.
  • Personal first line, dated last line. The middle can be standard.
  • Never template an apology, bad news, or a reply to someone upset.
  • Review the library quarterly. Delete anything unused for three months.

Handling angry and difficult email

~8 min

Slow down the loop

An angry email is a timing problem before it is a writing problem. The first draft you write in the first two minutes will be defensive, and it will contain a sentence you cannot take back. Write it if it helps, in a blank document, then close it without saving. Then check three things before you touch the reply: what actually happened, what was actually promised, and whether this person is angry for the first time or the third. The third time changes everything, and it will be in the thread history. Speed still matters, so do not go quiet for a day. A short honest acknowledgement inside an hour cools more situations than a perfect reply the next morning. What you must not do is answer at the same temperature they wrote.

What you can send without permission

Even with narrow authority, you can almost always send an acknowledgement, and it is the most valuable message in the whole exchange. It has three parts and no fourth. You have received it and read it. It is with the person who can decide, named if that is normal. When they will hear back, with a specific time you can actually keep. What you never do without permission: admit fault, name a cause, promise a refund or a discount, blame a colleague or a supplier, or explain what went wrong internally. Words like our mistake and we will fix it are commitments made in someone else's name. Confirm the one promise you can keep, which is the reply time, then keep it. If that deadline slips, write again before it passes, not after.

Acknowledge, facts, next step

When you are cleared to answer properly, the shape is short. Acknowledge what they lost, not their feelings: the delivery missed Friday and that cost you the weekend. Then the facts in order, dated, with no adjectives, including the part that is not flattering to your side. Then the next step, with a name and a date. No paragraph about how much the company values them. No use of the word regret doing the work of a fix. If some of the fault is theirs, state the sequence and let it speak, because we did not receive a reply to our email of the fourth is a fact, while you failed to reply is a fight. Read it once more and delete every sentence that exists to make your side feel better.

The ones you never answer

Some messages leave the inbox routine immediately, whatever your authority says. Anything mentioning a lawyer, a court, a regulator or a chargeback. Anything using publicity or a public review as leverage. Personal abuse or threats aimed at anyone. Anything about the death, illness or serious personal trouble of a named person. Anything alleging discrimination, harassment or a safety problem. For all of these you do one thing: send it to your client with a one-line summary, say that you have not replied and will not, and stop. Do not acknowledge, do not apologise, do not ask a clarifying question, because in a dispute every line you write becomes part of the record. Then log it: date, sender, subject, what you did. That log has saved a great many assistants.

Protecting yourself

You will be shouted at for things you did not do, and the shouting is not about you. Do not carry it into the next message. Two habits help. Never reply to an angry email as the last thing you do in a shift, because tired and stung is the exact state that sends something regrettable. And never argue the same point twice in one thread: if the second reply comes back at the same temperature, it is a decision for your client, not another attempt from you. If a client is the one being abusive to you, that is a different situation and it is not part of the job. Write it down, keep the messages, and decide with a clear head whether to continue. Good clients do not shout at their assistants.

Remember

  • Never answer at the same temperature. Write the angry draft, then close it unsaved.
  • You can always acknowledge: received, with whom, by when. That needs no permission.
  • Never admit fault, name a cause, or promise money without written authority.
  • Lawyers, threats, abuse or discrimination: pass it up, do not reply, log it.
  • Never send an angry reply as the last thing in your shift.

The follow-up loop

~7 min

Every loop needs a name and date

Most of what goes wrong in an inbox is not a bad reply, it is a message nobody answered and nobody noticed. The moment you send something that needs a response, or your client does, it becomes an open loop, and every open loop needs two things attached: a person and a date. Who owes what, by when. Without the date it is a hope. This runs in both directions. Their unanswered requests to other people are the obvious half. The half that gets forgotten is what your client owes: the quote they said they would send, the reference they promised, the form the accountant needs. You are the only person holding the whole picture, and tracking it is often the service a client notices most.

The Waiting label and snooze

Two Gmail features do the work. When you send something that needs an answer, apply your Waiting label to the sent message so the thread lives in one visible place. Then snooze the thread to the date you would chase, and it returns to the top of the inbox that morning. Use them together, because snooze alone hides the item until the day and you lose the overview, while a label alone needs you to remember to look. Snooze to a working morning, not to a Friday evening or a Sunday. When the answer arrives, remove the label the same minute, because a Waiting list full of things that already came back stops being trusted within about a week. An empty Waiting label at the end of a shift is a real achievement.

A tracking sheet that survives

For anything that outlives a week, the label is not enough and a Google Sheet is. Six columns: what, who owes it, asked on, chase on, status, link to the thread. One row per open item. Sort by chase date so today's chases sit at the top. Colour only the overdue rows, red, and nothing else, because a sheet where everything is coloured tells you nothing. Share it with the client in view or comment mode and put the link in every handover note, so they can look without asking you. The sheet is also your protection. When somebody says they never received a request, the row shows the date and the thread proves it. Keep it in the client's own Drive, not yours, so it stays theirs when the work ends.

Chasing without nagging

A chase should be easy to answer and impossible to take badly. Reply inside the original thread so the whole history is right there. Keep it to two sentences: what you need, and the date you need it by. Never open with an accusation about not hearing back, and never write just following up, which says nothing and invites nothing. Make the answer cheap: offer two dates rather than asking for availability, attach the form again rather than referring to it, or say that a yes or no by Thursday is enough. A workable rhythm is three days, then a week, then a fortnight, then stop and tell your client the item is stalled. After the second chase the problem is no longer a missing email, and pushing harder will not fix it.

Closing the loop out loud

Finished work that nobody saw finish still costs your client attention, because they are still carrying it. When a loop closes, say so in one line in the handover: the signed contract came back from the supplier on Tuesday, filed in the shared folder, nothing needed from you. Then remove the label and mark the row done. Keep completed rows on a second tab rather than deleting them, because a month of closed loops is the clearest evidence of your value that exists, and it will be there when you ask about rates or when the client wonders what they are paying for. On AfterDesk your delivery note does the same job: a short, plain statement of what is finished and what still needs a decision.

Remember

  • Every open loop gets a person and a date. Without a date it is a hope.
  • Waiting label plus snooze. Remove the label the minute the answer lands.
  • Track long items in the client's own Google Sheet, sorted by chase date.
  • Chase in-thread, two sentences, with a date. Never write just following up.
  • Say when a loop closes. Closed loops are the record of your value.

Daily routine and the handover note

~8 min

The shift routine

A routine turns a stressful inbox into a shift with a shape. Start with the sweep: label everything, archive the noise, write nothing. Then work Handle top to bottom and empty it. Then write the Draft lane, leaving each reply in drafts, and note which ones are time-sensitive. Then prepare the Theirs lane: summarise each one in a line or two so your client reads your summary and not a forwarded wall. Then the chases due today from your sheet. Then a short second sweep for whatever arrived while you worked. Then the handover note, written last and never skipped. Same order every day. The order matters more than the timing, because a fixed order is what lets you stop thinking about the inbox and start thinking about the work.

Working while they sleep

If you work while your client sleeps, you have an advantage office assistants never get: several uninterrupted hours in an inbox that is not moving. Use them for the work that needs quiet, the drafts and the sorting and the sheet, and leave anything needing an answer from a colleague for the overlap window. Agree one or two hours of overlap in writing and hold them, because a week without a single shared hour turns small questions into two-day delays. Know their public holidays and working days, not only yours, and write both calendars somewhere you both see. Be careful with send times too: a reply landing at three in the morning their time can read as pressure, so use schedule send to land messages in their working morning.

The handover note

The handover note is what your client reads with their first coffee, and for many of them it is the whole product. Keep it under twenty lines, in the body of one email, never as an attachment. Five parts, always in the same order. Needs you today: the decisions only they can make, numbered, each with its deadline. Drafts waiting for approval, with the recipient and one line on what each says. Done and closed: what you handled, one line each, so they can stop carrying it. Waiting on others, with the chase dates. Anything unusual: a new sender, a change in tone, something you were not sure about. Then stop. No greeting paragraph, no apologies, no summary of the summary. Same headings every day so their eye knows where to land.

The weekly reset

Once a week, in a quiet hour, do the maintenance the daily routine has no room for. Empty the Waiting label of everything that has come back. Read the whole tracking sheet, not only today's rows. Review which filters fired most and add one or two new ones from the week's repetition. Unsubscribe from three things nobody reads. Read the last drafts your client edited and update the voice sheet. Check the authority document against anything that surprised you. Then write a short weekly note: how many messages arrived and how many actually reached them, what changed, and what you propose to automate next. That last part is what turns an assistant into someone the client plans around instead of someone they instruct.

Proving invisible work

Inbox work is invisible when it goes well, which is a real professional risk. Nobody notices the two hundred messages that never reached them. Keep three simple numbers each week: messages received, messages that needed the client, and open loops closed. A Gmail search with a date range gives you the first two in a minute. Show the trend monthly, not daily. Do not dress it up, and never chase a number by pushing borderline messages out of their proper lane, because the moment a number stops being honest it is worthless. Keep the record for yourself as well. When you ask for a rate increase or apply for larger work, the sentence that lands is that you took an inbox from three hundred and ten daily messages to eleven decisions.

Remember

  • Same order every shift: sweep, handle, draft, summarise, chase, sweep, handover.
  • Their night is your quiet time. Protect one or two overlap hours in writing.
  • Handover note: needs you, drafts, done, waiting, unusual. Under twenty lines.
  • One weekly maintenance hour keeps the whole system from rotting.
  • Keep three honest numbers. Invisible work needs a record.

Sit the exam

The courses are free. The work is real.

Twelve scenario questions. Pass at ten. Three attempts a day. The bar is the point.

No paid tier. No certificate fee. No upsell. Not now, not later.

Create a free account

You can start the first course tonight.

The curriculum

Everything, and what is in it.