Why a shared inbox is more than a shared email account
In short
A shared email account shows everyone the same messages, but not who is taking care of them. A shared inbox adds exactly that: one owner per request, visible processing states and internal coordination, while your email addresses stay the same.
When several people look after one address, mistakes rarely come from carelessness. They happen because email clients are built for one person: they know “read” and “unread”, but not “I'll take this one”.
This guide shows where the classic shared mailbox reaches its limits and which ground rules make a shared inbox work.
What goes wrong in a classic shared mailbox
Four people open the same mailbox in the morning. Whoever clicks a message marks it as read for everyone, even if nobody replies. Colour flags and folders become a makeshift system that each person uses slightly differently.
- Read gets confused with done.
- Forwarding to colleagues creates copies that nobody brings back together.
- Replies sent from personal mailboxes are missing from the shared history.
- During holidays or sick leave, nobody knows what is still open.
The difference at a glance
| Aspect | Shared email account | Shared inbox |
|---|---|---|
| Access | One password for everyone | Personal sign-in with a role |
| Ownership | Unclear, agreed informally | One person per request, visible to all |
| Status | Read or unread | New, in progress, waiting, done |
| Internal coordination | Forwarding, copies, shouting across the room | Internal note on the request itself |
| Traceability | Who replied? Unclear | History per request with names |
| Someone leaves | Change the password for everyone | Remove one person's access |
Duplicate and forgotten replies
Two typical mistakes share one cause. In the first, two people answer the same complaint: one offers a credit, the other points to the terms and conditions. In the second, everyone assumes someone else is on it, and the customer waits for days.
More discipline does not fix either. What is missing is a visible answer to one question: who owns this request, and where does it stand?
Assignment: every request needs exactly one owner
Assignment does not mean only one person may see a request. It means exactly one person takes care of the next step. Everyone else can see that and stays out, or helps in a targeted way.
- Unassigned requests wait visibly in a shared queue.
- Whoever takes on a request assigns it to themselves before replying.
- Handovers are explicit, with a short note on where things stand.
- When someone is away, their open requests are deliberately reassigned.
Transparent processing states
A shared status replaces individual memory. A few clearly defined states are enough; what matters is that everyone uses them the same way.
| State | Meaning | Whose move is it? |
|---|---|---|
| New | Nobody has taken the request yet | The team |
| In progress | One person is on it | The assigned person |
| Waiting for customer | A question has been asked | The customer |
| Waiting internally | Information from a colleague is missing | The colleague who was asked |
| Done | The matter is closed | Nobody, until a new message arrives |
Working together internally, without copying the customer
Questions for accounting or the warehouse usually travel by forwarding in a shared mailbox. The answer arrives in another mailbox, the context gets lost, and in the worst case an internal remark reaches the customer through reply-all.
Internal notes attached to the request solve both: the discussion stays with the case, and it is clearly separated from the correspondence with the customer.
Keeping your existing email addresses
Nothing changes for your customers: they keep writing to the address they know. A shared inbox connects to the existing mailbox, for example through the standard protocols IMAP and SMTP or an interface offered by the email provider.
For replies to appear in the right conversation for the recipient, they have to carry the identifiers of the original message. Email clients group conversations using these header fields.[1]
If you send through a different service than before, it must be authorised for your domain. SPF and DKIM records take care of this; without them, replies easily end up in spam.[2][3]
In practice: a Monday morning in a small team
Fictional example
A small online shop for kitchenware answers requests via service@. Lena leads the team, Murat handles deliveries, Sophie handles returns. Many messages arrived over the weekend.
Before: all three open the mailbox. Murat reads a complaint, plans to answer later and forgets. Sophie answers the same customer in the afternoon, unaware that Lena had already promised a credit on the phone.
After: Lena distributes the new requests in the morning. Murat sees that the complaint is assigned to Sophie and only adds an internal note with the tracking number. Lena records the phone promise as a note too. Sophie replies once, completely, and marks the request as done.
Key points
- “Read” is not a processing state.
- Every request needs exactly one owner, visible to everyone.
- Internal coordination belongs on the request, not in forwarded emails.
- Your addresses stay; check SPF and DKIM when you change the sending service.
Related questions
Questions about this?
Talk to us – we answer them personally.
Sources
- RFC 5322 – Internet Message FormatRFC Editor (IETF)
- RFC 7208 – Sender Policy Framework (SPF)RFC Editor (IETF)
- RFC 6376 – DomainKeys Identified Mail (DKIM) SignaturesRFC Editor (IETF)