A five-person software team answers support from one address. Everyone replies between other work, and someone asks whether they should move to a real help desk. For most teams that size, the honest answer is no, not yet.
A shared inbox is the right tool for a team of 2 to 20 people answering customer email alongside everything else. A help desk earns its cost when you have promised a response time, when support arrives somewhere other than email, or when somebody needs a number the mailbox cannot produce. What follows is what each does well, what a help desk adds, and when to move up.
The difference in one table
| Shared inbox | Help desk | |
|---|---|---|
| What it holds | Email to a team address | Conversations from several channels |
| Built for | A team answering between other work | A support function with shifts and targets |
| Response-time targets | Not tracked | Timers, breach alerts, reports |
| Reporting | Little beyond the mailbox | Volume, first response time, resolution time |
| Channels | Email, chat, phone, in-app, social | |
| Setup | Connect the mailbox, invite the team | Configure queues, targets, fields and views |
Response-time targets and reporting decide most cases. The rest are differences of degree.
What a shared inbox is good at
One address, several people reading and replying from it, and the mailbox as the record. A customer writes to support@, any teammate can answer, and the reply goes out from support@ rather than from whoever typed it.
The history stays in one place. Six months later, “what did we tell this customer” has an answer that does not depend on asking the person who sent it.
Email is also where the customer already is. Nobody installs anything, and nobody checks a second tool for a message that arrived in the first one.
Setup is small: connect the mailbox, invite the team, agree who is answering today. That last part is the work, and no tool does it for you.
What a help desk is good at
A help desk makes each conversation a record with an owner, a status and a clock. When a message arrives it can be routed to a queue, assigned by rule, and measured against a target response time.
It is built for a group of people whose job is support. The screens assume somebody works a queue all day: filters for unassigned, overdue and escalated conversations, saved replies for questions that repeat, and reports that a lead reads on Monday.
What a help desk gives you that a shared inbox does not
| What you get | What it looks like in practice | Worth it when |
|---|---|---|
| Response-time targets | An SLA clock starts when a conversation arrives, and the tool flags a breach before the customer does | You promised a response time in a contract, an RFP or on your pricing page |
| Reporting | Volume by day, first response time, resolution time, reopened conversations | Somebody outside the support rotation asks for a number |
| Ticket history | Every conversation with an account in one timeline, including last year’s | An account has more than a handful of conversations open |
| More than one channel | Chat, in-app messages, phone and social share a queue with email | A customer’s follow-up arrives somewhere that is not email |
None of these are things a shared inbox attempts, which is a fair trade at low volume and stops being fair once the list is longer than the attention the team gives it.
The signals that mean it is time to move up
- You promised a response time in a contract, an RFP or on your pricing page, and nothing warns you that you are about to miss it.
- Support arrives somewhere other than email: in-app chat, a phone number, a social account.
- One person now spends most of their week on support, and the work stopped being something everyone does between other things.
- You cannot answer “how many conversations did we close last month” without counting by hand.
- The same failure keeps repeating: two people answer one message, or a message nobody owns sits for a day.
- A customer asks what your team discussed six months ago and assembling the answer takes twenty minutes.
Any one of those is survivable. Two or three at once is the point where the tooling becomes the cheaper problem to fix.
What a help desk costs beyond the plan
The seat price is the visible part. The rest is migration, a new tool to check, and a second queue to keep in step with Linear. Somebody has to configure it, usually a developer who was answering support an hour ago.
The running cost is attention. Every conversation now exists in two places, and someone has to decide which one is true.
For a team of five, that overhead is worth paying when most of the list above is true, and hard to justify before then.
Where Chirp sits
If the answer is not yet, the next question is which shared inbox. Chirp is a shared inbox for small software teams that track their work in Linear.
Connect a Google inbox, invite the team, and support@, billing@ and security@ sit in one list with replies going out from the shared address. The mailbox stays the source of record.
Press i in a thread to link a Linear issue. Snooze until the issue is done, and Chirp reopens the thread with a draft that names it. Rules can close, tag, assign and snooze threads, and write drafts. No rule can send email: a reply leaves when a person sends it, or when a script you gave API access to sends one.
It costs $9 per user per month. Access is set per inbox and checked by the server on every read, so a teammate covering support@ does not automatically see security@.
FAQ
Do I need a help desk for a small team? Usually not at first. A shared inbox covers one address, several people and one history. Move up when you have promised a response time, when support arrives on more than one channel, or when reporting matters outside the team.
When should I switch from a shared inbox to a help desk? When the failure is structural rather than personal. Two people answering one message twice in a month is a process problem. Two people answering one message twice a week, with nobody able to say how many conversations are open, is a tooling problem.
Can a shared inbox handle ticketing? It handles the conversation and the history. What it does not give you is a target response time, a report against it, or a customer profile that gathers every conversation.
What are the disadvantages of a shared inbox? There is no target clock and no reporting, so a missed reply stays invisible until the customer chases. Ownership is only as good as the team’s habit of claiming a thread. Anything outside email is out of scope.
Is a help desk worth it for five people? It is worth it when the help desk does work the team cannot do by reading the list: enforcing a response time, reporting on volume, or holding several channels. If none of those is true, the plan buys configuration and a second place to look.
Next step
If you are staying with a shared inbox, the decision left is how to build one. What a collaborative inbox is covers the four ways teams do it, and how each one fails.
