KoltrixHelp Desk or Shared Inbox? Deciding at Each Company Stage
A shared inbox is enough for longer than most teams think, and a help desk is right sooner than some admit. How to decide at each stage of a company.
On this page(8 sections)
The help desk versus shared inbox question usually gets asked at the wrong time: either far too early, when a founder buys a ticketing system for twelve emails a week, or far too late, when three people are answering the same customer and nobody can say how long anyone waited. The right answer depends almost entirely on what stage you're at.
Here is a stage-by-stage way to decide, along with the signals that tell you it's time to move on.
First, what each tool actually is
The two categories overlap, but they start from different assumptions.
A shared inbox treats support as email. Messages stay threads, replies look like normal mail, and the team sees a common mailbox for addresses like support@ or hello@. Features vary, but typically include shared access, some way of seeing who is handling what, labels or folders, and notes or drafts that teammates can see.
A help desk treats support as tickets. Every incoming message becomes a record with a status, an assignee, a priority and timestamps. Help desks usually add multiple channels (chat, phone, social, web forms), service level targets, reporting, macros, routing rules and a knowledge base.
Neither is better. A help desk is a heavier, more structured tool for a heavier, more structured job.
Stage 1: the founder answers everything
Volume: a handful to a few dozen conversations a week. One or two people reply.
At this stage you need very little:
- A dedicated address like
support@that isn't anyone's personal mailbox - Replies that look like normal email from a human
- A way for a co-founder to see the thread if you're away
A ticketing system here mostly adds friction. Customers get "Ticket #10482 received" auto-replies from a two-person company, and you spend time configuring statuses nobody needs. A shared mailbox on your own domain does the job, and it keeps support close to the people building the product, which is where it belongs this early.
Stage 2: the first support person
Volume: dozens to a couple of hundred conversations a week. A founder plus one dedicated person, maybe a part-timer.
The questions change. Now you need to know:
- Who is handling this thread?
- Has anyone replied yet?
- What did we tell this customer last month?
A good shared inbox still covers this: per-person access to shared mailboxes, visible drafts, labels for status, and full thread history. What you want to avoid is the anti-pattern where support@ forwards to two personal inboxes and both people reply.
This is also the stage to write down your canned answers, refund rules and escalation paths. That documentation matters more than the tool.
Stage 3: a small support team
Volume: hundreds of conversations a week. Three to eight people in support, possibly across time zones.
This is where the decision gets real. A shared inbox can still work, especially if your support is almost entirely email and your team communicates well. But watch for these signals:
| Signal | What it means |
|---|---|
| You need to promise response times and prove you met them | You need SLA tracking and reporting |
| Customers reach you through chat, social and phone too | You need multi-channel in one queue |
| Work has to be routed by skill, language or plan tier | You need routing rules |
| Managers ask for weekly volume, backlog and resolution data | You need reporting built in |
| The same twenty questions make up most of the volume | You need a knowledge base and macros |
| Different teams (billing, technical, onboarding) share one queue | You need queues, groups and handoffs |
If two or three of those apply, a help desk will probably save you time even after the setup cost. If none apply, the structure of a help desk may just slow your team down.
Stage 4: a dedicated support organization
Volume: a large, steady stream across channels, with team leads and a support operations role.
At this point a help desk is almost always the right call. You'll want workforce planning, quality review, detailed analytics, integrations with your CRM and billing system, and automation that a shared inbox isn't designed to provide. Pretending otherwise to avoid a migration only postpones it.
Questions to ask before you switch
Before moving from a shared inbox to a help desk, or picking one for the first time, work through these:
- What percentage of support arrives by email? If it's nearly all of it, the multi-channel features you're paying for may sit unused.
- Do you have formal response-time commitments? Contractual SLAs push strongly toward a help desk.
- Who will own the configuration? Help desks reward someone who tunes rules and macros. Without that person, they decay.
- How will customers experience it? Ticket numbers and portal links feel different from a reply from a named person. Decide whether that matters for your brand.
- What happens to the rest of your email? Support is only one stream. Sales, billing, partnerships and replies to your product's automated mail still need a home.
- Can you get your history out? Check export options before you put years of conversations into any tool.
A middle path
Some teams split the difference. They run a shared inbox for most addresses (hello@, billing@, partners@, replies to product mail) and a help desk only for the high-volume support queue. That works, but you'll have two tools and two places to look. Make the boundary explicit: which addresses go where, and who watches each.
If you're on the shared inbox side today, the scorecard for choosing a business email provider is a useful way to compare options. Koltrix, for what it's worth, is on the shared-inbox side of this line: shared mailboxes with per-mailbox permissions and AI triage, not a ticketing system with SLAs and multi-channel queues. Teams that need those should pick a help desk.
Key takeaways
- Founders and very small teams rarely need a help desk; a shared mailbox on your own domain is enough.
- With a first support hire, invest in documentation and clear ownership before buying more tooling.
- Move to a help desk when SLAs, multiple channels, routing or reporting become real requirements, not before.
- At scale, a help desk is the right tool. Plan the migration rather than resisting it.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
