KoltrixHow to build an email triage rota for a team of three to ten
A runbook for a shared-inbox triage rota: shift length, triager duties, handoffs, fairness, holidays, and a sample two-week schedule for small teams.
On this page(10 sections)
When everyone watches the shared inbox, nobody really does. A triage rota fixes that by making one named person responsible for first contact at any given hour, while everyone else gets to focus on their actual work.
This runbook covers how to set one up for a team of three to ten people: shift design, the triager's duties, handoffs, fairness and the boring-but-essential holiday rules. At the end there's a sample two-week rota you can copy.
What the triager is (and isn't) responsible for
Write this down before scheduling anyone. A vague role turns into either "answers everything" (burnout) or "glances occasionally" (dropped mail).
The triager does:
- Looks at every new thread in the shared inbox at least every hour or two during the shift
- Sorts and labels each thread so its type is obvious
- Answers quick ones directly: anything that takes under five minutes and needs no special knowledge
- Routes the rest to the right person with a one-line note on what's needed
- Flags anything urgent immediately in the team chat
- Writes a short handoff at the end of the shift
The triager does not:
- Solve every hard problem personally
- Own every thread they touched forever
- Decide policy questions (refund exceptions, custom contracts) alone
The "route the rest" part only works if routing rules exist. A simple table helps:
| Thread type | Route to | Triager's first step |
|---|---|---|
| Bug report | Product engineer on duty | Ask for repro details if missing |
| Billing question | Finance owner | Acknowledge, link to billing page if relevant |
| Sales inquiry | Founder or sales lead | Acknowledge within the shift |
| How-to question | Answer directly | Link docs where possible |
| Security or legal | Founder | Do not reply; flag immediately |
Step 1: Pick a shift length
There are two common options for small teams.
Full-day shifts (one person per working day) work well when volume is moderate and everyone has deep-work tasks. The triager accepts a fragmented day; everyone else gets an uninterrupted one. With five people, each person triages roughly one day a week.
Half-day shifts (morning and afternoon) suit teams where triage is intense or people find a full day of interruptions draining. Shorter shifts mean more handoffs, so the handoff note matters more.
Avoid shifts shorter than half a day. Each handoff costs context, and hourly rotations mean nobody is ever responsible for anything for long enough to finish it.
Step 2: Decide who is on the rota
Not everyone needs to be. Include people who can answer common questions and know where to route the rest. A new hire can join after their first couple of weeks, ideally paired with an experienced triager for their first shifts.
Founders often exclude themselves. In a team of three, that's rarely realistic. In a team of ten, it may be fine, as long as the founder still reads the weekly summary.
Step 3: Define the handoff
The handoff is where rotas fail. At the end of each shift, the outgoing triager posts a short note. Keep a fixed format so it takes two minutes:
Triage handoff – Tue PM → Wed AM
Open, waiting on us:
- [Customer A] export failing – routed to Priya, she's reproducing
- [Prospect B] pricing question – drafted, needs founder review
Waiting on customer:
- [Customer C] asked for screenshots, follow up Thursday if silent
Watch out for:
- Payment provider had an incident at 3pm; expect billing questions
The incoming triager reads it first, then checks the inbox. Anything not in the note and not handled is fair game to ask about directly.
Step 4: Make it fair
Rotas breed resentment when the load is uneven. A few practices help:
- Rotate days. If Mondays are always the heaviest, don't give them to the same person every week.
- Count shifts over a month, not a week. Holidays and sick days will cause short-term imbalance; correct it over time.
- Lighten other work on triage days. If someone's triage day also has a deadline, swap. The rota is a real job, not a side task.
- Let people trade, with one rule: the trade is posted where everyone can see it.
Step 5: Plan for holidays and sick days
Decide in advance:
- Who covers when the scheduled person is out unexpectedly. A simple "next person in the list" rule avoids a scramble.
- What happens on public holidays. Either nobody triages (and an auto-reply says so) or someone does and gets a day back later.
- How far ahead swaps for planned leave should be arranged. A week is reasonable.
Sample two-week rota for a five-person team
Full-day shifts, rotating so nobody gets the same weekday twice in a row:
| Mon | Tue | Wed | Thu | Fri | |
|---|---|---|---|---|---|
| Week 1 | Ana | Ben | Chen | Dee | Eli |
| Week 2 | Ben | Chen | Dee | Eli | Ana |
For a three-person team on half-day shifts:
| Mon | Tue | Wed | Thu | Fri | |
|---|---|---|---|---|---|
| AM | Ana | Ben | Chen | Ana | Ben |
| PM | Ben | Chen | Ana | Ben | Chen |
Next fortnight, shift everything one slot to the right.
Step 6: Review after a month
After four weeks, hold a 20-minute review:
- Did any thread fall through a handoff? Why?
- Were some days consistently overloaded?
- Did the routing table cover what came in, or did new types appear?
- Does anyone dread their shift? What would fix that?
Adjust shift length or routing based on the answers, not on guesses made before you started.
Runbook checklist
- Triager duties written down, including what they don't do
- Routing table for common thread types
- Shift length chosen (full day or half day)
- Rota members agreed; new hires paired for first shifts
- Handoff template posted where everyone can see it
- Cover rule for unexpected absences
- Holiday policy decided
- First review scheduled four weeks out
Key takeaways
- A rota makes one person clearly responsible for first contact, which frees everyone else to focus.
- The triager sorts, answers quick ones and routes the rest; they don't solve everything.
- Full-day or half-day shifts both work. Shorter shifts create too many handoffs.
- A fixed two-minute handoff note is what keeps threads from falling through.
- Rotate days, count shifts monthly, and review after the first month.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
