Inbox command
The inbox is the trust test
When a US founder hires you, the first thing they hand over is the thing they hate most: their inbox. It's also the first place you can destroy trust. Miss one investor email and you're not "the new VA who made a mistake" — you're "the reason we missed the wire deadline." So we don't manage inboxes with vibes. We run a system.
The goal isn't reading every email. It's this: nothing important waits, nothing gets lost, and the founder only touches messages that genuinely need their brain.
The four triage tiers
Every incoming email lands in exactly one tier. Memorize these — they're the backbone of everything else in this lesson.
| Tier | What it is | Your move |
|---|---|---|
| 1 — Fire | Clients, revenue, emergencies, the boss's boss | Surface to founder within the hour, flag in Slack if urgent |
| 2 — Decision | Needs the founder's judgment or signature | Draft the reply, queue for approval |
| 3 — Yours | Routine: scheduling, confirmations, vendor logistics | Handle it, log it in your EOD report |
| 4 — Noise | Newsletters, notifications, cold pitches | Archive, unsubscribe, or filter so it never appears again |
Labels that mean something
In Gmail, build a small, ruthless label set: @Action (founder must act), @Approve (your draft is waiting), @Waiting (you sent something, awaiting reply), plus two or three topic labels like Finance and Travel. Color the @ labels red, orange, yellow. If your label list needs scrolling, you built a filing cabinet, not a triage system.
Here's what a triaged inbox looks like mid-shift:
The daily inbox-zero pass
@Approve. The founder approves or edits — they never write from scratch.Run this pass twice per shift — start and end — and nothing slips. Grace, a VA in Davao working for a Texas agency owner, runs this exact loop from 9pm to 6am Manila time and her founder hasn't opened his own inbox in eight months.
The trust ladder: from drafting to autonomy
You don't earn inbox autonomy by asking. You earn it by drafting so well the founder stops editing. The progression looks like this:
The message that moves you up the ladder
"Inbox is at zero. 3 drafts waiting in @Approve: (1) Jennifer/Acme — accepted the redlines, flagged clause 4 for your read; (2) podcast decline with a Q4 offer; (3) intro to the bookkeeper you asked for. I handled 11 routine threads — list in today's EOD. Only thing needing you tonight is Jennifer; her deadline is Friday."
Notice what this does: it proves judgment (clause 4 flagged), respects their time (one priority named), and shows the system working. Founders promote the VA who writes messages like this.
Do this now
Build the system on your own Gmail. Create the labels (@Action, @Approve, @Waiting) and two filters that auto-archive real noise you receive. Then write a one-page "Inbox Triage SOP" for a fictional founder: the four tiers with two example senders each, your daily pass schedule in both PH time and the client's timezone, and the three things you'd never send without approval. Save it as a doc — this SOP goes straight into your portfolio in Lesson 7. About 20 minutes.
Tip: use your ← → arrow keys.