Shared inbox software gives a whole team one customer-facing email address with assignment, internal notes, collision detection and reporting on top. It sits between a free Google Workspace or Microsoft 365 shared mailbox, which has none of that, and a full ticketing system, which adds SLAs, routing rules and multi-channel queues you may not need. Paid team inbox tools run roughly $14 to $105 per seat per month, and the plans are capped by seat count, so the headline rate is rarely what you end up paying.
Most teams that answer customer email do not start with a help desk. They start with one address, support@ or billing@ or hello@, and a handful of people who all check it. That is a shared inbox, and it is the quiet workhorse of back-office customer experience. It is also where replies go missing, two agents answer the same person, and urgent requests sit unread because everyone assumed someone else had it.
The difference between a shared inbox that builds trust and one that erodes it is not the software. It is whether every message has a clear owner, a clear next step, and a way to tell when something is slipping. This guide covers how a shared inbox works, when to use one, and the practices that keep it from turning into a black hole.
What is a shared inbox?
A shared inbox is a single email address that multiple team members can read and reply from together, with visibility into who is handling each message. Unlike a personal mailbox, everyone sees the same conversations, the same history, and the same status, so a customer writing to support@ reaches the team rather than one person who might be on vacation.
That shared visibility is the whole point. When a customer emails a personal address and that person is out, the message waits. When they email a shared inbox, anyone on the team can pick it up, see what was already said, and respond with full context. The mailbox becomes a team workspace instead of a relay to one human.
How does a shared inbox work?
A shared inbox works by giving a team collective access to one mailbox, then layering on ownership and status so the group does not collide. Incoming mail lands in a common queue; a person or a rule assigns each message to an owner; that owner replies from the shared address; and the conversation is marked done when resolved, so the rest of the team knows it is handled.
The mechanics vary by tool. A basic version is a Microsoft 365 or Google Workspace shared mailbox where several people simply have access. A more capable version adds assignment, internal notes, collision detection, and reporting on top. Either way, the workflow is the same in spirit: a message arrives, it gets an owner, the owner acts, and the status reflects reality. Writing that path down explicitly is worth an hour of anyone's time, and the customer service workflow process covers how to define the triggers, owners, and exit conditions before you pick a tool. Everything that goes wrong with shared inboxes is some version of one of those four steps breaking down.
Shared inbox vs distribution list: which do you need?
A distribution list forwards a message to everyone's personal inbox, while a shared inbox holds the message in one place the whole team works from. The distinction matters more than it sounds. A distribution list creates duplicate copies and no shared status, so three people may reply, or nobody does, and there is no record of who owned what.
Use a distribution list when you want to broadcast or notify a group and you do not need a coordinated reply, for example an internal announcement alias. Use a shared inbox when customers expect one coherent response and the team needs to know who is handling each request. For anything customer-facing, support, billing, onboarding, the shared inbox model wins, because accountability and history live in one place instead of scattered across personal mailboxes.
Shared inbox best practices for support teams
The teams that run a shared inbox well tend to follow the same handful of habits. None of them require expensive software; they require agreement and discipline.
- Give every message an owner. The single biggest failure mode is a message that belongs to no one. Assign each conversation to a specific person, by rotation, by topic, or by workload, so there is always one name accountable for the reply. "Everyone is watching it" reliably means nobody is.
- Run a coverage rota. Put one or two people on inbox duty for set blocks of the day rather than asking the whole team to half-watch it all the time. A clear rota means the inbox is always covered and the rest of the team can do focused work without guilt.
- Use internal notes, not side channels. When agents discuss a customer's issue in Slack or a separate email, the context is lost the moment someone else picks up the thread. Keep the discussion attached to the conversation as private notes so the next person has the full picture.
- Avoid collisions. Decide how you will know when someone is already replying, whether that is collision detection in a tool or a simple convention of assigning before you start typing. Two replies to the same customer reads as a team that does not talk to itself.
- Save and reuse answers. For the questions that come up constantly, keep approved templates so replies are fast and consistent, then personalize the opening line. Once the repetitive share gets large enough, an AI layer that answers and qualifies the routine messages is the next step past templates. Consistency is part of the experience; customers should not get three different answers to the same question depending on who replied.
- Set a definition of done. A conversation should be open or closed, and closed should mean the customer's request is actually resolved, not just replied to. An inbox full of half-finished threads marked done is worse than an honest backlog.
- Write a short etiquette guide. Agree on tone, signature, how to hand off, and when to escalate, then write it down. Give the "when to escalate" part a real backbone with a written customer service escalation matrix so a hard message moves to the right owner instead of stalling in the queue. Shared inbox etiquette is what keeps a dozen people sounding like one coherent company instead of a dozen strangers.
Routing: get the message to the right person fast
Most of the time lost in a shared inbox is spent figuring out where a message belongs. A billing question lands in support@, gets read, gets forwarded, waits again, and the customer experiences all of that as silence. Good routing kills that delay.
Start with the structure of your incoming mail. A lot of it is predictable: certain senders, subjects, or phrases reliably mean a certain type of request. Set rules that tag and assign those automatically so they reach the right owner without a human triaging them first. For the genuinely ambiguous messages that remain, have one person triage on a rota and assign them quickly rather than letting them sit. The goal is that no message waits to be understood; it waits, at most, to be answered. This is the same intake problem that decides response times across support, covered in more depth in our guide to turning support email overload into structured action.
Measure what the inbox is telling you
A shared inbox is one of the richest sources of operational signal you have, but only if you capture it. Track first response time, resolution time, and volume by category, and the inbox stops being a daily firefight and becomes a readout of where your business is creating work for itself.
The categories matter as much as the timings. If a quarter of your inbound is "where is my invoice" or "I sent that document already," the inbox is telling you exactly which upstream process to fix. The same flood of email that feels like a burden is also a free, continuous survey of your operation's weak points. Treat those recurring themes as feedback and route them into a real customer feedback loop, so the pattern in your inbox actually reaches the team that can fix the upstream cause. Pair the response metrics with the category mix and you can both run the inbox better today and stop the most common requests from being created at all. The repeated questions are also the raw material for a customer service knowledge base that lets customers answer them without writing in at all. A shared inbox is also the natural first step toward omnichannel customer service: once one channel runs on shared context, the next move is connecting your other channels to the same customer record so nobody has to repeat themselves when they switch.
When to graduate from a shared mailbox to a help desk
A plain shared mailbox in Google Workspace or Microsoft 365 is fine up to a point. You will know you have outgrown it when assignments live in your head instead of the tool, when you cannot answer "what is our average response time" without guessing, or when collisions and dropped threads become routine rather than rare. Those are signs the volume now exceeds what convention alone can manage. Before you buy anything, check whether the real problem is upstream: turning unstructured support email into routable action often removes more triage work than a new tool does.
At that stage, a dedicated customer service ticketing system earns its cost by enforcing the practices above automatically: every message gets an owner, status is unambiguous, notes stay attached, and reporting is built in rather than reconstructed. The decision is the same one you face elsewhere in back-office operations, where the manual version works until volume makes the cost of mistakes higher than the cost of the tool. For the broader case that this operational plumbing is where customer experience is actually won or lost, see why CX is won in the back office, and how it fits the wider practice of customer experience operations.
Shared inbox software compared: what the main tools cost
Shared inbox software costs $12 to $25 per user per month for a small support team at the annual rates vendors publish, and $55 to $115 once you need ticketing, SLAs and advanced routing. The rates look close together and are not, because vendors bill on four different units: per seat, per ticket, a flat team price, and per AI resolution. We read every figure below on the vendor's own pricing page on September 22, 2026.
| Tool | Published price (checked 2026-09-22) | Billing unit | Where shared inbox and assignment start | Caps and catches |
|---|---|---|---|---|
| Drag | Starter $12, Plus $18, Pro $24 per user/mo annual; $16, $22, $30 monthly | Per user | Every plan, with collision detection | Gmail only. Round robin and Drag Agent on Pro |
| Helpwise | Standard $12, Premium $23, Advanced $39 per user/mo annual; $15, $29, $49 monthly | Per user | Every plan, with collision detection | Standard covers 2 to 10 users; round robin from Premium; 3 extra inboxes $49/mo |
| Missive | Starter $14, Productive $24, Business $36 per user/mo annual; $18, $30, $45 monthly | Per user | Every plan | Starter caps at 5 users, Productive at 50; AI needs API access, from Productive |
| Keeping | Essentials $14, Advanced $24, HIPAA $49 per user/mo annual; $19, $29, $59 monthly | Per user, 2 user minimum | Every plan, with collision detection | Essentials includes 2 mailboxes; Advanced unlimited |
| Gmelius | Meli $19, Growth $25, Pro $40 per user/mo annual; $21, $33, $50 monthly | Per user | Growth, with collision detection | Enterprise is quote only with a 50 user minimum |
| Help Scout | Standard $25, Plus $45, Pro $75 per user/mo annual; $30, $54, $90 monthly | Per user | Every plan; round robin from Plus | Standard includes 2 inboxes, Plus 5, extra inboxes $10/mo; Pro has a 10 user minimum; AI Answers $0.75 per resolution |
| Front | Starter $25, Professional $65, Enterprise $105 per seat/mo annual; $35 and $85 monthly | Per seat | Every plan | Starter caps at 10 seats, Professional at 50; Autopilot $0.05 triage, $0.39 draft, $0.89 per full resolution; Copilot $20/seat |
| Hiver | Growth $25, Pro $55, Elite $85 per user/mo annual; $35, $65, $95 monthly | Per user | Growth | Skill based routing on Elite only; voice $30 per voice seat |
| Freshdesk | Growth $19, Pro $55, Enterprise $89 per agent/mo annual | Per agent | Growth; round robin and load balancing from Pro | AI Agent: 500 sessions included, then $49 per 100; Copilot $29/agent |
| Zendesk | Support Team $19, Suite Team $55, Suite Growth $89, Suite Professional $115 per agent/mo annual; $25, $69, $115, $149 monthly | Per agent | Support Team (email ticketing) | A ticketing system rather than a shared inbox; AI billed per automated resolution |
| HubSpot Service Hub | Starter $7, Professional $90 per seat/mo annual; $20 and $100 monthly | Per seat plus credits | Starter | Onboarding fee $1,500 on Professional, $3,500 on Enterprise; Customer Agent uses 50 credits per resolved conversation |
| Helply (formerly Groove) | Starter $49, Pro $199, Scale $449 per month | Flat per team, unlimited users | Every plan | Starter 3 mailboxes, Pro 10, Scale unlimited; 15% off annual; AI paid in credits. groovehq.com now redirects here |
| Gorgias | Basic $50 (300 tickets), Pro $300 (2,000), Advanced $750 (5,000) per month annual; Starter $10 monthly (50 tickets) | Flat by ticket volume | Every plan | Overage $0.36 to $0.40 per ticket; AI Agent $0.90 per interaction annual, and each one also counts as a ticket |
| Trengo | Boost EUR 299, Pro EUR 499 per month annual (EUR 349 and EUR 599 monthly) | Flat by team size and conversations | Every plan | Boost 10 users and 500 conversations; extra 100 conversations EUR 15; priced in euros only, the USD toggle is a live conversion |
| Spike Teamspace | Team $4, Business $8 per member/mo annual | Per member | Team | A team email and chat tool, not a support help desk |
| Kayako | Help desk: no published price. AI agent $1 per resolved ticket | Quote, plus per resolution | Not stated | Seat pricing requires a sales call |
| Google Workspace or Microsoft 365 shared mailbox | Included with the seat you already pay for | None | Not applicable | No assignment, no collision detection, no reporting |
What does shared inbox software cost for a 10 person support team?
For ten agents handling about 1,000 customer emails a month, the cheapest dedicated shared inbox tools run about $1,440 a year and the mainstream ones about $3,000, at annual rates. The real spread comes from caps: add one hire and some of these bills jump by thousands, while flat team pricing does not move at all.
| Plan | Year one, 10 agents, annual rate | What the 11th agent does to the bill |
|---|---|---|
| Helply Starter (flat, 3 mailboxes) | $588 at the monthly rate, less 15% on annual | Nothing, users are unlimited |
| Drag Starter or Helpwise Standard | $1,440 | Drag adds $144; Helpwise Standard stops at 10 users, so the team moves to Premium at $3,036 |
| Keeping Essentials | $1,680 | Adds $168 |
| Freshdesk Growth or Zendesk Support Team | $2,280 | Adds $228 |
| Missive Productive (Starter stops at 5) | $2,880 | Adds $288 |
| Help Scout Standard, Hiver Growth or Gmelius Growth | $3,000 | Adds $300 |
| Front Starter | $3,000 | Starter stops at 10 seats, so 11 seats on Professional is $8,580 |
| Gorgias Pro (2,000 tickets) | $3,600 | Nothing; volume, not headcount, sets the price |
| HubSpot Service Hub Professional | $10,800 plus $1,500 onboarding | Adds $1,080 |
Two traps are worth naming. First, almost every vendor headlines its annual rate, and the month-to-month price is 17% to 40% higher: Help Scout Standard is $25 annual against $30 monthly, Front Starter $25 against $35. Compare quotes on the same billing term or the cheaper-looking tool may not be cheaper. Second, inbox count is priced separately at some vendors. Help Scout Standard includes two inboxes and charges $10 a month for each extra one, Keeping Essentials includes two mailboxes, and Helpwise sells three extra inboxes for $49 a month, so a team running support@, billing@ and orders@ can outgrow the entry plan on mailboxes before it outgrows it on seats.
The seat caps matter more than the per-seat rate for a growing team. Front's Starter plan stops at 10 seats and Professional costs $65, so the eleventh hire is not a $25 decision, it is a $40 per seat jump across the whole team. Missive's Starter stops at 5. Ask each vendor what your bill looks like one seat past the cap, not at your current headcount.
Which shared inbox tool fits which team
| If your team | Look at | Because |
|---|---|---|
| Is 2 to 5 people and already lives in Gmail | A Google Workspace shared mailbox, or Gmelius | Gmelius layers assignment onto the Gmail interface people already use, which removes the retraining cost |
| Runs relationship-driven B2B email where threads matter more than tickets | Front or Missive | Both keep the conversation as an email thread with internal discussion attached, rather than converting it into a ticket record |
| Wants a clean support product with a knowledge base included | Help Scout | Docs sites are part of the product, so the self-service layer does not need a second vendor |
| Handles high volume across email, chat and phone with SLA commitments | Zendesk or another ticketing system | Shared inbox tools generally do not enforce SLAs, tiered routing, or multi-channel queues |
| Needs internal chat and shared drafting alongside customer email | Missive | Co-drafting and team chat are built in rather than bolted on through Slack |
None of these is a wrong answer for a small team. The expensive mistake is buying a ticketing system to solve a coordination problem that a $24 per seat shared inbox solves, then paying for routing rules and SLA policies nobody configures. If you are genuinely unsure which side of that line you are on, the criteria are laid out in our guide to choosing a customer service ticketing system.
What to test before you buy shared inbox software
- Send yourself a message and reply from two accounts at once. Collision detection is the feature people buy for and the one that varies most. Watch whether the second person is warned before they start typing or only after they send.
- Connect the second and third address. Almost every team ends up with more than one inbox. Find out on the trial whether extra addresses cost extra, because Help Scout charges $10 a month per additional inbox and others include them.
- Ask for the report you will actually use. First response time by inbox and by person, for a date range you choose. If it needs an export to a spreadsheet, you have not solved reporting.
- Price the plan one seat above the cap. Get the number in writing before you sign an annual contract at the tier below it.
- Forward a real message with a 30-message thread and an attachment. Rendering long, messy, forwarded threads is where these tools quietly differ, and it is most of what a support inbox contains.
Frequently asked questions about shared inboxes
How do you manage a shared inbox effectively? Manage a shared inbox by assigning every message an owner, running a coverage rota so it is always watched, keeping discussion as internal notes on the thread, and tracking response and resolution times. The core idea is that no message belongs to "the team" in the abstract; each one belongs to a named person with a deadline.
What is the difference between a shared inbox and a shared mailbox? The terms are often used interchangeably. In practice, "shared mailbox" usually refers to the basic feature in Microsoft 365 or Google Workspace where several people access one mailbox, while "shared inbox" often implies a richer tool that adds assignment, collision detection, and reporting on top of that mailbox.
How many people can use a shared inbox? There is no hard limit that matters for most teams; the practical ceiling is how many people can work the same queue without colliding. Beyond a handful of agents, you need assignment and status features to keep them from stepping on each other, which is the point at which a dedicated tool starts to pay off.