A shared inbox is one email address that more than one person can read and reply from. Write to support@ and you
reach a team; any of them can answer, and the reply comes back from support@ rather than from whoever typed it.
The term covers two things that are easy to mix up. The plain version is an address several people share the password for. The tool version is software that puts the same address in front of the team with the parts a mailbox does not have: who is handling a thread, what state it is in, and what the customer has already been told.
What a shared inbox is
Everyone with access sees the same messages, and whoever answers, the customer sees one correspondent instead of four.
That is what separates the address from a group. A shared mailbox lets a group of people monitor and send from a public alias, and when one of them replies, the message appears to be from the alias rather than from that person, according to Microsoft’s documentation for shared mailboxes in Outlook.
The term is not a synonym for any group address a team happens to run. Four arrangements get called one:
| Arrangement | Has a mailbox | Sends as the address | Shows who is handling a thread | Keeps one record |
|---|---|---|---|---|
| Distribution list | No | Usually not | No | No |
| Shared mailbox | Yes | Yes, with permission | No | Depends on setup |
| Shared Gmail login | Yes | Yes | No | Yes |
| Shared inbox | Yes | Yes | Yes | Yes |
What a shared inbox is not
It is not just any address several people receive. A distribution list delivers a copy of each message to every member’s own mailbox and has no mailbox of its own, so the reply comes from whoever answered and there is no single place to read the history. Shared mailbox vs distribution list covers that choice in full.
It is not a shared Gmail login. The free version is one account and one password for the whole team. Whoever opens the mailbox first marks a message read for everyone, so unread stops meaning “nobody has this”.
It is not the same thing as a shared mailbox. A shared mailbox is one mailbox several people open, which is the storage half of a shared inbox. It still cannot show that someone has started a reply.
It is not a help desk. More on that below, because it is the boundary readers ask about most.
The three parts
| Part | What it means | What a shared mailbox does on its own |
|---|---|---|
| Shared access | Every member sees every thread, rather than only the ones addressed to them | Yes |
| Shared identity | Replies leave from the team address | Yes, with send permission |
| Shared ownership | A thread shows which one person is handling it, and what state it is in | No |
The third part is the one that makes the difference in daily use. Access and identity are what get a team to one address. Ownership is what stops two people writing the same reply, and a mailbox has no concept of a thread being claimed.
Shared mailbox vs shared inbox
These are not two products to choose between. A shared mailbox is the mailbox: one address, one history, several people with access. A shared inbox is what turns that mailbox into a queue the team can see.
The words carry the confusion. An inbox is the list of messages you work through; a mailbox is the store they sit in.
There is one practical difference worth knowing. With a plain shared mailbox on Microsoft 365, a reply can land in the sender’s own Sent Items folder rather than the mailbox, unless the mailbox is configured to keep a copy, as Microsoft’s Exchange troubleshooting note describes.
Shared inbox vs help desk
A help desk takes requests and turns them into a queue. Tickets, priorities, service levels and reporting are part of that model, and none of them exist in a mailbox.
A shared inbox keeps the conversation in email and adds the parts a small team needs: one owner per thread, a small set of states, and a view of what is open. The split is the data model: a thread with an owner, or a ticket with a workflow.
What a shared inbox changes for a team
The first thing a shared inbox changes is that “who is answering today” stops being a rota. The answer lives in the tool, on the thread, visible to everyone with access.
The second change is what the reader stops doing. On a shared Gmail login or a list, one person becomes the router: they read the incoming mail, work out who knows the answer, and forward it. A shared inbox removes that role because the thread is already visible to the people who can answer it.
The awkward part is reply all. When a customer writes to one person and copies the team, four people have an opinion about who owns the reply. CC and BCC covers who sees what when it goes out.
Chirp and the shared inbox
Chirp is a shared inbox for small software teams that track their work in Linear. It connects to your mailbox, which stays the record, and puts the queue in front of the team.
Press i in a thread to link it to a Linear issue, create one, or search for the one that already exists. When every
linked issue is Done or Canceled, the thread comes back with a reply drafted for you that names the issue.
Every other action has a key too: j and k to move, e to archive, s, a, t and b to snooze, assign, tag
and block. Each inbox carries its own access list, and roles are Admin, Agent and Viewer. Chirp costs $9 per user per
month.
FAQ
What is a shared inbox in simple terms? One email address that several people can read and reply from, so a message sent to the team reaches the team. It sits beside your personal mailbox rather than replacing it.
What is the difference between a shared inbox and a shared mailbox? A shared mailbox is the mailbox itself: one address, one history, several people with access. A shared inbox adds the layer on top that shows who is handling each thread and where it stands.
What is the difference between a shared inbox and a distribution list? A distribution list sends a copy to each member and has no mailbox of its own, so replies leave from the individual and there is no shared history.
Is a shared inbox the same as a help desk? No. It keeps the conversation in email and adds ownership, where a help desk turns requests into tickets with priorities, service levels and reporting.
What are the downsides of a shared inbox? Visibility cuts both ways. Everyone can see every thread, including the mistake someone made in a reply, and a customer’s message may be read by a colleague they never wrote to.
Can a shared inbox run on Gmail or Outlook? Yes. A shared inbox is an address on a mail server, so it works with Gmail, Google Workspace, IMAP and most hosted mailboxes.
Next step
If your team already shares an address, what a collaborative inbox is covers the Google Groups way of building one and the four ways it breaks. If you are still choosing what the address should be, shared mailbox vs distribution list is the decision that comes first.
