Shared inbox or help desk? A small-team decision tree.

What you’re actually choosing between

Before the questions, the categories. They overlap, and the marketing for both sides muddies the line on purpose — but the difference matters.

A shared inbox gives a team one collaborative workspace for customer messages. Email, sometimes chat, sometimes social. Assignment, internal notes, tags, search, mobile. The mental model is “all of us, replying to messages from our customers, together.” Examples: Vidual Inbox, Front, Missive, Hiver, Help Scout’s base plan, Gmelius, Helpwise.

A help desk does all that and adds a structured framework around it. Tickets with reference numbers. SLAs and resolution timers. Workflows that route by priority, language, topic, or customer tier. Reporting dashboards. A customer-facing knowledge base. Escalation paths. The mental model is “every customer interaction is a tracked work-item with a defined lifecycle.” Examples: Freshdesk, Zendesk, Help Scout’s Plus/Pro tiers, Intercom, Gorgias.

Some tools straddle the line. Help Scout is the most prominent — its base tier reads like a shared inbox; its higher tiers turn into a help desk. That’s deliberate, and it’s part of why the category gets confusing. The questions below are designed to cut through.

Question 1 — What’s your daily message volume?

Volume is the question most often gotten wrong, in both directions. Small teams overestimate it (“we get a lot of messages” usually means thirty a day spread across three people) and end up over-tooled. Larger teams underestimate it because volume is uneven — spread across the week it’s manageable; on the Monday after a launch it’s a fire drill.

Count by actual messages over a fortnight, not by feel. If your team handles fewer than a hundred a day each, the case for help desk infrastructure is weak. The features are designed to manage volume that you don’t have.

Question 2 — What do your customers expect?

B2B customers, technical buyers, and people who’ve had to chase enterprise software for years tend to expect a ticket number. They want a reference they can quote back. They want a public knowledge base they can search before asking. They want to know where their question sits in a queue.

Most consumer brands — especially craft and bespoke brands, indie ecommerce, small studios — have customers who expect the opposite. A reply that sounds like a human, sent within a reasonable time, that knows what they’ve bought and what they’ve asked. Forcing a ticket number into that conversation makes the experience worse, not better. It signals “you are now a support case” in a relationship that you’d rather kept feeling like “you are now a customer we’re talking to.”

Be realistic about which kind of customer you have and this question often answers itself. The brands that pick the wrong category usually do so because they’ve been told “real businesses have help desks” — which is true for some real businesses and not for others.

Question 3 — What are you measured on?

This is the question that sometimes does require help desk — even for a small team. If you have an SLA in a contract with a customer, or a regulator that requires audit trails, or a CFO who needs monthly resolution-time graphs, you need a tool built around those numbers. Trying to retrofit reporting onto a shared inbox doesn’t work; you’ll end up exporting to spreadsheets and gradually rebuilding what a help desk would have given you.

For most small brands, none of this applies. The metrics that matter to a five-person studio are: are customers happy, are we replying within a day, is the team not drowning. Those don’t need reporting infrastructure. They need attention paid to the right things at the right time.

The hidden fourth: channels

This isn’t really a shared-inbox-versus-help-desk question. It’s a within-category question that catches a lot of teams off guard. Most help desks (Freshdesk, Zendesk, Help Scout) were built when customer service meant email, and their social integrations were added later. They’ll technically receive Instagram DMs — sometimes — but the experience is generally worse than email, with weaker threading, weaker context, and no real awareness of platform-specific things like the 24-hour reply window or Story reactions.

If IG is a real channel for you, this should narrow your shortlist on either side of the help-desk-or-not line. We wrote more about what an IG-aware shared inbox actually needs if it’s the deciding factor for you.

Summary — your answer in one card

When a help desk is the right answer

We sell a shared inbox and we’re biased — so when we say “you actually need a help desk,” we mean it.

The cases where help desk is the right answer:

• You have more than eight full-time support agents.
• You have contractual SLAs with customers and need to evidence response/resolution times.
• You’re in a regulated industry — healthcare (HIPAA), financial services, government — that requires audit trails on customer interactions.
• You need routing logic that depends on multiple custom fields, languages, departments, or customer tiers.
• You need a public, searchable knowledge base as a deflection layer.
• Your team’s success is measured by ticket-throughput metrics rather than relationship outcomes.

If any of those apply, the right answer is probably Help Scout Plus or above, Freshdesk, Zendesk, or one of the vertical-specific help desks (Gorgias for ecommerce, Intercom for SaaS). Trying to make a shared inbox carry that workload is false economy.

When a shared inbox is the right answer

And the inverse. The cases where shared inbox is right:

• Your team is between one and ten people, and customer service is part of everyone’s job rather than anyone’s only job.
• Your channels are email, social DMs, and maybe website chat — not phone, not SMS at scale, not multilingual support across regions.
• Your customers see your brand as the work of people they recognise, not as a service organisation they file tickets against.
• You measure success by “do customers come back” rather than by “what’s our average resolution time.”
• You’d rather pay one flat fee for the whole team than a per-seat licence for everyone who needs access.

If that’s you, Vidual Inbox was built for this case — though there are several good answers in the category, and we’ve written about how we compare with Help Scout in particular. We also wrote a longer piece on why most small brands don’t have a project management problem — they have an email problem, which is the deeper version of this article. And if it was the help-desk aisle you were sent down in the first place, we’ve written up what help desk software needs to mean for a small business — the job list, the free tiers, and the IT sign-off.

The cost of getting it wrong

The cost of picking the wrong category is real but recoverable. If you start with a shared inbox and outgrow it, you migrate to a help desk — export the contact list, import it into the new tool, lose two weeks of momentum, carry on. If you start with a help desk and find it’s overkill, you migrate down — same shape of pain, opposite direction.

The cost that compounds is the cost of the wrong mental model. A team that’s been thinking in tickets for three years has trouble going back to thinking in conversations. A team that’s been thinking in conversations doesn’t naturally pick up the discipline of a ticket-and-SLA workflow. Pick the right category for where your team is now, with a clear-eyed view of whether it’s where your team will be in three years.

If you’re between, and you’re leaning shared inbox, have a look at Vidual Inbox. The trial is fourteen days, no card required. If we’re wrong for your case, book a demo and I’ll tell you straight — including which competitor I’d send you to instead.

Vidual Inbox is available now at vidualinbox.com. 14-day free trial, no credit card required. £34.99/month after that, every feature, every team member, no per-seat surcharges.