Short answer: Give every email one owner, agree in writing how fast and in what tone the team replies, discuss messages in internal notes instead of forwarding them, and give each person their own login instead of a shared password. Then let rules do the sorting, keep reply templates in one shared place, and look at the numbers once a week. A shared inbox only stays calm when everyone can see who is handling what.
This guide covers what a shared inbox is, how to set one up in Microsoft 365, Google Workspace or a dedicated tool, the ten practices that keep it under control, and how a shared inbox helps people talk across teams and levels without losing track of decisions.
What is a shared inbox?
A shared inbox is one email address, such as support@ or sales@, that several people read and answer from their own accounts. Everyone sees the same conversations, so a customer gets one reply instead of three, and nothing sits unread in one person's inbox while they are on holiday.
There are three common ways to run one, and they differ more than the names suggest:
| Setup | Where it lives | Good for | Watch out for |
|---|---|---|---|
| Shared mailbox | Microsoft 365 (Outlook) | Small internal teams already on Microsoft 365 | No built-in assignment; Microsoft says it supports a maximum of 25 users |
| Collaborative inbox | Google Groups (Google Workspace) | Gmail teams that want to assign and close conversations | Assignment and status tools must be turned on by the group owner |
| Mail delegation | Gmail | One person handing their inbox to an assistant | Delegates can read, send and delete, but there is no assignment or status |
| Shared inbox app | A dedicated tool | Teams that need assignment, notes, templates and reporting | A per-user monthly cost |
A shared inbox is not the same thing as a unified inbox, which pulls one person's several accounts into one view. Our comparison of a unified inbox vs a shared inbox explains the difference.
Which teams need a shared inbox?
Any team that answers mail sent to a role rather than a person. The most common shared addresses:
| Address | Team | What goes there |
|---|---|---|
| support@ | Customer support | Product questions, bug reports, refunds |
| sales@ | Sales | Inbound leads from forms and direct outreach |
| accounts@ or billing@ | Finance | Invoices, vendor questions, payment confirmations |
| orders@ | Operations | Order intake, shipping confirmations, supplier issues |
| hiring@ or jobs@ | Recruiting | Applications and candidate scheduling |
| hr@ or it@ | Internal teams | Policy questions and technical requests from staff |
| exec@ | Executive support | An assistant or chief of staff handling a leader's mail |
How to set up a shared inbox
- Pick the setup. Use the table above. If you need to assign emails, track status or measure reply times, a plain shared mailbox will feel thin quickly; a collaborative inbox or a shared inbox app does that out of the box.
- Create the address and give people access. In Microsoft 365, an admin creates the shared mailbox and adds members; it needs no license of its own up to 50 GB, but each member needs a licensed Exchange Online mailbox. In Google Workspace, create a group, then turn on the collaborative inbox features so members can use Take, Assign and Mark as complete.
- Block direct sign-in. Microsoft says a shared mailbox is not meant for direct sign-in and that you should keep sign-in to its account blocked. The same idea applies everywhere: people work from their own accounts, never a shared password.
- Set permissions by role. Decide who can reply, who can only read, and who can change rules. Remove access the day someone leaves the team.
- Add rules, labels and templates. Route mail by sender or subject, agree on a short set of labels, and write templates for the replies you send most.
- Connect the tools you already use. If your inbox app links to your CRM or help desk, set that up now so people don't copy and paste customer history.
- Review after two weeks. Look at who is answering what and how long replies take, then adjust rules and roles.
10 shared inbox best practices
1. Give every email one owner
When everyone can see a message, everyone assumes someone else has it. Assign each conversation to one named person as soon as it arrives, either by hand or with a rule. In a Google collaborative inbox that is Take or Assign; in a shared inbox app it is usually an assignee field. The owner can ask others for help, but the reply is theirs.
2. Define roles and who covers when
Split the work instead of letting everyone handle everything: one person triages new mail, another handles follow-ups, a third takes escalations. For small teams, a simple rota works well: one or two people watch the inbox for a shift and hand over with a short note.
3. Write down your reply rules
Agree how fast the team replies (for example, within one business day), which messages count as urgent, who gets escalations and what tone you use. Keep it to one page. New teammates learn the rules in ten minutes instead of guessing for a month.
4. Use labels and statuses, not just folders
A folder can hold an email in only one place, while labels or tags let one message be both "Billing" and "Urgent". Keep the list short and shared: a few topic labels plus a status for each conversation, such as open, waiting on customer and done. Personal labels belong in personal inboxes.
5. Comment inside the thread instead of forwarding
Forwarding a message to a colleague, or asking about it in a chat app, splits the context in two. Internal notes and @mentions inside the conversation keep the discussion next to the email, leave a record for whoever picks it up next, and remove the risk of an internal remark going to the customer by mistake.
6. Keep reply templates in one shared place
Write templates for the questions you answer every week, and store them where the whole team can use and improve them. Answers stay consistent and new hires sound like the rest of the team from day one. Personalize the first line every time.
7. Let rules do the sorting
Route billing mail to finance, tag messages by keyword, and auto-assign by sender or subject. Start with a handful of rules you can explain in a sentence each, and review them monthly; a rule nobody remembers creating is how mail goes missing.
8. Close the loop: snooze, archive, mark done
Snooze messages that can't move until later so they come back on time, and archive or mark done everything that is finished. The view the team works from should show only open work. In Outlook, note that Focused Inbox doesn't work with shared mailboxes, so sorting has to come from rules or folders.
9. Protect access
No shared passwords, ever. Give each person individual access with the permissions their role needs, turn on two-step verification, and remove people promptly when they leave. Individual access also tells you who replied to what. For managers who only need to watch, read-only access avoids notifications they don't need.
10. Review the numbers every week
Spend 20 minutes a week on three things: how long first replies take, how many conversations are still unanswered, and whether the load is spread fairly. If one person carries most of the inbox, or the same question keeps coming in, change a rule, a template or the rota.
Shared inbox mistakes to avoid
- Sharing one login. You lose the record of who did what, and you can't remove one person without locking out everyone.
- Leaving conversations unassigned. "Someone will get it" is how a customer waits four days.
- Moving mail into personal folders. Once it leaves the shared view, nobody else can see it was handled.
- Replying all to discuss internally. Use notes; one slip sends your internal discussion to the customer.
- Letting a Microsoft 365 shared mailbox fill up. Microsoft warns that a full mailbox first stops sending and later stops receiving, and senders get a non-delivery report.
Using a shared inbox for cross-team (diagonal) communication
Diagonal communication is a direct conversation between people in different departments and at different levels, such as a support agent asking a finance manager about a billing problem without going through their own supervisor. It sits between vertical communication (up and down the reporting line) and horizontal communication (between peers in the same team).
Done well it speeds up decisions, because the question goes straight to the person who can answer it. Done badly it leaves managers out of the loop and scatters decisions across private threads. A shared inbox helps because the conversation stays visible: the support agent can mention the product manager inside the thread, the decision is written down where the team can see it, and nobody has to forward messages up and down the chain.
Some everyday examples:
- A support agent notices the same technical complaint repeating and brings the product manager into the conversation directly.
- A marketer who needs a quick budget answer assigns the email to the finance controller instead of waiting for a weekly meeting.
- An operations coordinator spots a staffing gap and settles it with HR in the same thread.
Set a few guardrails so it doesn't turn into noise: agree when cross-team outreach is welcome and when it isn't (sensitive HR matters, for instance), keep permissions tight on confidential queues, and post a one-line summary of the outcome when a thread is resolved so managers stay informed without being copied on everything.
Choosing a shared inbox tool
If Outlook shared mailboxes or Google Groups cover what you need, start there; they come with the accounts you already pay for. Teams that outgrow them usually want assignment, internal notes, templates and reporting in one place. Our comparison of the best shared inbox tools covers the main options and prices.
Disclosure: we make Shared Inbox by Canary. It works with Gmail, Microsoft 365 and IMAP addresses, and lets you assign emails to teammates, chat and @mention inside conversations, share templates, track ticket status and auto-tag messages by issue type. Plans start at $10 per user per month, with a 14-day free trial that needs no credit card. See shared-inbox.ai for current plans.
For your own mail, Canary Mail, our email app for Mac, iPhone, iPad, Windows and Android, keeps Gmail, Outlook, iCloud, Yahoo, Exchange and IMAP accounts in one app, with AI inbox sorting on the free plan.
Frequently asked questions
What is the best way to manage a shared inbox?
Give every conversation one owner, agree on reply times and tone in writing, discuss messages in internal notes rather than by forwarding, and give everyone individual access. Then use rules and shared templates for the routine work and review reply times weekly.
How do you stop duplicate replies in a shared inbox?
Assign each email before anyone answers it, and only the owner replies. Tools that show who is viewing or drafting a reply help too. In a Google collaborative inbox, Take marks a conversation as yours.
What are the disadvantages of a shared mailbox?
A Microsoft 365 shared mailbox has no built-in assignment or status tracking, you can't stop members from deleting messages, email sent from it can't be encrypted, and Microsoft says it supports at most 25 users. Without a license it is limited to 50 GB.
How many people should have access to a shared inbox?
Only the people who answer from it, plus read-only access for anyone who needs to watch. In Microsoft 365, more than 25 users on one shared mailbox can cause connection problems, and Microsoft suggests a Microsoft 365 group instead.
What are the 5 Ds of email management?
It is a common triage shorthand, and versions differ. A typical set: delete it, do it now if it takes a minute or two, delegate it, defer it to a set time, or file it for reference. In a shared inbox, delegating means assigning the conversation.
What is diagonal communication?
Communication between people in different departments and at different levels, such as an agent in support asking a manager in finance directly. A shared inbox keeps those conversations visible, so decisions don't get lost in private threads.