What a shared inbox is, how it differs from a shared mailbox or distribution list, what Gmail and Microsoft 365 already include, and when to move on.
Table of contents
- What is a shared inbox?
- Shared inbox, shared mailbox, collaborative inbox, distribution list: what is the difference?
- How does a shared inbox work?
- What Gmail and Microsoft 365 include at no extra cost, and where each stops
- What a dedicated shared inbox adds
- Do you need a shared inbox?
- Who needs a shared inbox?
- How to set up a shared inbox for your team
- How to choose a shared inbox
- Shared inbox tools and what they cost in 2026
- What AI changes about shared inboxes
- Frequently asked questions
The short version: a shared inbox is one email address, such as support@ or sales@, that a whole team reads and answers together, each from their own login. Gmail, Google Workspace and Microsoft 365 include basic versions at no extra cost on plans you already have. Teams move to a dedicated shared inbox when they need every email to show an owner and a status, plus internal notes and reporting.
What is a shared inbox?
A shared inbox is a single email address that several people work from at once, each signed in as themselves, with every conversation visible to the whole team. Dedicated tools add an owner and a status to each one.
Take a support@ address. A customer writes in about a wrong invoice. Everyone on the support team can see the email. One person takes it, so the rest know to leave it alone. She asks finance a question in a private note on the thread, replies to the customer, and marks it done. Nobody forwarded anything, nobody replied twice, and anyone who opens the thread later can see what happened.
That is the whole idea: one copy of each email, worked by a team, with the "who" and the "what state" on show.

Founder’s Take
A personal note from Nick, co-founder of Drag
Clicks are dying. AI is reshaping how teams use their inboxes, and everyone in this market knows it. But shared inboxes are still the traditional, and still mainstream, way teams collaborate on email: resolving support tickets, closing sales, keeping a group address from dropping things. The demand is still there, and for most teams a shared inbox is still a core requirement.
This page covers the key players in the market, and the ones I think will stay ahead as the industry changes.
I will always bet on our own product, Drag, because of the velocity we deploy at. But there are some great others out there. See for yourself.
Shared inbox, shared mailbox, collaborative inbox, distribution list: what is the difference?
The difference is whether the team works from one copy of each email and whether anyone can see who is handling it. The terms are often used interchangeably, but they are not the same thing.
| Term | What it is | One copy the team works from? | Shows who owns an email? |
|---|---|---|---|
| Distribution list | An address that forwards a copy to every member's own inbox | No | No |
| Shared mailbox (Microsoft 365) | A mailbox several people open from Outlook with their own logins | Yes | No |
| Collaborative inbox (Google Groups) | A Google Group with assignment and "resolved" switched on | Yes | Basic |
| Shared inbox (Google Workspace) | An admin-created mailbox that delegates open in Gmail | Yes | No, though it shows who sent each reply |
| Shared inbox (dedicated tool) | A team address with assignment, status, notes and reporting added | Yes | Yes |
"Shared inbox" is the umbrella term, which is why the built-in options and the dedicated tools all use it. If you are choosing between the first two, our distribution list vs shared mailbox guide goes deeper.
How does a shared inbox work?
A shared inbox works by keeping one copy of each email in a place the whole team can open, and, in a dedicated tool, adding the information a personal inbox lacks: an owner, a status and a private conversation alongside the thread.
- An email arrives at the team address and appears for everyone with access.
- Someone owns it. A person takes it, a manager assigns it, or a rule assigns it automatically.
- The team talks privately. Questions and context go in internal notes on the thread, not in forwards or CCs.
- One reply goes out from the team address. In a dedicated tool, a second person who starts replying is warned.
- The status changes to waiting or done, so the queue always shows what is left.
Drag · with Varley
The inbox your team and Varley work in together
Shared inbox and live chat for Gmail teams, with Varley, Drag’s AI, included from $18. Plus an MCP server your own AI tools can drive.
What Gmail and Microsoft 365 include at no extra cost, and where each stops
Both Google and Microsoft include ways to share an inbox on plans you already have, and for a small team with low volume they are often enough. Each gives shared access. Only Google Groups lets you assign a conversation and mark it complete, and none warns when two people reply, keeps internal notes, or reports on response times.
| Gmail delegation | Google Groups collaborative inbox | Google Workspace shared inbox | Microsoft 365 shared mailbox | |
|---|---|---|---|---|
| Who sets it up | The inbox owner | A group owner or manager | A Workspace administrator (the account owner can convert a delegated account) | A Microsoft 365 administrator |
| Where the team works | Gmail | The Groups interface | Gmail | Outlook |
| Stated limits | 10 delegates on a personal account, 1,000 on a work account, 40 at once with typical use | None on Google's help page | No member limit stated; Business Starter, Standard and Plus only | 25 users, 50 GB without a license |
| Shows who replied | The delegate's email address appears | Depends on the group's settings | "Sent by" field, unless hidden | Depends on the permission: send as, or send on behalf |
| Assign an email to a person | No | Basic | No | No |
| Warning when two people reply | No | No | No | No |
| Internal notes on the thread | No | No | No | No |
| Reporting on response times | No | No | No | No |
A few details that most guides miss:
- Google Workspace has a native shared inbox. An administrator creates it in the Admin console, from the Home page's Users section, with "Set up a shared email address". Each reply shows the shared address in From and the person in "Sent by", unless the administrator hides it. Existing delegated accounts can be converted. Google described it as "being released in phases" when we checked on November 11, 2026, and it was not yet in our own Business Starter console that day (Google Workspace help, last updated October 26, 2026). One cost to check: Google's page does not say whether the shared address needs its own paid user license, and administrators who have the feature report that it is a regular user account that does. Budget for one extra seat until Google says otherwise.
- A Google Groups collaborative inbox has basic assignment. Members with the right permission can take a conversation, assign it to someone else and mark it as complete, all in the Groups interface and not in Gmail (Google Groups help, checked November 11, 2026).
- Gmail delegation has real ceilings. Google's own figures are 10 delegates on a personal account, 1,000 on a work or school account, and 40 delegates in the account at the same time with typical use (Gmail help, checked November 11, 2026). It was designed for an assistant covering one person's mail.
- A Microsoft 365 shared mailbox supports a maximum of 25 users and holds 50 GB without its own license, though every person using it needs a licensed mailbox of their own (Microsoft Learn, last updated March 13, 2026).
- Sharing a password is the one route to avoid. It breaks two-step verification and leaves no record of who did what. Microsoft tells administrators to always block sign-in on the shared mailbox's own account.
If your volume is low and you only need several people to see the same mail, start with a built-in option. Setup steps for each Google route are in our Gmail shared inbox guide. If you administer Google Workspace, our Google Workspace shared mailbox guide covers licensing and the Admin console.
What a dedicated shared inbox adds
A dedicated shared inbox adds the workflow the built-in options leave out, on the same address your customers already use. These are the parts that matter, in the order teams usually feel their absence.
- Assignment. Every email has one named owner, set by hand or by a rule.
- Status. Open, waiting, done. "Read" is not the same as "handled".
- Collision detection. A warning, or a lock on the draft, when a teammate is already replying.
- Internal notes and @mentions. The team's conversation stays attached to the thread and hidden from the customer.
- Shared drafts and templates. Replies can be reviewed before they go, and common answers are written once.
- Automation rules. Predictable email is tagged, routed and assigned without anyone triaging it.
- Reporting. First response time, time to resolution, volume by tag and load per person.
- More channels. Some tools bring live chat and WhatsApp into the same queue as email.
- AI. Drafts, summaries and tags on every email, and in some tools an agent that resolves routine requests by itself.
Do you need a shared inbox?
You need a shared inbox once more than one person answers the same address and you can no longer tell, from the inbox itself, who is handling what. In practice these are the signs.
- Customers get two replies, or two different answers, to the same email.
- Emails go unanswered because everyone assumed someone else had it.
- You forward and CC to hand work over, and the thread is the only record.
- Nobody can say how long replies take, or who is overloaded.
- A new joiner cannot see the history of a conversation they are picking up.
- The free options feel too thin, and a help desk feels like too much.
And when you do not need one: if a single person answers the address, or the team gets a handful of emails a week, Gmail delegation or a shared mailbox is enough. Adding a tool will not fix a process that does not exist yet.
There are trade-offs too. A dedicated tool is a cost per person every month. It only works if the team uses the statuses, which is a habit to build. And it is one more place where access has to be granted and removed.
If the signs fit, the quickest test is a week on your real address: Drag has a 7-day trial with no card.
"Drag has completely changed the way our team uses our Email, eliminating double work, emails getting missed and creating LESS emails for everyone!"
Troy Parquer, Senior Transaction Coordinator, CBH Homes
Who needs a shared inbox?
Any team where several people answer the same address benefits from one, and support is only the most obvious case.
- Customer support: support@ and help@, where every email needs an owner and a reply time.
- Sales: sales@ and info@, where an unanswered inquiry is lost revenue.
- Finance and operations: billing@ and orders@, where invoices and supplier email need tracking to done.
- HR and recruiting: jobs@ and people@, where candidates and staff expect one consistent answer.
- Agencies: one address per client, with the whole account team able to see the thread.
How to set up a shared inbox for your team
To set up a shared inbox, keep the address you have, give each teammate access from their own login, and agree who owns new email. Nothing is migrated.
- Pick the address customers already write to. Keep it.
- Choose how to share it: a built-in option for basic access, or a dedicated tool when you need assignment and status.
- Add the team with their own logins. Never share the password.
- Agree on the statuses and who owns new email by default.
- Add rules for the routine work, such as sending invoices to billing.
- Review response times weekly and fix one thing each time.
Running one well is its own subject, covered in shared inbox management.
How to choose a shared inbox
Start with where your team already works (Gmail, Outlook or a mix), then test a tool on your real address with two teammates for a week. Our guide to the best shared inbox software compares twelve tools on price, AI and fit, so we do not repeat that here.
Shared inbox tools and what they cost in 2026
Dedicated shared inbox tools cost between $12 and $25 per user per month at entry level, and the main difference between them is where your team works. Prices below are each vendor's published entry price on annual billing, checked on November 11, 2026.
| Tool | Works with | Entry price | Free trial | Worth knowing |
|---|---|---|---|---|
| Gmail and Google Workspace | $12 per user | 7 days, no card | AI included from $18; no seat minimum; no free plan | |
| Gmail, Outlook and other providers | $14 per user | 30 days, no card | Entry plan is limited to 5 users | |
| Gmail and Outlook | $25 per user | 7 days, no card | Plans start at 2 seats | |
| Gmail | $25 per user | 7 days | Shared inboxes start on the Growth plan; the $19 Meli plan has none | |
| Gmail and Outlook, in its own app | $25 per seat | 14 days, no card | Entry plan is limited to 10 seats |
For a team of five on annual billing, the entry plans come to $60 a month with Drag, $70 with Missive, and $125 with Hiver, Gmelius or Front. Check the caps before you commit: Missive's entry plan stops at 5 users and Front's at 10.
Entry price is only the bottom of each ladder. This chart shows the full published range for the same five tools, in the same order, from the cheapest plan to the most expensive.
Prices also move. We keep dated captures of every vendor's pricing page going back to 2021 in our support tool pricing history, and worked cost scenarios for different team sizes in what a shared inbox really costs.
Drag is our product, so treat our view of it accordingly. The honest fit: Drag is a shared inbox for Gmail, built for teams that run on Gmail and Google Workspace. If your team is on Outlook, or mixes providers, Missive, Hiver or Front will suit you better. Drag has a 7-day trial with no card: start a trial. For the full comparison with more tools, see our guide to the best shared inbox software, and for the monthly bill at your team size, the shared inbox cost calculator.
What AI changes about shared inboxes
AI changes a shared inbox from a place where people organize email into a place where some routine email can be handled before a person opens it. Three things are now common: every email arrives tagged and summarized, a draft reply is waiting in the team's voice, and an agent can resolve simple requests end to end and hand the rest to a person with what it found.
The limits are worth knowing. An agent is only as good as the knowledge it can read, so the answers have to be written down somewhere. Anything that sends, refunds or edits should wait for a person's approval until you trust it. And ownership still matters: an email an agent could not resolve needs a named person, which is the job a shared inbox was built for.
Frequently asked questions
Can a shared inbox handle WhatsApp and live chat?
The built-in options in Gmail and Microsoft 365 handle email only. Dedicated tools vary: some add live chat and WhatsApp to the same queue, so one team answers every channel from one place. In Drag, live chat for your website is on every plan and a shared WhatsApp inbox is on the Pro plan.
Can you turn an existing email address into a shared inbox?
Yes, and you should, because customers already use it. In Google Workspace an administrator can convert an existing account, including a delegated one, into a shared inbox. Dedicated tools connect to the address you already have, so nothing is migrated and old email stays in place.
Is a shared inbox secure?
A shared inbox is more secure than the habit it replaces. Each person signs in with their own account, so there is no shared password, two-step verification keeps working, and access can be removed for one person without affecting the rest. The risk to manage is permissions: give each person only the inboxes they need.
Is a shared inbox the same as a help desk?
No. A help desk turns each email into a ticket in a separate system, often with a customer portal and phone support. A shared inbox keeps the conversation as email on your own address and adds ownership and status. Many small teams use a shared inbox until they need phone support or a large support operation.
Do customers see that an email came from a shared inbox?
Customers see the team address they wrote to. Whether they also see the individual depends on the setup: Google Workspace's shared inbox shows the person in a "Sent by" field unless that is hidden, and in Microsoft 365 it depends on whether the person has send as or send on behalf permission. Dedicated tools let you choose.
Co-founder
Building Drag for nearly ten years: shared inboxes, boards, and now the AI and agent layer, all on Gmail, plus HeyHelp for the personal inbox. Writes the honest versions of the comparisons.





