Give every message exactly one owner. A shared inbox fails for the same reason a shared chore fails: when responsibility belongs to everybody it belongs to nobody, and each person assumes the message they read has been handled by someone else. Assign ownership on arrival, keep the categories few enough to remember, and get the automated noise out so what remains is genuinely for a human.
The characteristic failure of a shared inbox is not that messages are missed. It is that they are read and then not acted on, by three people in a row, each assuming one of the others has it.
Read receipts do not fix that. Colour-coded labels do not fix it. The only thing that reliably fixes it is a name attached to a message, visible to everyone, from the moment it arrives.
That is the whole fix, and it is why inboxes with assignment work and inboxes with folders do not.
Open a neglected shared inbox and a large part of it is notifications, receipts, delivery confirmations, calendar invitations, newsletters, and automated replies.
That volume is what makes the inbox feel unmanageable, and it is also what trains people to stop looking. When four out of five messages need nothing, the habit becomes scanning rather than reading, and scanning is how a real request goes past.
Getting the noise out is not tidying. It is what makes the remaining messages worth a person's attention.
The commitment that changes how customers experience a business is not resolving everything quickly. It is that nothing sits unacknowledged.
A one-line reply the same day — we have this, here is who is looking at it, here is when you will hear back — removes almost all of the frustration of waiting, and it costs a fraction of what the resolution costs.
It also has an internal effect. Once acknowledgement is the standard, the messages nobody wants to deal with stop being invisible, because somebody has already put their name on one.
Every shared inbox eventually accumulates twenty labels, at which point sorting becomes a decision and decisions get skipped.
Four or five categories is usually the whole taxonomy a small business needs: a new enquiry, an existing customer with a problem, something about money, something for a specific person, and everything else. If a category has not been used in a month, it is not a category.
One name, visible to everyone, before anything else happens. This is the fix. The rest of the list makes it easier to sustain.
Notifications, receipts, delivery updates and newsletters go somewhere else. What is left in the inbox should be things a person wrote.
New enquiry, existing customer, money, for a named person, other. If you cannot say the list from memory it is too long to be used consistently.
One line: we have it, this is who is on it, this is when you will hear back. Separate acknowledgement from resolution and the inbox stops feeling like a backlog.
Decide what counts as urgent — a complaint, a payment failure, a booking for tomorrow — and make sure it reaches a person directly rather than waiting to be found.
Twice a day beats continuously. Continuous monitoring means the inbox is always slightly open and never actually clear.
Not to begin with. Assignment and a short set of categories are the substance, and both can be done in the inbox you already have. A helpdesk becomes worth its setup when volume makes tracking by hand unreliable, not before.
The same working day. Speed of acknowledgement is what customers actually notice; speed of resolution matters far less once they know the message landed with a named person.
Those are the ones that prove whether the system is real. Assign them by rota rather than by volunteer, because a queue that depends on someone volunteering is a queue with a permanent bottom nobody reaches.
Sorting, categorising and acknowledging, yes — those are reversible and visible. Anything that commits the business, such as a refund, a promise about a date, or a reply to a complaint, should be drafted for a person to approve rather than sent.
We're onboarding our first companies by hand. A person reads what you write and answers within a day.