Shared Inbox vs Ticketing System: Which One a Small Support Team Needs

A shared inbox lets several people read and answer the same support address. A ticketing system turns every message into a record with an owner, a status and rules about what happens next. Most teams of one to five people answering email need a shared inbox with light ticketing: one owner per message, a status, and a way to stop two people replying. A full ticketing system earns its cost when you need service-level timers, routing rules, several channels in one queue, or reports someone else will audit.

How this guide was put together: desk research of Google's and Microsoft's official help pages, checked November 12, 2026, plus Chatsy's own product code. Chatsy publishes this blog and sells a forwarding-based shared inbox with numbered tickets. The Chatsy section is clearly marked, and it says where that inbox stops.

What is the difference between a shared inbox and a ticketing system?

A shared inbox is a mailbox several people can open. A ticketing system is a database of requests that happens to accept email. The difference shows up the moment two people work the same queue.

The middle of that table is where most small teams live: they want an owner and a status per message, but not a rules engine.

Which one fits your team?

Pick the lightest option that answers the questions your team actually asks each morning: "who is on this?", "is this done?" and "did anyone reply twice?"

Signs you have outgrown a shared inbox

These are the signals that conventions are no longer enough:

• Two people answer the same customer. Assignment exists only in people's heads.
• "Did anyone reply?" comes up daily. There is no status besides read and unread.
• Messages wait over a weekend unseen. Nobody owns the queue outside working hours.
• You cannot say how long replies take. Someone asks for response times and the answer is a guess.
• Customers write on two channels. The chat and the email about the same problem live in different tools.
• A contract mentions a response time. You now need a timer and a record, not a promise.

The first three are fixed by a shared inbox with assignment and statuses. The last three usually need a ticketing system or a tool that adds reporting and other channels.

Signs a ticketing system is too much

Ticketing systems cost setup time and discipline. They are the wrong choice when:

• Fewer than a handful of emails arrive a day. Fields, macros and queues add clicks to every reply.
• Nobody will maintain the rules. Automations written once and never reviewed send tickets to people who left.
• Customers expect a personal email. Ticket-number footers and portal links feel like a call center to some audiences.
• You only need to stop double replies. Assignment and a "done" status solve that without a rules engine.

What do the built-in shared mailboxes do?

Before buying anything, check what your email provider already includes. Both big providers ship a shared option, with limits worth knowing.

Google Workspace Collaborative Inbox. A group owner or manager can turn on Collaborative Inbox features for a Google Group. Members with the right permissions can take, assign or drop a conversation, the assignee gets an email notification, and a conversation can be marked complete, as needing no further action, or as a duplicate (Google Workspace Admin Help, checked November 12, 2026). That covers ownership and a basic status. The help page describes no response-time timers or reports.

Microsoft 365 shared mailbox. People open a shared mailbox from their own licensed Exchange Online account; the shared mailbox itself needs no license and stores up to 50 GB. It supports a maximum of 25 users, only people inside your organization can use it, and you cannot prevent users from deleting messages in it (Microsoft Learn, checked November 12, 2026). The page describes no assignment or status per message, so ownership stays a convention.

If your team is two or three people and email is the only channel, one of these may be enough. Our support email setup guide covers forwarding, reply loops and first-week checks for both.

A worked example: three people, one support address

Picture a three-person online shop with one support address and a chat widget. The assumptions are illustrative, not data from a real store.

1. Week one on a plain shared mailbox. All three read every email. Two of them reply to the same refund request. Nobody answers a Saturday message until Monday.
2. Add assignment and statuses. Each email gets one owner, and "pending" means "waiting for the customer". Double replies stop. The Saturday problem stays, because ownership does not create coverage.
3. Add the chat. Customers who already wrote by email now ask the same question in chat. If chat and email live in different tools, the second person to answer has no history. A tool that shows both channels to the same team, ideally on one customer record, fixes that.
4. Stop there unless a new need appears. No contract promises a response time and there is one queue, so routing rules and SLA timers would be overhead.

The shop needed a shared inbox with light ticketing and chat handled by the same team, not a full ticketing system.

How to switch without losing messages

Whichever way you move, keep the customer-facing address the same and change only where it is delivered.

1. Keep the address on your own domain. Customers keep writing to it; you change forwarding or routing behind it.
2. Run both for a week. Forward a copy to the new tool while the old mailbox still receives mail, and compare.
3. Decide what happens to history. Many tools cannot import past threads. Export or archive the old mailbox before you stop using it.
4. Test the reply path. Send from an outside account, reply from the new tool, and check the customer sees your address, not a vendor address.
5. Write down ownership. Who assigns, who covers weekends, and when "pending" becomes "closed".

Where does Chatsy fit, and where does it not?

This section describes Chatsy, the product that publishes this blog.

Chatsy's mailbox is a shared inbox with light ticketing next to an AI chat agent. It is deliberately small:

• How email gets in: you verify your support address with a 6-digit code that expires after 15 minutes, then forward it to an address Chatsy generates for the mailbox. Each new email becomes a numbered ticket, and replies thread into the same ticket.
• What a ticket has: statuses Open, Pending, Resolved, Closed and Spam; priorities Low, Normal, High and Urgent; an assignee; tags; and saved replies.
• Chat and email together: when you link a mailbox to the agent, it gets a Create Support Ticket tool and can open a ticket with the customer's name, email, a subject and a summary it writes. The ticket does not carry the full chat transcript, and chat and email are not merged into one customer history. Live chat handoffs sit in the same dashboard.
• Auto-assign is basic: when it is switched on, every new ticket goes to the mailbox owner. There is no round robin.
• What it does not have: no SLA timers, routing rules or escalation rules; tickets come only from forwarded email or the agent's ticket tool, with no phone, SMS or social channels; no customer portal; no ticket reports by agent; no import of old tickets from another help desk.
• Plans: the mailbox starts on Hobby ($40 a month, 1 mailbox, 1 seat). Standard ($150) has 2 mailboxes and 3 seats, Pro ($500) has 5 and 5. Seats include the owner. See pricing.

That makes it a fit for small teams that want website chat and support email in one place. It is the wrong choice once you need SLAs, routing, more channels or ticket reporting. Then compare the tools in our help desk software guide. Setup steps are in the support email docs, and the product page is shared inbox and email tickets.

Frequently asked questions

Is a shared inbox the same as a help desk?

No. A help desk is a ticketing system with extras such as a knowledge base, a customer portal and reports. A shared inbox is the lighter part: one address that several people can read and answer, ideally with an owner and a status per message.

Can a shared inbox handle SLAs?

Usually not. Built-in shared mailboxes from Google and Microsoft have no response-time timers. If a contract names a response time, use a tool that measures it.

Do customers notice the switch to a ticketing system?

Only if you let them. Keep the same address and reply from it. Customers notice ticket numbers in subject lines and portal links, so decide whether you want those before you turn them on.

How many people can share one inbox?

It depends on the tool. Microsoft says a shared mailbox supports a maximum of 25 users. Coordination usually breaks well before any limit like that, which is when assignment and statuses matter more than the head count.