Shared Team Inboxes Explained: One Place for Every Message
What a shared team inbox is, how it differs from personal email, how to assign and answer messages, set response targets and avoid double replies.
When customer messages arrive in several personal mailboxes, chat tools and social accounts, nobody can see the whole picture. Two people reply to the same message, or nobody does because each assumes someone else will. When the person who knows the customer is on leave, their messages sit unseen. A shared inbox is the standard cure.

This guide explains what a shared team inbox is, how it differs from personal email, the workflow of a message from arrival to close, the rules that stop things falling through, and the measures that tell you if it is working. It ends with the matching features in Call. It pairs with Omnichannel Support Explained.
What a shared inbox is
A shared inbox is a single list of conversations that more than one person can see and work. Each conversation is a thread with the customer's messages and your replies, a status, and usually an owner. Messages from different channels can appear in the same list, so the team works in one place instead of switching between tools.
The difference from a personal inbox is not technical but organisational. In a personal mailbox, a message belongs to whoever received it. In a shared inbox, it belongs to the team until someone takes it, and everyone can see who did.
Personal vs shared inbox
| Personal inbox | Shared inbox | |
|---|---|---|
| Who sees it | One person | The whole team |
| When someone is away | Messages wait | Colleagues can take over |
| Ownership | Implicit | Explicit assignment |
| Oversight | None | Supervisors see waiting and overdue items |
| History | Scattered | One thread per customer conversation |
The flow of a message
From arrival to close
- ArrivesThe message lands in the shared list.
- Seen and sortedSomeone reads it and checks whether it is new or a repeat.
- AssignedOne person takes it, or it is assigned to them.
- First replyThe customer gets a first answer within the target time.
- WorkedFurther replies, notes and actions follow.
- ClosedThe thread is marked resolved; it can be reopened.
Two things make this flow work. First, the status of each conversation, such as open, pending and resolved, is always visible. Second, there is one owner. When two people believe they own the same message, the customer receives two answers, which may disagree.
Rules that keep it from falling apart
Software gives you the list. Rules give you reliability. Agree these before you start.
- Take before replying. Claim or assign the conversation before you write, so nobody else starts the same reply.
- One owner at a time. Hand over explicitly, with a note, rather than letting threads drift.
- Use notes for the team and replies for the customer. Mixing them up is a common and embarrassing mistake.
- Close what is finished. Open threads that are really done hide the work that is not.
- Define urgent. Agree what must be answered first, such as complaints or time-limited requests.
Response targets and what to measure
Customers care mostly about how soon they hear back, so define a first-response target for each channel. Email can tolerate hours; chat expects minutes. Write the target down and measure it. Message Response Time discusses sensible expectations.
Four numbers worth watching
- Waiting on usHow many conversations are waiting for our reply.
- Past the first-response targetHow many have already waited too long.
- UnassignedMessages nobody has taken.
- Oldest waitingThe single message that has waited longest.
Look at the oldest waiting message rather than the average. Averages hide the one customer who has been ignored for three days. Reviewing it each morning keeps standards high without much effort.
A first-response target is not a resolution target. A customer who gets a quick, honest acknowledgement, such as "we have your message and will answer by tomorrow noon", is usually calmer than one who hears nothing for a day. Track both: how soon the first answer came, and how long the whole conversation took to close. If resolution is slow while first replies are fast, the problem is probably hand-overs or missing information, not speed at the keyboard.
Writing the reply
A shared inbox makes it easy to answer quickly, which tempts people to answer carelessly. Good practice is to keep a small set of approved saved replies for frequent questions, written in the customer's language where possible, and to personalise the first line. Use help-centre articles to answer repeated questions, but add a sentence that speaks to the person. Attach files only when needed, and check the message after sending to see whether it was delivered, since some channels cannot confirm delivery. See Auto-Replies Done Well and A Tone Guide for Written Support.
Rolling out a shared inbox
Moving from personal mailboxes to a shared inbox is a change in habits, and habits are harder to change than software. A staged rollout works better than a big switch.
A gentle rollout
- Agree the rulesWrite the five or six rules on ownership, notes and closing.
- Start with one channelBring in the busiest channel first and learn from it.
- Train on real examplesPractise with a few typical and awkward messages.
- Add channelsWiden once the team is comfortable.
- Review weeklyLook at waiting, overdue and unassigned items and fix the causes.
Expect some resistance at first. People who have managed their own mailboxes for years may feel watched. Explain that the aim is cover and fairness: no customer is stranded because one person is out, and no one carries a hidden backlog. Celebrate the first time a colleague rescues a message that would otherwise have waited. It is the clearest proof that the new way works. One View of Conversation History shows how a shared record helps the next person who helps the same customer.
Privacy and access
A shared inbox means more people can see customer messages, so access should follow need. Give each person the access their job requires, record who did what and avoid keeping personal data longer than necessary. Check the rules that apply to you. See Access Controls in a Contact Centre.
Doing it in Call
In Call, the Inbox under Calls (in Easy mode, Inquiries under Essentials) lists messages and phone inquiries in one place. In Full mode you choose a view: Open, Pending, Resolved or All, and can narrow it by channel, to only your own conversations, or with the search box. Counts show how many conversations are waiting on you, how many are past the first-response target and how many are unassigned. A channel that cannot send is marked as not sending, so you know before you reply.
Pick a conversation on the left, read the thread on the right and reply at the bottom. You can insert a saved reply, add a line pointing to a matching knowledge article, or attach a file up to a small size limit. After sending, a message tells you whether it was sent, accepted but not yet confirmed as delivered, or saved but not sent, with the reason. Press Resolve when it is done, and Reopen to bring it back. In Easy mode, Phone inquiries lists what callers asked on your line, and Mark as handled closes a thread. Which channels appear depends on what has been set up for your workspace. For voice, see Per-Queue Voicemail in Call.
Frequently asked questions
What is the difference between a shared inbox and a shared mailbox?
A shared mailbox gives several people access to one address. A shared inbox adds assignment, status and history for conversations, so the team can see who is working on what.
How do we stop two people replying to the same message?
Agree that the person who answers must first take or be assigned the conversation. Then everyone can see the owner.
Which channels can go into one inbox?
That depends on what is connected. Common ones are email, web chat, messaging apps and phone inquiries, and each has its own limits.
What should the first-response target be?
It depends on the channel and customer expectations. Chat is expected within minutes; email can allow hours. Choose a target you can really meet and review it.
Is it safe for many people to see customer messages?
Only if access is limited to those who need it, and you record who views and changes what. Check the privacy rules that apply to you.
How do I handle a conversation that needs a colleague?
Add a note explaining the situation, assign it to the colleague and tell the customer who will answer, so they do not need to repeat themselves.