A shared inbox alternative that keeps email simple.
A Gmail or Outlook shared inbox works until two people answer the same email at once. Solves turns support@ into owned, SLA-tracked tickets without changing how your customers reach you. Same email simplicity, with ownership, public and private separation, timers and multi-brand on top.
See it in action
Owned, timed tickets in place of a messy shared inbox
Every email becomes a ticket with one owner, a clear state and a response timer. A glance at the queue shows what is outstanding and what is ageing, instead of a wall of read and unread mail.
- One owner per ticket, so nobody doubles up or assumes someone else has it
- First-response and resolution SLA timers, with a breaching view for overdue work
- Known states from New to Closed, so nothing hides behind a read flag
The short answer
Why a shared inbox breaks the moment two people touch it
A shared inbox is one address that several people read and reply from. It is the right tool for a solo founder or a quiet week. It stops being the right tool the instant two people are answering at the same time, because plain email was never built to share work safely.
The failures are familiar. Two people open the same email and both reply, so the customer gets two answers that disagree. Someone marks a message read while skimming, and it drops out of sight with nobody on it. A reply sits in Drafts for a day because the person who started it went home. There is no record of who owns a thread, no agreed time to respond by, and no way to see what is ageing until a customer chases. Internal comments end up either in a separate chat, where they lose the email they relate to, or forwarded around, where they risk reaching the customer.
None of that means email is the problem. Email is exactly how your customers want to reach you, and it should stay that way. The problem is using a personal inbox to do a team's shared work. A support ticket system keeps the email and fixes the sharing: every message becomes a ticket that one person owns, in a known state, with a timer and a clear line between what the customer sees and what stays internal.
What you keep, what you gain
Keep the email simplicity, gain the structure
Moving off a shared inbox should feel like an upgrade, not a migration to a heavy new system your customers have to learn. Solves is deliberately email-first, so the parts that already work stay exactly as they are.
What you keep
- Your support@ address. Customers carry on emailing the same place, with nothing to relearn.
- Plain email replies. Answers land in the customer's inbox as normal email, not a portal login.
- A simple way to write. The composer is an email composer, not a workflow builder.
- Your existing inbox during the switch. Run it alongside Solves until the team has settled in.
What you gain
- Ownership and assignment, so exactly one person is responsible for each reply and nobody doubles up.
- Clear ticket states: New, Open, Waiting for Customer, Snoozed, Resolved and Closed, so nothing hides as an unread email.
- A hard wall between public replies and private notes, so internal comments can never reach the customer by accident.
- First-response and resolution SLA timers, with breaching and ageing views, so you can promise a response time and keep it.
- Multi-brand from one queue, so a second support address is another brand badge, not another inbox to babysit.
In short, you keep the channel your customers love and add the structure your team has been improvising in spreadsheets, colour-coded labels and side-chats. The work that used to live in someone's head becomes visible and shared.
What you get
The shared-inbox fixes, built in
Each one targets a specific way a Gmail or Outlook shared inbox falls over once a team has to answer together.
One owner per ticket
Assign a ticket to one person so responsibility is never vague. No more two replies to the same email, or a thread nobody picks up because everyone assumed someone else had.
States, not unread flags
Every ticket sits in a known state: New, Open, Waiting for Customer, Snoozed, Resolved or Closed. Work cannot quietly vanish behind a read flag the way it does in a shared inbox.
Private notes, kept private
Add internal notes on a ticket with a hard separation from public replies. Light collaborators are notes-only, and a stale-reply guard stops you answering on top of someone else's newer message.
Saved replies
Reuse vetted answers instead of rewriting them or hunting through old sent mail. Saved replies can be scoped to a brand or shared across the whole organisation.
SLA timers and ageing
First-response and resolution timers, with per-brand targets, surface a breaching view, so ageing tickets are obvious before a customer chases.
Reports and audit history
See open backlog, ageing, waiting, first response, resolution and created-versus-resolved, with brand filters. A metadata audit history records who did what, without exposing message content.
How it works
Move over without downtime, forwarding-first
You verify sending before you switch a single message, so customers never notice the change underneath.
Set up and verify the mailbox
Add your support address and follow the guided, copyable DNS steps for Postmark. Live sending stays blocked until the mailbox is verified or a founder override is recorded, so a half-finished setup cannot send anything broken.
Forward your shared inbox in
Turn on forwarding from your existing support@ in Gmail or Outlook. New email arrives in Solves as tickets, while your old inbox keeps running, so you can switch with no gap in cover.
Bring history across (coming)
If you are leaving another helpdesk, a guided Freshdesk import is coming. When it ships it will bring contacts, saved replies, open tickets and conversations into a chosen brand, with a preview before you commit, so private notes stay private through the move. In the meantime we will help you plan your move from Freshdesk by hand, including setting up your saved replies.
Work the queue as a team
Assign owners, set priority and tags, reply publicly or note privately, and let the SLA timers track response times. When you are confident, retire the shared inbox and work everything from Solves.
Honest comparison
A shared inbox vs Solves
Where a Gmail or Outlook shared inbox is genuinely fine, and where owned tickets start to earn their place.
| Shared inbox | Solves | |
|---|---|---|
| Customers email support@ | Yes | Yes, unchanged |
| Replies arrive as normal email | Yes | Yes |
| One clear owner per thread | No, anyone can reply | Yes, assigned and visible |
| Stops two people answering at once | No | Yes, with a stale-reply guard |
| Known ticket states | Read or unread only | New to Closed, with Waiting and Snoozed |
| Private notes kept off the customer | Risky: forwards or side-chat | Hard separation from public replies |
| Response-time targets you can see | None | First-response and resolution SLA timers |
| Several brands from one queue | One inbox per address | Brand badges, one unified queue |
| Good fit when | One or two people, light volume | A team that answers together |
A shared inbox is a perfectly good start. If you are one or two people on a light load, you may not need a ticket system yet, and we would rather say so. Solves earns its place once more than one person has to answer and a missed reply starts to cost you.
Have you outgrown it?
Five honest signs a shared inbox is holding your team back
You do not need a ticket system the day you set up support@. You need one when the cost of a missed or doubled-up reply starts to outweigh the comfort of a familiar inbox. These are the signs we hear most often from teams who move to Solves, and the shipped features that answer each one.
You catch two people replying to the same email
The classic shared-inbox failure: two helpers open the same message, both write a careful answer, and the customer gets two replies that do not agree. Assigning each ticket to one owner removes the ambiguity, and the stale-reply guard stops you sending on top of a newer message you have not seen, so a slow draft cannot overwrite a colleague's fresher answer.
Things slip because read does not mean done
In a shared inbox, the only signal a message carries is read or unread, and read gets used to mean handled, looked at and skimmed all at once. A message marked read while someone was triaging quietly drops out of view with nobody on it. Ticket states fix this: New, Open, Waiting for Customer, Snoozed, Resolved and Closed each mean one specific thing, so a glance at the queue tells you what is genuinely outstanding rather than what merely looks opened.
You cannot tell what is urgent or how it is sorted
Every email in a shared inbox looks the same weight, so a refund that has waited two days sits level with a routine question that arrived this morning. Priority levels from low to urgent and reusable tags let you sort the queue by what actually matters, and group recurring themes so a busy Monday does not bury the one ticket that needed answering first.
Nobody can prove how fast you really answer
Ask a shared inbox how long your team takes to first reply and it cannot tell you. Solves puts a timer on every ticket and a reports view on the whole queue: open backlog, ageing work, waiting tickets, first-response and resolution figures, and a breaching view that surfaces the most overdue work first, all filterable by brand. You move from a hunch about how support is going to a number you can show, built only from metadata and event timings, never decrypted message content.
Internal context lives somewhere the email does not
When a shared inbox has no safe place for an internal aside, that context scatters: a forwarded copy with a note on top, a message in a separate chat that loses the thread it refers to, a verbal handover that nobody wrote down. Private notes live on the ticket itself, with a hard wall between what is internal and what the customer sees, so the next person picks up the full story without the risk of an internal comment landing in the customer's inbox.
If none of these ring true yet, a shared inbox may still be the right tool, and we would rather you stayed on it than paid for structure you do not need. If two or three of them sound like your week, that is usually the point where owned, timed tickets start paying for themselves.
Common questions answered honestly
Shared mailboxes, Microsoft 365 groups and Inbox by Gmail
Is a Microsoft 365 group the same as a shared mailbox?
No. A Microsoft 365 group is a collaboration container: a group inbox, a calendar and shared files for a team, often tied to Teams or Planner. A shared mailbox is a dedicated mailbox several people open to read and send as one address, with no separate licence for the mailbox itself, though each person still needs their own account. People mix them up because both let a few people work one address, but neither is a support tool. A group thread and a shared mailbox both still leave you with shared email: no owner per ticket, no states, no SLA timers and no audit of who answered what. That gap is exactly what an email-first ticket system fills.
Why was Inbox by Gmail discontinued?
Google shut Inbox by Gmail in 2019 and moved its best ideas, such as bundling related mail and snoozing reminders, back into the main Gmail app, then concentrated on one product instead of two. Inbox was always a personal email client, so even at its best it had no concept of ticket ownership, a service-level target or a shared queue. The takeaway for a support team is the one Solves is built on: a slicker personal inbox is not a ticket system. However you arrange your labels, shared email hits a ceiling the moment a team has to answer together, and the fix is owned, timed tickets, not a tidier inbox.
Do I have to move my customers to a portal?
No. Solves is email-first by design, so customers keep emailing support@ and keep getting normal email replies. A customer portal and knowledge base are on the roadmap and described as coming, never as live features, precisely because forcing customers to log in to a portal is the kind of friction a shared-inbox replacement should avoid. The point of moving off a shared inbox is to fix how your team works, not to make your customers work harder.
Email-first, on purpose
Solves handles support email: owned tickets, ownership, private notes, SLAs and multi-brand. It does not do live chat, phone or social inboxes. That focus is what lets a small team leave a shared inbox behind without taking on a sprawling contact-centre suite.
FAQ
Shared inbox alternative questions
What is a shared inbox and why do support teams outgrow it?
A shared inbox is a single email address, such as support@ or info@, that several people open and answer from Gmail or Outlook. It works fine for one or two people and a light load. It breaks when volume rises: two people reply to the same email, messages get marked read and forgotten, nobody owns a thread, and there is no record of who promised what by when. A ticket system keeps the email simplicity but adds ownership, states and timers.
Can I keep my support@ address and email replies?
Yes. Solves is email-first and forwarding-first. You keep support@yourdomain and your customers keep emailing it. You forward that address into Solves, replies still arrive as normal email in the customer's inbox, and nobody has to learn a new place to write to. You are changing how your team works, not how your customers reach you.
Will moving off a shared inbox cause downtime?
No. You set up your mailbox and verify sending before you switch anything, then turn on forwarding when you are ready. Until a mailbox passes its checks, live sending is blocked, so a half-finished setup cannot send a broken reply. Existing email keeps flowing the whole time, and you can run the old inbox alongside Solves while the team settles in.
Is a Microsoft 365 group the same as a shared mailbox?
No, they are different things. A Microsoft 365 group is mainly a collaboration container with a group inbox, a calendar and shared files for a team. A shared mailbox is a dedicated mailbox several people open to read and send as one address, with no extra licence for the mailbox itself. Both are still shared email: neither gives you ticket ownership, states, SLA timers or a record of who answered what.
Why was Inbox by Gmail discontinued?
Google retired Inbox by Gmail in 2019 and folded its better ideas, such as bundling and reminders, back into the main Gmail app. It was a personal email client, not a support tool, so it never offered ticket ownership or SLAs. The lesson for support teams is the same one Solves is built on: a tidier personal inbox is not a ticket system, and shared email always hits a ceiling once a team has to answer together.
How is Solves priced compared with adding more inbox users?
Solves uses GBP team bands, ex VAT, not a charge per mailbox user. Starter is £29 a month, Team £79, Growth £149 and Agency/MSP £299, with annual billing priced as twelve months for ten. A Starter at £29 covers 3 users, 1 brand, 1 mailbox and 1,000 tickets a month for small teams. You size the band to your team and let occasional helpers help without a per-seat penalty.
Turn support@ into owned, timed tickets
Keep your address and your email replies. Add ownership, private notes and SLAs in an afternoon, with no downtime to switch.