A shared inbox is a single mailbox that several people work in together. Every conversation in it carries an owner and a state, so the team can see what has arrived and who has it.
The distinguishing feature is ownership. Several people have been able to open the same mailbox for decades; what a shared inbox adds is a per-conversation assignee and a per-conversation state, which is what turns a pile of messages into a queue.
What it replaces
| Approach | Problem it leaves |
|---|---|
| Personal mailboxes | Requests are invisible to everyone else and stall when their owner is away |
| Distribution list | Several unowned copies; nobody can see who replied, or whether anybody did |
| Delegated mailbox access | Shared visibility with no assignment or state, so two people answer or nobody does |
| Forwarding chains | The history fragments across mailboxes and the original sender is lost |
Common features
- Assignment, so one named person owns each conversation
- States such as open, snoozed and completed, so the queue reflects what is outstanding
- Internal notes, so the team can discuss a reply without the client seeing it
- A needs-response view, computed from whether the client has spoken more recently than the team has
- Per-person read state, so one colleague opening a message does not mark it read for everybody
How mail gets in
Most shared inboxes are fed by forwarding: the team's existing support address is pointed at an address the system provides, and everything sent there appears in the queue. Replies go out under the company name, and threading is maintained by a token in the reply address so the client's answer returns to the same conversation.
Forwarding is preferred over connecting to the mailbox directly because it needs no password or OAuth grant, and it is reversible in one step at the provider.
Why service firms use one
For an agency or consultancy, the reason is rarely response time. It is that client requests represent real, chargeable hours, and hours handled out of a personal mailbox are hours nobody can measure, staff for, or invoice.
Putting the queue where the team's retainer and billable hours are already tracked closes that gap: the request, the time it took, and the invoice line it becomes are the same record rather than three reconstructions of one.
