A collaborative inbox is one email address that several people can read and reply from. The point is that a customer
writing to support@ reaches a team rather than an individual, and any of them can answer.
They break in a consistent way. The mail arrives, everyone can see it, and nobody is sure who is answering.
What it actually does
Three things separate a collaborative inbox from a normal mailbox:
- Shared visibility. Every member sees the whole queue, not just what was sent to them.
- Shared identity. Replies go out from the group address, so the customer sees one correspondent rather than four.
- Some form of ownership. A way to mark that a thread is being handled, by whom.
The third is the one teams skip, and it is the one that causes the problems below.
The four ways teams build one
| Approach | Sends as the shared address | Where the conversation lives | Can assign | Identity per person |
|---|---|---|---|---|
| Google Group | Configurable, often the member’s own address | Each member’s own mailbox | In the web view, if the group is a Collaborative Inbox | Weak |
| Shared mailbox (Outlook and Microsoft 365) | Yes, if the member has send-as permission | One mailbox, shared | No, unless you add something | No |
| Gmail delegation or an alias | Partly. Delegates read, sending as the address needs setup | The owner’s mailbox | No | No |
| A shared inbox tool | Yes, per inbox | The tool, with the mailbox as the record | Yes | Yes, per inbox |
The first three are free or already paid for, which is why most small teams start there.
Where they break
Two people answer the same email. Without a visible claim, two people reading the same message at the same time both start replying. The customer gets two answers, sometimes contradicting each other.
Nobody owns the reply. The mirror image of the first problem. Everyone can see the message, so nobody assumes it is theirs. It sits until the customer chases.
The history is scattered. In a Google Group or a delegated mailbox, each member keeps their own copy of what they sent. Ask “what did we tell this customer in March” and there is no single place to look.
Handover depends on memory. Someone goes on holiday and the threads they were holding are not visible as work in progress. The person covering finds out when the customer writes again.
All four are the same underlying gap: sharing the mailbox is not the same as sharing the work.
Google Groups as a collaborative inbox
The free option most teams try first, and a reasonable starting point. One address, delivers to everyone, and Google Groups includes a Collaborative Inbox group type that adds assignment and resolution to the web view.
Two limits matter for support:
- Where the mail lives. A group delivers copies. The conversation record ends up spread across members’ own mailboxes, so the group is a distribution mechanism rather than a shared record.
- Who the customer sees. Depending on how the group is configured, replies can come from the individual’s address rather than the group address. That is fine internally and confusing for a customer who wrote to one address and hears back from four.
The test is simple. Reply to a message your team received through the group, from a phone, while someone else is looking at the same thread. If neither of you can see that the other is answering, the group is not yet a collaborative inbox.
What to check before you pick
- Can every member see every thread, and see who is handling it? Shared visibility without visible ownership solves nothing.
- Do replies go from the shared address? Check this from a phone, not just from the desktop client.
- Is there one record? After a month, can you find what you told a specific customer without asking the person who sent it?
- What happens when someone leaves? Their mailbox should not be the archive.
- Can access be limited per address?
billing@andsecurity@usually should not be readable by everyone who coverssupport@. - What does a customer see? One correspondent or a rotating cast.
Setting one up
The order matters, because each step depends on the one before it:
- Decide the address, and who is allowed to write from it.
- Grant access, and decide which teams see which inbox.
- Write down the ownership rule, even if it is one line.
- Agree the states a thread can be in: open, waiting on us, waiting on the customer, done.
- Add saved views for the ones people use daily. Unassigned, mine, waiting on the customer.
- Only then add automation, once the team follows the manual version.
Most teams skip steps 3 and 4 and then blame the tool.
What to measure
Four numbers a small team can collect without extra tooling:
- How many threads are open right now, and how long the oldest has been open.
- How many have no owner.
- How long between a customer writing and a human replying for the first time.
- How often two people reply to the same thread. Ask the team. Twice in a month is a process problem.
Everything else can wait until the team is bigger than the tooling is.
FAQ
What is a collaborative inbox? An address several people share, where each of them can read, reply and see who is handling what.
Is a Google Group a collaborative inbox? It can be. Groups have a Collaborative Inbox type with assignment, but the mail is still delivered to members’ individual mailboxes rather than one shared record.
What is the difference between a shared mailbox and a collaborative inbox? A shared mailbox is one mailbox several people open. A collaborative inbox adds the workflow on top: ownership, status, and a single history.
Can a collaborative inbox send from the shared address? It should. If replies leave from personal addresses, the customer is dealing with several people rather than one address, which is usually the reason the team set the inbox up.
How many people can share one inbox? There is no technical limit worth worrying about at small-team scale. The practical limit is the point where nobody can tell who is doing what.
Next step
If you are choosing between the free options, shared mailbox vs distribution list covers which one fits which job. And if the inbox is shared, CC and BCC matter more than they do in a personal mailbox.
