The problems with a shared inbox

1. Two people answer the same message

The first and most visible failure. Both replies are polite, both are slightly different, and the customer now has two contradictory answers and a poor impression.

A mailbox cannot prevent this, because it has no concept of somebody having taken a message.

2. Read is not answered

Somebody opens a message, decides to deal with it later, and it is now marked read. It looks handled. Nobody will ever see it again unless they scroll.

This is the quiet failure and the expensive one – the customer who was ignored rarely writes again to say so.

3. Nobody knows what was promised

Internal context lives in chat, in a phone call, or in one person's head. When that person is unavailable, whoever picks up the thread starts from nothing.

4. Holidays are a cliff

Threads that were personally owned go quiet for two weeks. Reassignment means forwarding, and the history arrives as a quoted mess.

5. Nothing can be proven afterwards

How many requests came in last month? How fast did we answer? A mailbox can tell you how many messages it holds. It cannot tell you how many were cases, or how many were resolved.

6. Search that half works

Mailbox search finds words in messages. It does not find the number that appeared in an attached scan, and it does not know that these four threads were all the same case.

7. Rules that fight each other

Every attempt to fix the above with folders and rules adds a state nobody agreed on. Six months later the folder structure is a form of organisational archaeology.

What actually fixes it

Three things, and only three: an owner, a status and a deadline. Everything else a help desk offers is convenience on top of those. What that looks like in practice is in what is a help desk.

What you keep

The address. Customers keep writing to support@ and keep getting replies from support@. Nothing about their experience changes – which is the point.