An email rarely vanishes. It gets marked read by someone who was not answering, forwarded out of the shared history, filed in a personal folder, answered from an individual address so the reply lands somewhere else, or bounced back because the mailbox hit its storage limit. Every one of these fails silently: nothing errors, nobody is told, and you find out when the customer follows up annoyed, or never. The two checks at the end catch most of them in ten minutes a week.
Losing an email is worse than answering it twice
A duplicate reply is embarrassing and self-announcing. Somebody notices within the hour, usually the customer, and the team fixes its process that afternoon.
A message nobody answered produces no signal at all. The customer waits, decides you are not interested, and goes elsewhere. You never learn it happened, so nothing gets fixed, and the same mechanism keeps working quietly in the background. Teams routinely count their duplicates and have no idea what their silence rate is.
That asymmetry is why this is worth ten minutes a week.
The seven ways it happens
1. Someone read it without answering it. The commonest by far. A colleague opens the message to check a reference before a call, gets pulled into that call, and never comes back. The message now shows as read for everyone, which every other person reads as handled. Read status was designed for one person managing their own mail: it carries no information about intent, and in a shared mailbox it actively misleads.
2. It was forwarded, and the thread left with it. Someone forwards the message to a colleague’s personal address so they can deal with it. The reply now goes out from that personal mailbox, the customer’s next message lands there, and the shared address never sees the rest of the conversation. The original still sits in the shared mailbox looking unanswered, or worse, looking handled.
3. It went into a personal subfolder. The “Marie” and “Thomas” folder pattern. It removes the message from the inbox, so it stops being visible to everyone else, and it is filed under a name rather than a status. When Marie is off sick, her open conversations are invisible: not lost exactly, but unreachable by anyone who would have covered.
4. The reply went out from an individual address. This one is a setting, not a habit. With Gmail delegation, when a delegate sends, their own email address appears. The customer replies to that address, and the conversation permanently leaves the shared history. Nothing looks wrong from inside the mailbox, which is what makes it durable.
5. It landed in spam or was deleted by someone else. In a Microsoft 365 shared mailbox you cannot prevent users from deleting messages, and there is no team-wide undo. In a Microsoft 365 group, someone who deleted their personal copy has not touched the group’s, and the reverse also holds, so two colleagues can genuinely disagree about whether a message still exists.
6. It arrived while everyone assumed someone else was on duty. Fridays after five, the week between Christmas and New Year, the morning of the trade show. Not a mechanism so much as a gap in coverage, and the one your customers remember, because those are the moments they wrote to you about something urgent.
7. It never arrived at all. The one nobody suspects. A Microsoft 365 shared mailbox stores 50 GB without a licence, and 100 GB with an Exchange Online Plan 2 licence. When it fills, it keeps receiving for a while, then stops sending, then starts bouncing incoming mail back to the sender. Your customer got a delivery failure, you got nothing, and there is no trace on your side to find. A support address running for a few years with attachments reaches that ceiling more easily than teams expect.
How to tell it is happening to you
You cannot count what you never saw, so you have to look for it sideways. Four signs, in increasing order of how bad it already is.
Someone asks “did anyone answer this?” out loud, more than once a week. That is the team detecting the gap manually, at the cost of everyone’s attention.
A customer follows up with “I already wrote to you about this”. Count those. It is the closest thing to a direct measurement you will get, and one a month in a small team is already a lot.
You find a conversation in your archive with no reply, dated weeks ago. Assume it is not the only one.
Your storage is above 80% of its ceiling. Check it before you need to, because the symptom arrives on the customer’s side first.
The two checks that catch most of it
The weekly sweep. Once a week, filter the shared mailbox on the last fourteen days and read only the subject lines of messages with no reply after them. Ten minutes for a small team. You are not looking for perfection: you are looking for the two or three that slipped, and they will be obvious.
Check the From line, once. Send yourself a test from each person’s account and read what address it went out as. This takes five minutes, once, and it catches failure 4 permanently. Most teams discover at least one person whose replies have been leaving under their own name for months.
Add a third if your mailbox is old: look at the storage figure. Microsoft’s ceilings are documented, but nobody watches them until the bounces start.
What actually prevents it
Every failure above shares one property: the state of a message lives in someone’s head rather than on the message. Read status is the wrong proxy, folders are the wrong container, and chat is the wrong place for the context.
The fix is to make the state explicit and attached. One owner per conversation, visible in the list. A closed state that is separate from read, so an inbox tells you what remains rather than what has been glanced at. Internal notes on the conversation itself. Replies leaving from the shared address whoever wrote them.
With Trupeo you connect the mailbox you already have, Gmail, Outlook, Microsoft 365 or any IMAP provider, and those four become properties of the tool rather than promises the team makes. The unassigned view is the part that matters here: it is a list of what nobody has claimed, which is precisely the list you cannot build in an ordinary mailbox.
See the features and our pricing. The mirror-image failure is covered in how to avoid duplicate replies, the rules in shared inbox etiquette, and the documented ceilings in shared mailbox limits.
Frequently asked questions
Why do emails get lost in a shared mailbox?
Because a message’s state lives in people’s heads rather than on the message. Someone reads without answering and it looks handled; a forward takes the thread out of the shared history; a personal folder hides it from everyone else; a reply sent from an individual address moves the conversation elsewhere. All of these fail silently, with no error and no notification.
How do I know if we have missed a customer email?
Count the follow-ups that begin “I already wrote to you about this”, which is the closest thing to a direct measurement available. Then run a weekly sweep: filter the last fourteen days and scan for messages with no reply after them. In a small team that takes about ten minutes.
Does marking an email as read stop it being missed?
No, it makes it more likely. Read only means somebody opened it, so a message opened and abandoned looks handled to everyone else and gets no reply at all. Read and unread were built for one person managing their own mail and carry nothing about intent.
Can a shared mailbox stop receiving without us noticing?
Yes. A Microsoft 365 shared mailbox holds 50 GB without a licence and 100 GB with Exchange Online Plan 2. Once full, it keeps receiving briefly, then stops sending, then bounces incoming mail back to senders. The failure is visible to your correspondents and invisible to you.
What is the fastest fix?
Check which address your replies actually leave from, for each person, once. It takes five minutes and it permanently closes the failure where a customer’s follow-up lands in one person’s private mailbox. With Gmail delegation in particular, a delegate’s own address appears when they send.
Sources:
- About shared mailboxes in Microsoft 365: the 50 GB and 100 GB storage limits, the Exchange Online Plan 2 requirement, the behaviour when the mailbox reaches its limit, and the impossibility of preventing users from deleting messages.
- Compare types of groups in Microsoft 365: the independent deletion behaviour between a subscriber’s personal inbox and the group mailbox.
- Delegate and collaborate on email: the fact that a delegate’s own email address appears when they send.
- Exchange Online limits: the storage quotas that apply to shared, user and group mailboxes by plan.