Shared Inbox Software That Answers the Email, Not Just Sorts It
Every shared inbox tool sells the same picture: your team, beautifully coordinated, dividing up email that your team still has to answer. InReply starts from a different question: why is a human answering most of it at all? Connect your info@, hello@ or bookings@ address, let the AI answer what it can from your own knowledge, and give your team one shared list of the emails that genuinely need a person. Keep Gmail or Outlook. Skip the helpdesk.
The shared inbox problem, stated honestly
Somewhere in your business there is an address that belongs to everyone and no one. It is called info@ or hello@ or bookings@, and the way most small teams run it is a password in a spreadsheet and a vague agreement about who checks it. The failure modes are famous: two people answer the same email, nobody answers the awkward one, and the enquiry that arrived on Friday evening gets its reply on Tuesday.
An entire software category exists to fix this. Missive, Hiver, Gmelius, Front and Help Scout all give the team a proper shared view with assignments, internal notes, collision detection and reports. These are good products, and later in this page we will be specific about when you should buy one. But notice what the whole category has in common: it is coordination software. It helps humans divide up email that humans still answer. Every reply is still read, thought about, written and sent by a person on a paid seat, and the seat is how you pay: per user, per month, forever.
For plenty of shared inboxes, coordination is not actually the bottleneck. Look at a week of your own info@ traffic and count how many messages are the same questions on rotation: prices, availability, opening hours, booking changes, "do you do X?". If most of the queue is routine, then software that helps five people share the routine is solving the wrong problem. The right problem is making the routine answer itself.
The per-seat maths nobody puts on their pricing page
Because the classic suites price per user, the cost of "just letting the whole team see the inbox" scales with headcount rather than with email. Here is what a 5-person team pays per month at list prices retrieved on 22 July 2026:
- Hiver Growth at $25/user/month (2-seat minimum): $125/month, before you touch the $55+ Pro tier where most of the good features live.
- Front Starter at $25/seat/month: $125/month, with Professional at $65/seat, or $325/month for five.
- Missive Productive at $24/user/month billed yearly: $120/month (Starter is $14/user but capped at 5 users).
- Gmelius Growth at $25/user/month billed yearly: $125/month.
- Help Scout Standard at $25/user/month: $125/month, with the Plus plan at $45/user, or $225/month for five.
That is $120 to $325 every month, and here is the part worth sitting with: after paying it, your team still answers every email. The subscription bought visibility and ownership, not fewer emails. If two more people join the company, the bill goes up again, still without a single email being answered by the software.
InReply inverts the pricing because it inverts the work. Plans are a flat monthly workspace price, from £39/month, scaled by email volume (credits) rather than by seats. Adding your fifth or sixth teammate costs nothing, because teammates are not the unit of value. Answered emails are.
A different model: connect the address, answer the volume
InReply is an AI email agent, not a coordination layer. It connects to the shared Gmail or Outlook mailbox you already have via OAuth: no new client for the team to adopt, no migration, no forwarding rules. Then the work splits in two.
- The AI answers what it can. Replies are grounded only in your workspace's knowledge base: your FAQs, documents, policies and prices. Playbooks control tone, behaviour and routing per scenario, so booking enquiries and billing questions are handled by different rules in different voices. On Autopilot, confident grounded replies are sent automatically. In Ghost Mode (available on every plan), every reply is saved as a draft in the shared mailbox for a human to review and send.
- Your team sees what it cannot. When the answer is not in the knowledge base, or the email needs a decision, InReply does not guess. The email lands in a shared actions list that everyone with inbox access can see, with urgent messages flagged. That list is the team's single view of "what still needs a person", which for a small team is the useful core of what a helpdesk provides.
Access works the way a shared inbox always should have. Team members sign in with their own accounts and get per-inbox access, so the password to info@ stops circulating. Customers keep writing to the same address and keep getting replies from it; what changes is how many of those replies a human had to produce.
The practical effect on the famous failure modes: the routine majority of the queue is answered without anyone dividing it up, so there is less to collide over in the first place. And the awkward emails, the ones that used to sit unanswered because everyone hoped someone else would take them, are on a visible shared list with the urgent ones flagged, rather than buried between newsletters in a mailbox nobody owns. For the full mechanics, see how the AI email agent works.
Where the classic suites genuinely win
This page would be easier to write if InReply did everything the suites do plus AI, but it does not, and you should know exactly where the line is. InReply has no ticket assignment, no collision detection, no internal comments or notes on conversations, no SLA reporting and no round-robin routing. Those are real features, the suites do them well, and some teams need them.
Choose a coordination suite when:
- Your conversations are long, high-touch and genuinely need a specific owner: account management, complex B2B support, anything where "who is handling this?" is a daily question with a non-obvious answer.
- You manage agents against response-time targets and need SLA dashboards and workload reports to do it.
- Your team collaborates inside threads: drafting together, leaving internal notes, looping in specialists before a reply goes out.
Choose InReply when:
- The real problem is volume: too many routine enquiries for the people available to answer them.
- Most of the traffic could be answered from a good FAQ if only the FAQ could type.
- You want the team to keep Gmail or Outlook rather than adopt, and pay per seat for, a new client.
If your team's complaint is "we keep tripping over each other in the inbox", buy coordination software. If the complaint is "we cannot keep up with the inbox", coordination software will organise the drowning. Answer the volume first, then see what coordination problem is actually left.
Shared inbox tools compared (July 2026)
Competitor facts last verified 22 July 2026
| Tool | Model | Where the team works | Price (as verified, 22 July 2026) | 5-person team |
|---|---|---|---|---|
| Missive | Team email client with chat and assignments | Missive's own app (web, desktop, mobile) | $14-$36/user/mo billed yearly | $120/mo (Productive) |
| Hiver | Shared inbox and helpdesk; Gmail-native product plus a standalone platform | Inside Gmail, or Hiver's platform | From $25/user/mo, 2-seat minimum; Pro from $55 | $125/mo (Growth) |
| Gmelius | Gmail collaboration layer | Inside Gmail (Outlook waitlist only) | $19-$40/user/mo billed yearly | $125/mo (Growth) |
| Front | Omnichannel customer operations platform | Front's own app | $25-$105/seat/mo | $125/mo (Starter) |
| Help Scout | Helpdesk with shared inboxes and docs | Help Scout's own app | $25-$75/user/mo | $125/mo (Standard) |
| InReply | AI agent that answers from your knowledge | Your existing Gmail or Outlook, plus a shared actions list | £39-£149/mo flat per workspace | Same flat price, seats not billed |
Missive ($14-$36/user/month billed yearly, per its pricing page) is a genuinely nice team email client with chat, assignments and shared drafting. It is also exactly that: a client. The whole team moves into Missive's app to get the benefit, which is the adoption cost this page's title is about.
Hiver is the Gmail-native veteran, with a product that runs inside Gmail itself alongside a newer standalone platform. Plans start at $25/user/month with a 2-seat minimum, with the popular Pro tier from $55/user (pricing page, 22 July 2026). Strong assignment, SLA and analytics features; every reply still human-written. See our Hiver alternatives page for the fuller picture.
Gmelius ($19-$40/user/month billed yearly) also lives inside Gmail, which keeps adoption friction low for Google teams. Its Outlook support was waitlist-only as of 22 July 2026 ("Start with Outlook: Waitlist is open" on its homepage), so mixed-provider teams should check before committing.
Front ($25-$105/seat/month) is the heavyweight: omnichannel, deeply integrated, built for scaled customer operations teams. For a 5-person business answering info@, it is a lot of platform, and five Professional seats run to $325/month.
Help Scout (from $25/user/month, with a limited free plan) is the friendliest of the classic helpdesks and includes AI drafting assistance on paid tiers, plus a pay-per-resolution AI answers add-on listed at $0.75 per resolution (pricing page, 22 July 2026). The base model remains per-seat helpdesk software in its own app.
Every tool above charges per person to organise email that people still answer, and three of the five require the team to work in a new app. InReply charges a flat workspace price to answer the routine majority from your own knowledge, inside the Gmail or Outlook you already have, and to put the remainder on one shared list.
"Do we need an email ticketing system?"
Probably not yet, and possibly not ever. Ticketing systems exist to manage a large backlog of human work: queues, statuses, priorities, agent performance. They earn their keep when you have many agents and genuinely complex conversation flows. But a small team googling "email ticketing system" is usually describing a symptom, not a requirement. The symptom is an inbox that has outgrown informal habits: things get missed, nobody knows what is outstanding, customers chase.
There are two cures. One is to formalise the human work with tickets. The other is to shrink the human work until informal habits are enough again. If sixty emails arrive a day and forty of them are questions your website already answers, an agent that handles those forty leaves a queue of twenty, and a shared actions list with urgent flagging manages a queue of twenty just fine. You can always add a helpdesk later if you scale into needing one; it is much harder to un-adopt one, and un-training your customers off ticket numbers is harder still.
It is the same trade-off businesses weigh against hiring help or outsourcing to an answering bureau, which we cover honestly in our email answering service comparison.
Set up: connect the address, load the knowledge, go
Because InReply works on the mailbox rather than replacing it, rollout is one person's job for one afternoon, not a team migration.
- Connect the shared mailbox. Sign in to info@ (or hello@, or bookings@) via Google or Microsoft OAuth. No password sharing, no new client, revocable any time. Works with Gmail and Outlook, and a workspace can hold both.
- Load your knowledge. FAQs, documents, policies, prices. This is the only material replies are drawn from; when the answer is not in it, the email goes to a human instead of getting an invented reply.
- Grant the team access. Each member gets their own login with per-inbox access and sees the shared actions list of emails needing a person, urgent ones flagged.
- Start in Ghost Mode. Every AI reply is saved as a draft in the shared mailbox for review. Move playbooks to Autopilot as they earn your trust.
Plans scale by inboxes and volume, never by seats: Starter (£39/month, 500 credits, 1 inbox), Growth (£79/month, 2,000 credits, 3 inboxes), Scale (£149/month, 5,000 credits, 5 inboxes) and Business (custom, from 10,000 credits, unlimited inboxes). If your shared address runs on Google, the AI email assistant for Gmail page goes deeper on that side; Microsoft teams should read the Outlook version. Every plan starts with a 14-day free trial, no credit card required. See full pricing.
Frequently asked questions
What is shared inbox software? +
Shared inbox software lets a team work one email address (info@, support@, hello@) together without sharing a password. Tools like Missive, Hiver, Front and Gmelius add coordination features on top: assigning conversations to teammates, internal notes, collision detection so two people do not answer the same email, and reporting. They are priced per user per month, and the humans on those seats still write and send every reply.
Can I run a shared inbox in Gmail without extra software? +
Up to a point. Teams typically share a password (risky and against best practice), use Gmail delegation, or set up a Google Groups collaborative inbox. These get several people into one address for free, but coordination stays manual, and none of them reduces the number of emails a human has to answer. Whichever route you pick, every reply is still written and sent by a person.
How is InReply different from Missive, Hiver or Front? +
Those tools organise email for humans to answer; InReply answers email. You connect the shared address via OAuth, the AI replies to what it can from your knowledge base (as sent replies on Autopilot, or as drafts for review in Ghost Mode), and the emails that genuinely need a person appear in a shared actions list with urgent flagging. It is also priced flat per workspace rather than per user, so a 5-person team pays the same as a 2-person team.
Does InReply have ticket assignment, collision detection or internal notes? +
No, and we would rather tell you that here than after you sign up. InReply does not do ticket assignment, collision detection, internal comments, SLA reporting or round-robin routing. If your team's core problem is coordinating many humans across high-touch conversations, a suite like Missive, Hiver or Front is the better buy. InReply is for teams whose real problem is volume: too many routine emails needing answers in the first place.
Do I need an email ticketing system? +
Ask what the tickets are for. Ticketing adds queues, statuses and reports so a team of agents can manage a large backlog of human work. If your backlog is mostly the same twenty questions about pricing, opening hours, bookings and policies, the better fix is to remove those emails from the queue entirely by having an AI answer them from your own knowledge. Many small teams that think they need a ticketing system actually need fewer emails requiring a human.
How does my team access the shared inbox with InReply? +
Each team member signs in with their own account and is granted per-inbox access, so nobody shares the password to info@. Everyone with access sees the shared actions list: the emails the AI left for a human, with urgent ones flagged. Replies themselves continue to come from the shared address your customers already write to.
What happens to emails the AI cannot answer? +
They are left for a human, visibly. InReply only replies from the knowledge your workspace provides; when the answer is not there, or the email needs judgement, it does not invent a response. The email surfaces in the shared actions list, with urgent flagging, so the whole team can see what is waiting on a person. Nothing is silently auto-answered wrongly, and nothing silently disappears.
How much does shared inbox software cost? +
The classic suites are per user per month: Missive $14-$36, Hiver from $25 with a 2-seat minimum, Gmelius $19-$40 billed yearly, Front from $25 per seat, Help Scout from $25 per user (all retrieved 22 July 2026). For a 5-person team that is commonly $100-$300+ every month. InReply is a flat workspace price: Starter £39/month (500 credits, 1 inbox), Growth £79/month (2,000 credits, 3 inboxes), Scale £149/month (5,000 credits, 5 inboxes), Business custom from 10,000 credits. 14-day free trial, no credit card.
Can I connect more than one shared address? +
Yes. Starter includes 1 inbox, Growth 3, Scale 5 and Business unlimited, so info@, bookings@ and support@ can each be connected with their own playbooks and their own per-inbox team access. Mixing providers is fine too: a Gmail inbox and an Outlook inbox can live in the same workspace at no extra cost.
Connect your shared inbox in minutes
Keep Gmail or Outlook, skip the per-seat helpdesk. The AI answers what it can from your knowledge, and your team gets one shared list of what needs a person.