Most small SaaS teams do not start with a help desk. They start with a Gmail alias. Then a Google Group. Then a shared inbox. Then a long argument about tickets.
The words get used as if they were the same. They are not, quite.
A shared inbox is how two people share email. A help desk is how a software company answers someone who has a plan, a bug, and a billing history. We built Fernand as both, so I have a preference. The distinction still shows up in the work.
What a shared inbox is
Several people can see the same mailbox, assign a thread, and reply from the company. Collision detection, so two of you do not send the same answer. Drafts, tags, snooze. It looks like email because it is email.
Help Scout is the version that stays close to mail. Front is the version for a few departments living in the same threads. Collaborative Gmail is what a lot of teams have now, without the assignment.
It fits when almost everything still arrives as email. When two to ten people need the same threads. When you do not yet have a widget, a help center, or an agent you trust. When the job is not dropping a message, rather than seeing the Stripe plan without switching tabs.
If that is the week, a shared inbox is not a stepping stone. It is the tool.
What a help desk tends to add
The inbox stays. Around it: live chat and a contact form, in the same queue, so a widget conversation is not a second product. A knowledge base on your domain, tied to the replies you already send. A little structure. Status, assignment, maybe an SLA. Not a form with forty fields.
Then the SaaS part. Plan, payments, open issues, data from your own API. An AI agent trained on the docs and the old replies, drafting in the inbox and answering in the widget.
A clinic can live in a shared inbox for a long time. A SaaS company keeps answering "what plan am I on" and "is this in Linear" until the inbox shows it.
Fernand is a shared inbox with those pieces included. That is a product opinion. You can assemble the same stack from a mailbox, a chat tool, Notion, and Stripe. The tab count is the part we got tired of.
Three different jobs
| Shared inbox | Help desk | Ticketing system | |
|---|---|---|---|
| Feels like | Email, plus chat and docs | A back office | |
| Unit of work | A conversation | A conversation | A ticket |
| Best at | Small teams sharing a mailbox | SaaS support with context | IT, ops, internal requests |
| Goes wrong when | You need in-app chat and a help center | You force it into a large-company workflow | Customers have to learn your portal |
Zendesk started as tickets and became a platform. Jira Service Management is still tickets, and a good one for internal IT. Calling either of those a shared inbox is how a small team inherits a configuration project.
A help desk should still feel like a conversation. The moment a customer has to create an account to ask where their invoice is, something has drifted.
When the inbox starts to feel thin
We noticed it in combinations, not in a single symptom.
The same five questions were half the queue, and they were not in a help center. People chatted in the product, then emailed, and someone stitched the story together. Stripe or the admin opened on every other reply. Bugs landed in Linear with the screenshot missing. A second person joined support and learned the product from the sent folder. We wanted an agent, and the inbox we had either did not have one or billed it per resolution.
One of those is a nuisance. Three of them is a second job.
It also happens the other way. A small team on a large desk, filling in fields nobody reads, who needed a shared inbox and ten articles. If the tool needs an admin and you are the admin, you may have bought software for a company you do not run yet.
Slack
B2B customers often want a shared Slack channel, not a ticket number. That is still support. It is a channel the inbox has to hold.
Fernand does Slack Connect on the paid plan. Plain and Pylon are built around Slack for larger B2B companies, with the account next to the thread. That shape fits enterprise customers and a success team. It is a lot of product for a founder and a mailbox.
A Slack-only inbox with no email has the same hole as a chat-only widget. The next customer will email you anyway.
What we see teams choose
Two founders, mostly email, often start with a shared inbox. Fernand and Help Scout both do this on a free plan. Help Scout stays closer to mail. We put chat, docs, and an agent in the same place because that is what we wanted when the stack felt like the work. Fernand and Help Scout.
A few teams sharing customer threads, with support not the only one in the conversation, often look at Front. AI is an add-on there. Fernand and Front.
When chat, docs, billing context, and an agent are already obvious, the inbox-only tools fall away. I compared eight help desks by stage. Zendesk shows up when the company is a different size than the one this piece is about.
I do not think this is a matter of taste so much as a stage. The expensive pattern is buying the next one early, or staying in Gmail after the queue already has a name.
Fernand is free to start if you want the inbox and the rest in one tool. Email included, 100 messages a month. We kept the old mailbox up until the new one was obviously quieter.