Here is how to set up a shared inbox for a small support team in about an hour: pick one or two channels to start, point your support address and website chat into a single queue, decide how conversations get an owner, agree on four statuses, and run a short triage routine twice a day. The steps below cover each of those in order, with the settings to choose, a checklist you can work through in one sitting, and the mistakes that cause dropped or double-answered messages in the first week.
What a shared inbox fixes, and what it does not
A shared inbox is one queue of customer conversations that several people work together, with each conversation owned by one person at a time. It fixes the problems that appear the moment a second person starts answering customers:
- Two people reply to the same customer, sometimes with different answers.
- A message sits unread because everyone assumed someone else had it.
- Nobody can see what was promised to a customer last week.
- Knowledge lives in one person's sent folder and leaves with them.
It will not fix a slow team, missing answers to common questions, or a product that generates too many tickets. Those need saved replies, help articles and product fixes. A shared inbox makes those problems visible, which is a good start.
Step 1: Decide which channels go in first
Start with the channels where customers already reach you, and only those. For most small teams that is email plus website chat. Adding five channels on day one means five sets of settings to learn while the team is still building habits.

A quick way to decide: count last month's customer messages by channel. If one channel carries less than about one in ten messages, leave it for week three. Our omnichannel coverage mapper helps you list where conversations arrive today.
Step 2: Choose where the shared inbox lives
You have three realistic options. The first two use tools you may already pay for; the third is a dedicated tool.
| Option | Setup | Good for | Where it falls short |
|---|---|---|---|
| Google Groups collaborative inbox | Create a group, turn on collaborative inbox features, set permissions | 2 or 3 people answering email only | Email only, basic assignment, no chat or reporting |
| Microsoft 365 shared mailbox | Admin creates the mailbox and adds members with Full Access and Send As | Teams already living in Outlook | No real assignment or status; ownership relies on folders and categories |
| Dedicated shared inbox tool | Forward your support address, add the chat widget, invite the team | Teams answering email, chat and other channels | Another subscription to manage |
In Google Workspace, a group owner can turn on collaborative inbox features so members can assign conversations, mark them complete or flag them as needing no action, as described in Google's collaborative inbox guide. In Microsoft 365, an admin creates the mailbox under Teams and Groups, then Shared mailboxes, and adds members. Microsoft notes that a shared mailbox usually needs no license of its own, and that users need both Full Access and Send As to work it properly (see Microsoft's shared mailbox guide).
Both work for a while. Teams usually move to a dedicated tool when they add chat, want reporting, or get tired of tracking ownership with colour categories. The rest of this guide assumes a dedicated tool, but steps 4 to 6 apply to all three.
Step 3: Connect website chat and email
Email first. Keep your own address, such as support@yourcompany.com, and forward it into the tool. Never publish an address the vendor gives you, because switching tools later would then mean telling every customer a new address.
- Add your support address in the tool and copy the forwarding address it gives you.
- In Google Workspace or Microsoft 365, set the support mailbox to forward every message to that address.
- Verify your sending domain in the tool (usually SPF and DKIM records) so replies arrive as you, not as the vendor, and do not land in spam.
- Send a test email from a personal account, reply from the tool, and check the reply arrives with your name and address.
Then website chat. Most tools give you a short script to paste before the closing body tag, or an app for platforms like WordPress and Shopify. Set your office hours and an away message before you go live, so a visitor at 11pm knows when to expect an answer. The guide to adding live chat to a website covers each platform.
Step 4: Set assignment rules: round robin, ownership or claim-it
Every conversation needs exactly one owner. How it gets one is your choice, and for small teams the simplest rule usually wins.
| Method | How it works | Best for | Watch out for |
|---|---|---|---|
| Claim-it | Agents pick conversations from the unassigned queue | 2 to 4 people who sit close together | Easy tickets get claimed, hard ones wait |
| Round robin | The tool hands new conversations out in turn | 4 or more people on similar work | Uneven loads when someone is out; set availability |
| Ownership | A customer or topic always goes to the same person | Account-based B2B, or billing vs technical splits | One person's holiday stalls their customers |
Whichever you choose, add one rule that never changes: if a customer replies to a conversation, it goes back to the person who owned it. Customers hate re-explaining, and the owner has the context.
Step 5: Use internal notes and collision warnings
Internal notes are messages on a conversation that only your team sees. They replace the side chats in Slack that nobody can find later. Agree on two uses from day one:
- Handoffs: "Waiting on refund approval from Priya, customer told Friday."
- Questions: mention a teammate in a note instead of messaging them privately, so the answer stays with the conversation.
Collision warnings show when someone else is viewing or typing in the same conversation. If your tool has them, make sure everyone knows what the indicator looks like. If it does not, claim the conversation before you start writing, every time.
Step 6: Create statuses and a simple triage routine
Four statuses are enough for a team of two to twenty:

- Open: needs a reply from us.
- Pending: we replied and are waiting on the customer.
- Snoozed: parked until a date, such as a shipment arriving.
- Closed: done. A new reply from the customer reopens it.
Then a triage routine, owned by one person each day on a rota:
- Morning: clear the unassigned queue. Everything gets an owner or gets closed.
- Midday: sort open conversations by oldest first and check nothing is past your reply target.
- End of day: pending conversations older than three days get a follow-up or get closed.
Write your reply target down, even if it is just "same business day". The first response time SLA estimator helps you pick one your headcount can actually meet.
Step 7: Add a second and third channel without chaos
Once email and chat run smoothly for two weeks, add the next channel. One at a time, with a week between each.
- Before connecting, decide who covers the channel and whether it follows the same reply target. Messaging apps usually set a faster expectation than email.
- Write five saved replies for the new channel's most common questions. Short replies read better in chat apps than email-length ones.
- Tag conversations by channel for the first month so you can see whether the channel is worth the effort.
In Sellio, for example, the live channels today are website chat, email, Telegram, Slack and Discord, and WhatsApp and Instagram are coming soon. Each lands in the same shared inbox, so a third channel adds conversations, not another place to check. Its AI agent works on website chat only; messages on other channels go to a person.
How to set up a shared inbox in 60 minutes: checklist
- (5 min) List your channels and pick the first one or two.
- (10 min) Create the workspace or mailbox and invite everyone who will answer customers.
- (10 min) Forward your support address, verify your sending domain, and send a test.
- (10 min) Install the chat widget, set office hours and an away message.
- (5 min) Choose an assignment method and turn it on.
- (5 min) Set up the four statuses and decide who runs triage tomorrow.
- (10 min) Write your first ten saved replies. The canned responses examples are a quick starting point.
- (5 min) Send a message on each channel from a personal account and answer it from the inbox.
Mistakes small teams make in week one
- Replying from personal email "just this once". The customer replies to that person, and the thread leaves the shared inbox for good.
- Forgetting the old address. If customers still write to sales@ or a founder's address, forward those too or answer with a note pointing to support.
- Creating twenty tags on day one. Start with three or four you will actually report on, such as billing, bug, shipping and feature request.
- No owner for the unassigned queue. Claim-it only works when someone checks it on a schedule.
- Auto-reply loops. Two autoresponders replying to each other can create hundreds of messages overnight; many tools can ignore mail marked as automatic.
- Measuring nothing. Note first response time in week one, so you can tell in a month whether things improved.
If you are still choosing a tool, our team inbox page and the Freshdesk vs Help Scout comparison are good next reads, and the pricing page shows what a workspace costs.

FAQ
Can I set up a shared inbox in Gmail for free?
With Google Workspace, yes. A Google Group with collaborative inbox features lets members assign conversations and mark them complete. It handles email only, and assignment and reporting are basic, so most teams outgrow it once they add chat.
What is the difference between a shared mailbox and a shared inbox?
A shared mailbox, as in Microsoft 365, is one email account several people can open and send from. A shared inbox tool adds ownership, statuses, internal notes, more channels and reporting on top of that.
How many people can work in one shared inbox?
Technically, as many as your plan allows. In practice, one queue works well up to about ten to fifteen people. Beyond that, split by team or topic so each group sees a manageable list.
Should everyone see every conversation?
For small teams, yes. Visibility is what stops double replies and lets people learn from each other. Restrict access only for sensitive queues such as billing disputes or HR.
How long does it take to set up a shared inbox?
About an hour for email and website chat, following the checklist above. Allow two weeks for the team's habits to settle before adding more channels.




