What is shared inbox?

Why it matters

Shared inboxes are where most support functions begin, and knowing when to leave one is a real decision. They are excellent up to a few hundred conversations a month and become a reporting dead end beyond that, because they optimise for reading messages rather than for understanding demand.

What to know

• The ceiling is analytics. Shared inboxes tell you about messages, not about issue types or resolution.
• Assignment and internal notes solve ninety percent of the pain of a plain group address at a fraction of help desk complexity.
• Threading breaks when customers reply from a different address, and that failure is silent.
• Search across historical conversations is the underrated feature and the first thing you miss after outgrowing it.
• Graduating usually happens when someone asks a question the inbox cannot answer, such as which topic costs the most.

An example

Example: a three-person team runs support from a shared inbox happily. At about eight hundred conversations a month, leadership asks which product areas drive contact volume. The inbox cannot answer, and that question is what triggers the move to a help desk.

Common mistakes

• Staying on a shared inbox past the point where you need topic-level reporting
• Using a plain group address and calling it a shared inbox
• Not enforcing assignment, which reintroduces duplicate replies
• Assuming migration to a help desk means losing history

Questions