Inbox management for a team is a different problem from managing your own inbox. One person can read, decide and remember everything. Five people sharing a mailbox at 500 emails a day cannot. This guide lays out the team version: five jobs, the rules that keep them done, three numbers that show whether it works, and the tools at each level.
Give every thread one owner and replace folders with four states: open, waiting on us, waiting on them, done. Sweep the inbox daily at a fixed time, and snooze nothing without a date and a reason. Measure first response time as a median and as the slowest 10 percent, and count overdue promises weekly. Gmail and Outlook run a light version; past a few hundred emails a day you need shared inbox software.
Why personal inbox-zero advice fails for a team mailbox
The email management tips that circulate are written for one reader. Touch it once, decide, archive. They work because the person who reads the email is the person who acts on it and remembers it. In a team mailbox those are three different people on a bad day, and the advice breaks at each handoff.
Archive means something different when five people share the view. One person's done is another person's never seen. Folders become personal filing systems that nobody else can read. Reading gets confused with owning: everyone opens the message, everyone assumes someone else is on it, and the client waits. At 500 emails a day, either each person reads everything or nobody does.
The five jobs a team inbox has to do every day
A shared mailbox has five jobs, and each has a visible failure when it is skipped. The failure column is how you find out which job your team is missing.
| Job | What it means | What breaks without it |
|---|---|---|
| Triage | Every new message is sorted within the hour: who it is for, how urgent it is, and whether a person needs to reply at all | Urgent mail waits behind newsletters, and the team reads the whole inbox to find the two threads that matter |
| Ownership | One named person is responsible for each thread until it is done | Two people reply to the same client, or nobody does |
| Follow-through | Promises made in replies are tracked until they are kept, and silent threads are chased | The quote you said you would send on Thursday goes out the following Wednesday, after the client asks |
| Record | Anyone can open a client and see what was asked, promised and sent, with the internal reasoning | Context lives in one person's head and leaves with them on vacation |
| Review | Someone looks at the numbers each week and changes one thing | The same slow Monday happens every Monday |
Seven rules that hold at volume
One owner per thread
Every thread gets a name on it the moment it is triaged, and that name stays until the thread is done. Reassignment is allowed and visible. The rule removes 'is anyone on this?' from the team's day and makes reply time someone's number. Assignment can be by hand, round robin or by load, as long as it happens on arrival.
States instead of folders
Folders answer 'where did I put it?' States answer 'whose move is it?' Four are enough: open, waiting on us, waiting on them and done. Waiting on them is the one teams skip, and it is the one that catches the silent client. When a client replies, the thread moves back to waiting on us without anyone touching it.
A daily sweep at a fixed time
Pick a time, 9 am or 4 pm, and have the owner of the inbox that day read every open thread once. Anything with no owner gets one. Anything waiting on us for more than a day gets a reply or a reason. The sweep is short if triage is working, and it is the whole morning if it is not.
Snooze with a promise
Snooze is where threads go to die. Allow it only with a date and a line that says what will happen on that date: 'check the contract came back' or 'send the revised quote'. Then the thread returns as a task with a reason, and the person who picks it up knows what to do. A snooze with no promise is an archive with a timer.
Templates for the twenty replies that repeat
Pull last month's sent mail and list the replies that repeat: the welcome, the where is my document, the invoice question, the meeting confirmation. Write each one once with the blanks marked, and keep them where the composer is. Twenty templates cover the routine part of the day and leave the team's attention for the hard replies.
Rules for machine mail
Notifications, receipts, calendar invites and newsletters make up a large part of a client-facing inbox. None of them need a person to reply. Write rules that tag them, mark them done, and move them out of the open view on arrival. A good rule set means the daily sweep only ever shows mail from people.
A weekly look at the numbers
Once a week, the same person opens the same three numbers and changes one thing: a rule, a template, an assignment pattern. The numbers are in the next section, and the habit is the job the table above calls review.
The three metrics that matter
First response time is the time from a client's message to the first human reply. Report it as a median and as the slowest 10 percent, which analysts write as p50 and p90. The median describes the normal day. The p90 describes the threads that waited, which are the ones clients remember. An average mixes both and hides each.
Reply coverage is the share of inbound threads from people that received a reply within the window you promised. It catches the thread that was triaged, assigned and then forgotten, which first response time alone misses because there was no response to time.
Overdue commitments are the promises the team made in writing and has not kept past their date. Count them weekly, per person. It is the number that tracks the follow-through job, and the one that predicts the next unhappy email.
Tools, from native features to shared inbox software
The system does not need a particular tool. The tool decides how much of it the team does by hand, and at what volume the manual version stops holding.
Gmail and Outlook on their own
Both run a light version for one inbox and a small team. Gmail has labels for states, filters for machine mail, snooze with a date, templates in the composer, and delegation so a second person can read and reply. Outlook has categories, rules, Quick Steps, My Templates and follow-up flags. Neither has an owner field, internal notes or a reply time report, so those jobs live in a spreadsheet.
Google Groups collaborative inbox
A Google Group with collaborative inbox turned on gives a shared address with assignment. Members can assign a conversation, mark it complete or duplicate, and filter by status or assignee. It has no internal notes, no snooze and no reporting, and the interface is the Groups site rather than Gmail.
An Outlook shared mailbox
A Microsoft 365 shared mailbox opens next to each member's own mailbox, and replies go out from the shared address. Categories can stand in for states, and rules can handle machine mail. There is no owner field, so teams invent one with a category per person, and there are no notes or metrics. With Send As permission the thread does not say which teammate answered.
Shared inbox software
Past a few hundred emails a day, or past three people, the manual version of ownership and follow-through stops holding. Shared inbox tools add the owner field, the states, the notes, the typing indicator and the numbers. When you compare them, check five things.
- Assignment on arrival, by rule, by round robin or by load, with a visible owner on every thread.
- States that change when the client replies, so waiting on them becomes waiting on us without a person touching it.
- Internal notes and mentions on the thread, so the context stays next to the email instead of in a separate chat app.
- Templates and rules for the repetitive part, including machine mail.
- First response time as p50 and p90 per person and per inbox, and a count of overdue promises.
Where Sektra fits
We build Sektra, an AI shared inbox for client-facing teams, and it is built around the five jobs above. Triage is a priority ranking by what it costs to ignore a message, plus intent tags on each thread. Ownership is round robin or load-balanced assignment, with notes and mentions on the thread and a typing indicator when a teammate is already replying.
Follow-through has three parts. Reminders that cancel themselves when the client replies. A silence watch, which tells you the day a client has been quiet longer than the number of days you set. And a morning digest that lists who owes you a reply. Rules combine normal checks and AI checks in one rule to tag, assign, snooze or draft. The assistant drafts; a person sends.
The record is one history per contact across email, WhatsApp and chat. Review is an analytics page with first response time as p50 and p90 per teammate, per inbox and per client, so the weekly look takes one screen. The feature list is on /product, and the twelve rules in shared inbox best practices go deeper on the settings.
Start with the states and the owner rule this week, in whatever tool you have. Add the daily sweep, then the templates. Measure p50 and p90 from the first week, so you know what each later change did.
