Managing one address between several people comes down to four decisions: give each person their own access rather than a shared password, name an owner per message rather than per time slot, mark what is finished explicitly instead of relying on the read status, and keep internal discussion on the conversation rather than in a chat app. Personal folders and colour codes, the thing most teams try first, fail for one reason: they depend on somebody remembering to keep them up to date.
What actually breaks
Opening a shared mailbox in the morning looks simple. You read the list, you reply. The difficulty is not the replying, it is that the list does not tell you what you need to know.
You cannot see intent. Some messages are read, some are not. Read tells you somebody opened it, and nothing about whether they are answering. A colleague who opened a message to check a reference before a call, then got stuck in that call, has left you a message that looks handled and is not. That single ambiguity produces both failure modes: two people answering because neither could tell, and nobody answering because both assumed.
The history is only half there. You handle a client together, and the exchange splits: part of it in one person’s sent items, part in another’s. When the client calls back, reconstructing what was agreed means asking two colleagues and searching two mailboxes. The client, meanwhile, explains everything again, which is the part they remember.
Responsibility dilutes with headcount. The more people watch an address, the more each one can reasonably assume somebody else is on it. This is not carelessness, it is arithmetic: at three people, any given message has two other plausible owners.
The four mistakes, and what each costs
Sharing the password. The security exposure is the obvious cost, and the organisational one is worse: when everyone signs in as the same account, you lose all trace of who did what. There is no accountability to build on, and no way to answer “who told the client 450?”. Microsoft’s own instruction for a shared mailbox is to block sign-in on that account and keep it blocked, precisely because it is not meant to be used that way. We covered the rest in sharing a mailbox without sharing the password.
Not deciding who handles what. If everyone does everything, the easy messages get answered and the difficult ones sink. Nobody chooses that: it is what happens when the decision is made 200 times a day under time pressure. The complex files resurface later as crises.
Discussing emails somewhere else. “Can you look at Mr Durand’s message?” in a chat app. The decision is now in a different application from the thing it decided, invisible to whoever picks the conversation up next month and to anyone who joins next year.
Building a folder tree. One folder per client seemed tidy. Then each person files by their own logic, and finding a message means guessing how a colleague thought. Filing becomes a second job, and the mailbox stops being searchable by anyone but its author.
Five decisions to make once
1. Individual access, never a shared account. Delegation, a shared mailbox with permissions, or a shared inbox. Any of the three beats a password in a group chat.
2. One owner per message, decided by topic. Quotes to one person, scheduling to another. By topic rather than by time slot, because a topic survives an absence and a handover, and a time slot breaks on every conversation that spans one.
3. Labels for state, not folders for storage. A small shared set: to process, waiting on someone, urgent. Three or four, identical for everyone. Add a fifth only the second time you wish you could filter on something you cannot. Labels also leave the message in place, which folders do not.
4. Internal notes on the conversation. “Client called, I quoted 450” belongs on the message. If your setup has no notes, the least bad substitute is a reply within the thread that the customer is not on.
5. An explicit done state. Archive what is finished so the inbox shows what remains. The measure that matters is not an empty inbox: it is that nothing is unowned. A conversation with an owner and an expected answer is under control even if it sits a day; an empty inbox where three threads were quietly filed is not.
The weekly routine
Ten minutes, once a week, which is enough for a small team.
Filter the last fourteen days and scan for messages with no reply after them. You are looking for the two or three that slipped, and they stand out.
Then look at what has been sitting too long with an owner. Ask why rather than chase: usually the person is waiting on information they cannot get, and the answer is to help or reassign, not to remind.
Count the follow-ups that begin “I already wrote to you about this”. It is the closest measure you have of what you missed entirely, and one a month in a small team is already a lot.
When good practice stops being enough
Three signals, and they are worth taking literally.
Duplicate replies more than once a month. Your current system has reached its limit, because the workarounds only work when nobody is busy.
You cannot say how many messages are pending. Not roughly: at all. That means the mailbox has stopped being a shared object and become several private impressions of one.
The team grew from two to three. The step from two to three is bigger than it looks: at two, coordination is one conversation, and at three it is three, held during the busiest part of the day.
What a shared inbox changes
The honest version: it does not make a team more disciplined. It removes the moments where discipline was the only thing preventing a mistake.
With Trupeo you connect the mailbox you already have, Gmail, Outlook, Microsoft 365 or any IMAP provider, keeping your address. Each person signs in with their own account, so the shared password stops circulating on day one. Each conversation carries one owner and an open or done status, internal notes live on the message, and when a colleague starts writing, everyone else sees it before they open anything. Decisions 1, 4 and 5 above become properties of the tool rather than habits the team has to maintain.
See the features or our pricing, and the complete shared inbox guide for the whole subject. If your team is at volume, the playbook for 300 emails a day goes further, and the ceilings your provider imposes are collected in shared mailbox limits.
Frequently asked questions
How do you manage a shared mailbox between several people?
Four decisions cover it: individual access for each person rather than a shared password, a named owner per message, an explicit done state separate from the read status, and internal notes attached to the conversation. Personal folders and colour codes, which most teams try first, depend on everyone remembering and fail on the busy days.
How should emails be divided between team members?
By topic rather than by time slot. Quotes to one person, scheduling to another: dividing by topic survives absences and conversations that stretch across the day, where a time slot breaks at every handover. Decide it once rather than message by message.
Should we share the mailbox password?
No. The provider can lock the account when it sees simultaneous sign-ins from several places, every departure forces a change for everyone, and nobody knows who answered what. Microsoft explicitly says to block direct sign-in on a shared mailbox account. The clean options are delegation, a shared mailbox with permissions, or a shared inbox.
How do you know who is handling which email?
The information has to live on the message rather than in people’s heads. A named owner, visible in the list without opening anything, is the only arrangement that holds. Read status does not answer the question: it only says somebody opened the message, possibly with no intention of replying.
How many people can manage the same mailbox?
Technically, a Microsoft 365 shared mailbox supports up to 25 users, with a warning about connection failures and duplicated messages beyond that. In practice, informal organisation breaks much earlier, at around three people answering the same address every day.
Sources:
- Create and manage labels in Gmail: labels as a flexible alternative to rigid folder structures, and the fact that a labelled message stays in place.
- Use a group as a Collaborative Inbox: assigning a conversation, marking it complete or duplicate, and filtering by assignment status.
- About shared mailboxes in Microsoft 365: the instruction to block sign-in on the shared mailbox account and keep it blocked, the system-generated password not intended for use, and the 25-user maximum with its connection failures or duplicated messages warning.
- Delegate and collaborate on email: what a delegate can and cannot do, and the fact that a delegate’s own address appears when they send.