Shared Mailbox Best Practices: 12 Rules for Outlook and Gmail Teams (2026)

The short version: a shared mailbox works when every email has exactly one owner, the team reads the same status list the same way, and replies go out from the shared address on an agreed clock. Most problems in a shared mailbox (two people answering one customer, emails nobody answers, "who sent that?") come from skipping one of those three things.

Two platform facts catch most teams out: a Microsoft 365 shared mailbox supports a maximum of 25 users, and by default replies are saved in each sender's own Sent Items, not in the shared mailbox (Microsoft's documentation, checked 5 October 2026).

The 12 rules below work in Outlook (Microsoft 365) and in Gmail (Google Workspace). For each one we say what the mailbox does natively and where you need a habit instead, because neither a Microsoft 365 shared mailbox nor Gmail delegation can assign an email to one person.

Every platform limit on this page was checked against Microsoft's and Google's help pages on 5 October 2026. The response targets, statuses and templates are our own recommendations from running shared inboxes since 2016.

The 12 shared mailbox best practices at a glance

These tips for managing a shared inbox work for any team. The twelve rules, in the order a team usually needs them, are below. The last two columns show whether Outlook and Gmail do it for you or whether it has to be a team habit.

"Habit" means the mailbox has no feature for it, so the team agrees a rule. Rules 1, 4, 5 and 11 are the ones a shared inbox tool adds as features.

1. Give every email exactly one owner

The most important shared mailbox rule is that each email has one person responsible for it, from the first reply to the close, and nobody else answers the customer. Ownership is what stops both failures that shared mailboxes are known for: two people replying to the same email, and nobody replying because everyone assumed someone else would.

Pick one claim rule and write it down:

• First to claim: whoever opens a New email marks it as theirs before writing anything. Simple, and it works for teams of two to five.
• A daily triage person: one person (rotating daily or weekly) assigns every new email in the morning and again after lunch. Better from about five people up, and for mixed inboxes such as info@.
• By topic or customer: billing emails go to one person, technical ones to another, key accounts to their account manager. Combine it with one of the first two for everything else.

A Microsoft 365 shared mailbox and Gmail delegation have no assign button, so the owner has to be visible some other way: a category or label with the owner's name, or a status of "Mine" plus a rule that you never touch an email with someone else's status. Google Groups Collaborative Inbox is the exception among the native options: Google lets members assign a conversation and mark it complete (our Collaborative Inbox guide covers it).

2. Use one status list, and use it the same way

A shared mailbox needs a short list of statuses that everyone reads the same way, so anyone can see what is waiting and who has it. Four is enough for most teams:

In Outlook these are categories, and in Gmail they are labels. Use colors consistently (for example red for New, green for Done) and resist adding more. Every extra status is one more thing people apply differently. Topic labels such as "Billing" or "Bug" are fine on top, as long as they never replace the status.

Two rules keep the list honest: an email in Waiting still belongs to its owner, and Done means archived, never deleted. Microsoft notes that you can't stop users deleting messages in a shared mailbox, so the habit matters more than the permission.

3. Write down the shared mailbox workflow on one page

A shared mailbox workflow (or shared email inbox workflow) is the path every email follows from arrival to archive, written down so new teammates do not have to guess. It does not need to be complicated. This is the six-step workflow we recommend:

Put the page where people will see it: pinned in the team's chat channel, or as the first item in the mailbox itself. Add who triages each day, the response targets from rule 4, and who to escalate to. A workflow nobody reads is the same as no workflow.

4. Set response targets by priority

Response targets (often called SLAs) turn "reply soon" into a clock the whole team can work to. Without them, urgent emails wait behind easy ones. These are the starting targets we suggest for a team working business hours; they are our recommendations, not an industry standard, so adjust them to what your customers expect:

Outlook and Gmail do not time emails against a target, so somebody has to check. The simplest native check is sorting the New and Mine views by oldest first at fixed times each day. Our SLA guide for customer support has a calculator for setting targets from your own volume.

5. Follow shared mailbox etiquette so nobody replies twice

Shared mailbox etiquette is the small set of manners that stops two people answering the same customer. Duplicate replies happen when two people open the same email and both answer it, which looks careless to the customer and wastes the team's time. Neither a Microsoft 365 shared mailbox nor Gmail warns you that a colleague is already replying, so the prevention is in the rules:

• Claim before you write. Change the status to Mine (or your name) before you start the reply, not after you send it.
• Never reply to an email that has someone else's status. If you know the answer, add a note for the owner instead.
• Refresh before you send on long replies, in case the status changed while you were writing.

If duplicates still happen more than about once a week, the team has outgrown a plain shared mailbox. That is the point where collision detection (a live "someone is replying" warning) earns its cost.

6. Use shared templates for the replies you send every week

Shared templates make replies from one address sound like one team, and they save the owner from retyping the same answer. Outlook's My Templates and Gmail's templates are both saved per person, so keep the master copies in one shared document and paste from there, or use a tool with shared templates. Here are four we would start with. Copy them and change the words in square brackets.

Acknowledgment (sent automatically when an email arrives):

Thanks for writing to [Company]. We've got your email and a member of the team will reply within [one business day]. If it's urgent, reply with "urgent" in the subject and we'll look at it first.

Handoff to a colleague (sent to the customer):

Hi [Name], I've passed your question to [Colleague], who looks after [billing] and can fix this. They'll reply on this same email thread by [Tuesday]. You don't need to do anything in the meantime.

Escalation (an internal note to the person you escalate to, not to the customer):

Escalating: [customer name and company]. Problem: [one sentence]. Already tried: [what you did]. Customer is waiting since: [date and time]. What I need from you: [a decision, a refund approval, a fix]. I've told them to expect an update by [time].

Close-out:

Hi [Name], I'm glad that's sorted. I'll close this on our side, but if anything else comes up, just reply here and it'll come straight back to me.

The close-out's last line matters: it tells the customer that the same person owns the conversation if they come back, which is rule 1 seen from the customer's side.

7. Keep internal discussion off the customer thread

Questions between teammates belong in internal notes or the team chat, never in a forward, a Cc or a reply-all on the customer's email. Forwards split the conversation into copies nobody can follow, and an internal comment sent on the wrong thread can reach the customer.

Neither Outlook's shared mailbox nor Gmail has notes on an email, so the native workaround is a link to the email in Teams or Google Chat with the question beside it. It works, but the context lives in two places. Notes attached to the email itself, visible to the team and never to the customer, are one of the main reasons teams move to a shared inbox tool.

8. Reply from the shared address, and keep every reply in the shared mailbox

Customers should get replies from support@ or sales@, not from personal addresses, so the conversation stays in the shared mailbox and anyone can pick it up. Then make sure the team can see what was sent.

In Outlook, Microsoft gives two sending permissions:

• Send As: the reply looks as if it came from the shared mailbox itself. This is the usual choice.
• Send on Behalf: the customer sees "[your name] on behalf of [shared mailbox]". Use it when the customer should see who replied.

By default, Microsoft 365 saves mail sent from a shared mailbox in the sender's own Sent Items, not the shared mailbox's, so the rest of the team cannot see the reply. An admin fixes this per mailbox with Set-Mailbox -MessageCopyForSentAsEnabled $True (and -MessageCopyForSendOnBehalfEnabled $True for Send on Behalf), as described in Microsoft's article on sent mail not being saved.

In Gmail, a delegate or a member of Google's native shared inbox replies from the shared address itself. Google shows the shared address as "From" and the delegate who sent it as "Sent by", unless your admin has set delegated mail to show the account owner only. Google Groups is different: if members reply from their own inboxes, the customer sees a personal address and the reply never reaches the group. Our guide to group emails in Gmail covers sending as the group address.

9. Give access by role, never by shared password, and audit it

A shared mailbox should be opened through each person's own account, so you can see who did what and remove one person without changing anything for the others. Sharing the mailbox's password breaks both, and it gets in the way of two-step verification.

• Microsoft 365: Microsoft says a shared mailbox isn't meant for direct sign-in, and every new shared mailbox has sign-in blocked by default. Keep it blocked. Give Full Access to people who work the mailbox and Send As (or Send on Behalf) only to people who reply. Full Access on its own cannot send.
• Google Workspace: add people as delegates (or use the native shared inbox; Google's delegation page says that in Gmail, delegated accounts and shared inboxes are the same). Don't hand out the account's password.
• Every quarter: list who has access and remove anyone who has changed role or left. Shared mailboxes collect access over time because nobody owns the list.

10. Plan for time off, sick days and people leaving

Plan coverage by handing every open email to a named colleague before any absence, and by reassigning a departing teammate's email before removing their access. Emails owned by someone who is away stop moving, and the customer cannot see why:

• Before time off, the owner hands each open email to a named colleague, with a note, and changes the status to that person.
• Unplanned absence: the triage person reassigns anything in the absent person's Mine view at the next triage.
• Out of hours: the acknowledgment template says when the team will reply, so customers are not left guessing.
• When someone leaves: reassign their open emails, then remove their access the same day (rule 9).
• When someone joins: they read the one-page workflow, shadow triage for a day, and get Send As only once they know the templates.

11. Measure three numbers and review them weekly

Track three numbers every week: first reply time, open emails past target, and emails closed per person. You can only fix a shared mailbox that you can see:

• First reply time, against the targets in rule 4.
• Open emails older than target, by owner.
• How the work is spread: emails owned and closed per person.

Outlook and Gmail have no built-in response-time reports for a shared mailbox, so on the native setup someone counts by hand from the status views, which is why many teams skip it. Spend 20 minutes a week as a team on the oldest open emails, anything past target and anyone carrying too much, then change one rule if something keeps going wrong.

12. Let AI handle the busywork, and keep a person on every reply

In 2026, AI can sort, summarize and draft replies in a shared mailbox, but every reply sent from the shared address should still have a named owner who is accountable for it. The safe pattern is AI on the work around the reply and a person on the decision:

• Good uses: tagging new email by topic and priority, summarizing a long thread for whoever picks it up, and drafting a reply from your help center for the owner to check.
• Guardrails: the owner reads every AI draft before it goes out, the AI only answers from sources you control, and anything involving money or account changes needs a person to approve it.

Microsoft 365 Copilot can now summarize and draft inside a shared mailbox for each licensed user (Microsoft message center MC1246031, rolled out May to June 2026), and Gemini works in Gmail, but neither tags or routes email for the whole team. In Drag, Varley, Drag's AI, tags and prioritizes every email as it arrives and drafts replies from your help center and past conversations for the owner to approve, with AI included on the Plus and Pro plans.

Outlook and Microsoft 365 shared mailbox best practices

A Microsoft 365 (Office 365) shared mailbox is a mailbox that several licensed users open from their own Outlook, with its own address, and which is never signed into directly. These are the platform limits and settings that matter most, from Microsoft's documentation (checked 5 October 2026):

Microsoft's exact words on the user limit are: "A shared mailbox supports a maximum of 25 users. If too many users access the mailbox at the same time, they might experience connection failures or duplicated messages."

Microsoft's sources: About shared mailboxes (updated 13 March 2026), Create a shared mailbox (updated 3 February 2026) and Sent mail is not saved (updated 25 June 2025).

One more Outlook habit helps: set up rules for the predictable sorting (for example, invoices to a Billing folder) so triage only handles what needs a human.

If your team is choosing between a shared mailbox and a distribution list in the first place, our distribution list vs shared mailbox guide covers the difference.

How to add and troubleshoot a shared mailbox in Outlook

To add a shared mailbox in Outlook, an admin creates it in the Microsoft 365 admin center (Teams & groups, then Shared mailboxes, then Add a shared mailbox) and adds members (Microsoft notes it may take a few minutes before members can be added); each member then sees it in Outlook. The fixes for the problems people hit most:

• It doesn't appear in classic Outlook. Automapping adds it after Outlook restarts, but only when Full Access was given to the person directly, not through a security group. Restart Outlook, or add it by hand.
• It doesn't appear in new Outlook or Outlook on the web. Right-click your account name in the folder pane and choose "Add shared folder or mailbox".
• You can read but can't send. Full Access alone cannot send. Ask the admin for Send As or Send on Behalf.
• Your replies vanish from the team's view. They are in your own Sent Items; the admin needs to turn on MessageCopyForSentAsEnabled (rule 8).
• People get connection errors or duplicated messages. Count the users. Microsoft's maximum is 25.

Shared mailbox for Google Workspace users

Google Workspace now has a native shared inbox, and Gmail delegation, Groups Collaborative Inbox and shared inbox tools are the other three ways to run a shared mailbox on Google. Here is what each gives you, from Google's help pages (checked 5 October 2026):

In the native shared inbox, an admin creates an address such as sales@ and adds people as delegates, who can read, send and delete its email. Google lists it for Business Starter, Business Standard and Business Plus and says it is "being released in phases". Some admin consoles do not show it yet, and Google says to use delegated accounts until it appears. With the native shared inbox and with delegation, each reply shows the shared address as From and the delegate as Sent by. Admins can also set delegated mail to show the account owner only, which hides the Sent by line.

Google's sources: Create a shared inbox (updated 1 October 2026), Delegate a user's email address (updated 1 October 2026), Let users delegate access to a Gmail account (updated 1 October 2026) and Collaborative Inbox.

The rules above apply to all four. On the native options, rules 1, 4, 5 and 11 are habits; on Collaborative Inbox, rule 1 is a feature. Our Google Workspace shared mailbox guide covers setup, licensing and storage for each, and our Gmail shared inbox guide compares every way to share one address in Gmail, including password sharing, which we do not recommend.

When a shared mailbox is no longer enough

A shared mailbox stops being enough when duplicate replies happen weekly, more than 25 people need it, or you need response-time reports. These are the signs to look for:

• Duplicate replies more than about once a week, even with the claim rule.
• Emails missing their response target and nobody noticing until the customer chases.
• More than 25 people need the mailbox (Microsoft's maximum), or people keep tripping over each other in Gmail.
• You need to know first reply times or workload per person and are counting by hand.
• Questions about one email are scattered across chat, forwards and Cc's.

At that point the fix is not more rules but a shared inbox for Gmail or Outlook that turns the habits into features: assignment instead of a "Mine" label, a collision warning instead of "refresh before you send", notes on the email instead of a chat link, and reports instead of counting.

Common shared mailbox mistakes

These five mistakes cause most of the trouble we see in shared mailboxes:

1. Replying without claiming first, so two people answer one customer (rule 5).
2. Sharing the mailbox's password instead of giving each person access (rule 9).
3. Deleting instead of archiving, so the history is gone when a customer writes back (rule 2).
4. Forwarding emails to ask a colleague, which splits the conversation into copies (rule 7).
5. Leaving replies in personal Sent Items, so nobody else can see what the customer was told (rule 8).

Why shared mailbox best practices are important

Good shared inbox management matters because a shared address is usually the first place a customer, a supplier or a prospect contacts your company, and the mailbox gives no warning when it starts failing. Emails do not bounce when nobody owns them; they just sit. The customer sees slow or double answers, while the team sees a busy inbox and assumes it is being handled.

The rules on this page are cheap to start: a claim rule, four statuses, three response targets, four templates and 20 minutes a week. They cost nothing on any plan, and they make the move to a tool easier later, because the tool then enforces habits the team already has.

Shared mailbox best practices FAQs

Can a shared mailbox have more than 25 users?

Microsoft's documentation says a Microsoft 365 shared mailbox supports a maximum of 25 users, and that too many people using it at once can cause connection failures or duplicated messages. For a bigger team, Microsoft points to a Microsoft 365 group instead. Gmail delegation is looser: up to 1,000 delegates, with about 40 working in the account at the same time.

Which is best for a small team: a shared mailbox or a shared inbox tool?

For two or three people with low volume, a shared mailbox plus the claim rule and four statuses is usually enough, and it costs nothing extra. Once duplicate replies, missed emails or "who has this?" questions happen every week, a shared inbox tool pays for itself, because it adds assignment, collision alerts and response-time reports that the mailbox cannot.

Can I see who replied from a shared mailbox?

In Gmail, usually: replies from a delegated account or Google's native shared inbox show the shared address as From and the person as Sent by, unless your admin shows the account owner only. In Outlook, Send on Behalf shows the person's name to the customer, while Send As hides it. Inside the team, turn on saving sent mail to the shared mailbox so everyone can see each reply.

Does a shared mailbox need a license?

Not in Microsoft 365, up to 50 GB. Each person who opens it needs their own licensed Exchange Online mailbox, and the shared mailbox itself needs a license only for more than 50 GB (100 GB with Exchange Online Plan 2), for archiving or for litigation hold. In Google Workspace, Google does not publish license terms for its native shared inbox.

Can two people use a shared mailbox at the same time?

Yes. In Microsoft 365, up to 25 users can use one shared mailbox, though Microsoft warns that too many at once can cause connection failures or duplicated messages. In Gmail, about 40 delegates can use an account at the same time. Being in it together is fine; replying to the same email is the problem, which is what the claim rule prevents.

Related guides: shared mailboxes in Outlook and Gmail, and when to use a shared inbox

• Team shared inbox: ownership models and the five workflows of a healthy team inbox.
• Google Workspace shared mailbox: Google's native shared inbox and delegation, set up step by step.
• Distribution list vs shared mailbox: which one you need in Microsoft 365 and Gmail.
• SLA for customer support: setting response targets, with a calculator.
• Best shared inbox software: 11 tools compared on price, AI and fit.

Ready to turn these habits into features for your Gmail team? Start a 7-day free trial of Drag, no card needed.