Team Mailboxes Without the Confusion: Who Owns Which Email
When a whole team can see the accounts@ or support@ mailbox, it's easy for two people to answer the same email — or for nobody to answer it at all. Here is the simple routine we use so every email has one owner and nothing gets lost.
Most businesses have at least one: support@, accounts@, bookings@, info@. A mailbox the whole team can see, so customers always have somewhere to write.
It works well — until it doesn't. A customer gets two slightly different answers from two different people. Or an email sits for three days because everyone assumed someone else had it. Nobody did anything wrong. The mailbox just had no way of showing who owned what.
This is one of the first things we look at in customer operations, and it is one of the easiest to fix.
The short version
A team mailbox needs the same thing as any shared piece of work: one owner per email, a few clear states, and a regular rhythm for checking it. Once ownership is visible, the double replies and the forgotten emails both disappear.
First, a word on how the mailbox is set up
By "team mailbox" I mean what Microsoft 365 calls a shared mailbox and Google Workspace calls a collaborative inbox. Done properly, each person opens it with their own sign-in — there is no shared password to pass around. That matters: it means you can see who did what, and when someone moves on, you simply remove their access. If your team mailbox is still opened with one shared login, that is the first thing worth changing.
The routine we use
1. Every email gets one owner
The moment someone starts working on an email, they claim it — with an assignment, a category, or a coloured flag with their name, whichever your platform supports. The rule is simple: if it has your name on it, it's yours until it's done. If it doesn't, it's nobody's yet.
2. A few clear states
We keep it to four, so everyone can see at a glance where things stand.
| State | What it means | Who acts next |
|---|---|---|
| New | Arrived, not yet claimed | Whoever is on mailbox duty |
| Claimed | Someone owns it and is working on it | The owner |
| Waiting | Answered, waiting on the customer or another team | The owner, when the reply comes in |
| Done | Resolved and filed | Nobody — it's finished |
3. Someone is on mailbox duty
Each day (or each shift), one person is responsible for sweeping New at agreed times — first thing, after lunch, and before close. They don't have to answer everything themselves. Their job is to make sure every new email is claimed by someone, so nothing sits unowned.
4. Agree what "quick enough" means
Not every email needs the same speed. A short, written agreement — for example, urgent requests the same morning, general questions within a working day — tells the team where to focus first and gives customers a consistent experience.
5. Keep the story in one place
When an email needs a colleague's input, the conversation stays with the email: an internal note, a forward that is filed back to the thread, or a comment in the ticketing system if you use one. Side conversations in chat are fine, but the outcome gets written back to the email. Then anyone can pick it up without having to ask.
6. Reuse the good answers
The same questions come in again and again. When someone writes a clear, friendly answer, we save it as a template. The next reply is faster, and every customer gets the same accurate information — written in a human voice, not a robotic one.
What good looks like
A customer writes once and gets one clear answer. The team can see at a glance what is new, what is in progress, and what is waiting. When someone is on leave, their claimed emails are easy to spot and hand over. And at the end of the day, New is empty.
If you only do one thing
Start claiming emails. Even before you add states or rotas, a simple "this one's mine" — a category or flag with a name on it — removes most of the double replies and most of the forgotten emails.
Final thoughts
A team mailbox is often the first place a customer meets your business. Keeping it clear isn't about new software; it's about making ownership visible. When everyone can see who has what, the team works calmly — and customers notice.
In your team mailbox right now, could you say who owns each unanswered email?
CustomerOps+ · Team mailboxes
This is part of what our CustomerOps+ team does every day
Structured support across ticketing systems, shared mailboxes, and customer relationship management — keeping your customers happy and your team focused.