The quote came back for twelve seats, because twelve was the minimum. The company has eight people, two of whom answer customer mail, and one of those two does it between other jobs. Further down the sign-up flow there's a step asking for an administrator to approve access to the company mailboxes, and nobody in the building is certain who that would be. The founder knows the password to most things. That is not the same as being an administrator, although it's close enough to be expensive.
The distance between what this category assumes about its buyer and what a company of eight actually is: that's the part worth understanding before you shortlist anything. Every page ranking for this search is a list of products with a "for small business" filter applied to it. What running the thing will cost you in administration, in commitments you can't unwind, or in one person's evenings tends not to make the list.
So this article covers the half of the decision that comes after "which one looks good". Whether your business can carry a help desk yet, who in it will have to, and what you're agreeing to when you sign.
The short version
- "Small business" in this category stretches a long way up. What you need at three, ten and thirty people is genuinely different, and the products are built for the far end of that range.
- Connecting a help desk to your company mail isn't a user action. On Google Workspace it takes a super admin; on Microsoft 365 the app permissions involved need Global Administrator approval, and Microsoft's own guidance is to keep that role rare.
- The quote isn't the cost. Add the platform license underneath it, the person who ends up administering it, the configuration month, and whatever you can't undo before renewal.
- A committed license count doesn't shrink when your team does. Both platform vendors publish that in their own billing documentation, and third-party tools copy the shape.
- Some businesses this size shouldn't buy anything yet, and the question is capacity, not fit. If you can't name the person who'll hold the admin role, you're not ready.
What counts as small here, and why the number changes the answer
Everyone writing on this subject uses the word "small" and almost nobody says what changes between one end of it and the other. The number of people who touch the support address is the single variable that decides whether this software helps you or sits on you.
| Team on the address | What the desk looks like | What breaks first | Does software help yet? |
|---|---|---|---|
| 1 to 4 people | One address, everybody reads everything, no rota because none is needed | Nothing, until somebody is away for a week | Rarely. The tool costs more attention than it gives back |
| 5 to 15 people | Two or three regulars plus stand-ins, an unwritten expectation about reply speed, nobody full time on the desk | Cover: handover, holidays, the morning the regular is sick | Usually yes, and this is the band the category serves worst |
| 16 to 40 people | Named roles, somebody owns the queue as an actual part of their job | Consistency and reporting, more than visibility | Yes, and the enterprise feature set finally starts earning its price |
The middle band is the one this article is written for. Below it, buying software formalizes a problem you don't have yet. Above it, the products make sense on their own terms and the feature lists stop looking absurd.
It helps to know where the industry itself draws the line. Microsoft's plan options documentation labels its entire Business family "Business (maximum of 300 users)", with a footnote reserving "the right to enforce the tenant limit of 300 provisioned licenses across the Business family of plans". That's a licensing boundary on a mail platform rather than a statement about help desk products, but it's the vocabulary the whole industry shares: a company of 280 people and a company of 8 are filed under the same word.
My read, and you should treat it as a read rather than a documented fact, is that this is why the software feels heavy at the bottom of the range. When one label covers a 40x span of company sizes, the product gets designed nearer the top of it, because that's where the revenue is. Nothing sinister in that. It just changes how you should read a feature list when you have eight people.
Help desk or IT help desk? Two products share the name
Search results for this term mix two different products, and it's worth thirty seconds to be sure you're shopping for the right one.
A customer-facing help desk handles the people who buy from you: order questions, bug reports, refunds, the mail arriving at support@ or hello@. An internal IT help desk handles your own staff: laptops, passwords, access requests, the broken printer. They share a queue-and-ticket shape and not much else, because their customers, their tone and their measures of success all differ.
The naming gets worse before it gets better. Both major platforms ship an administrator role called almost exactly this, and neither is support software. Microsoft's Helpdesk Administrator role resets passwords, forces users to sign out, manages service requests and monitors service health, and it can only help users who aren't administrators, plus a short list of low-privilege roles such as Directory reader and Reports reader. Google's Help Desk Admin can "Reset passwords for users who aren't administrators", view user profiles and view organizational units. If somebody in your company offers to "set up the help desk", establish which of these three things they mean.
This article is about the customer-facing kind. If you arrived on the wrong word and what you run is a team address rather than a support department, what a shared inbox is and how teams share email is a better starting point, and what changes when a message becomes a ticket record covers the model underneath every product in this category.
The four costs a small business pays that never reach the quote
The per-seat price is the visible cost and usually the smallest one. Four others land on a company this size, and none of them appears on the pricing page.
The license underneath the tool
A help desk doesn't replace your mail. It connects to a mail platform you already pay for, per person, every month, and that subscription keeps running. You're adding a second per-seat bill on top of the first, with its own renewal date, its own admin console and its own idea of who your users are.
That matters more at eight people than at eighty, because the two subscriptions rarely line up. Somebody joins in March and needs a platform license immediately and a desk seat two weeks later, once they're trained. Somebody leaves in September and the two bills stop on different dates, if they stop at all.
The admin seat, which is a person and not a license
Every product in this category needs somebody who holds the keys to your mail platform in order to be connected at all. Not a support agent, and not a paid seat: a named human with a privileged role on your company account. In a company of eight that's the founder, the office manager, or whoever is known for being good with computers. This is the cost that surprises people most, and the next section is entirely about it.
The configuration hours
Connecting a help desk takes an afternoon. Configuring one takes considerably longer, and the two get quoted as though they were the same job. The connection is the demo: authorize access, mail appears, everybody is impressed. Then come the categories, the routing, the canned replies, the business hours, the automations that fire on the wrong thing, and the second pass a few weeks later when the first set of decisions turns out to have been wrong.
It's slow, unglamorous work that happens in the evenings, and at this size it comes out of one specific person's week. Ask the vendor which of the two jobs they're quoting when they give you a number, and ask whether configuration help is billable.
The exit
Two things are hard to reverse once you've signed, and both are worth pricing before you do. The first is the seat commitment, which typically can't be reduced part-way through a term. The second is the configuration itself: whatever you spent those evenings on has to be rebuilt somewhere else if you leave, and that sunk effort is what keeps companies in tools they've stopped liking. Both are covered properly further down.
Who administers it when nobody is an admin
This is the part the product lists skip, and it's the one that decides whether a help desk purchase turns into a bad month.
Connecting a third-party tool to your company mail is a privileged act, not a user preference. On Google Workspace, the prebuilt administrator roles documentation lists installing Google Workspace Marketplace apps, granting domain-wide delegation and restoring deleted users as things only a super admin can do, and describes that role plainly: it "Has access to all features in the Google Admin console and Admin API and can manage every aspect of your organization's account". On the Microsoft side it's narrower but lands in the same place. Even the Application Administrator role, the one named for administering applications, can consent to permissions "except for application permissions for Azure AD Graph and Microsoft Graph", which is exactly the kind of permission a tool that reads your whole team's mail tends to want. That approval goes up to a Global Administrator.
Microsoft is then blunt about how careful you should be with that role. Its security guidelines for assigning roles are a table whose first row reads "Have as few global administrators as possible", because "Global Administrators have almost unlimited access to your organization's settings and most of its data", and whose second row asks you to assign "the least permissive role", meaning "giving administrators only the access they need to get the job done".
So a small business is squeezed from two sides. You need somebody holding a very powerful role on your account in order to buy support software at all, and you've been told to keep that role rare. Both instructions are correct. The way through is to decide the arrangement deliberately, in writing, before you sign anything, and there are three decisions in it.
Who holds the role. One named person, not "the founder and also the developer and also the agency, probably". Write the name down somewhere that isn't that person's laptop.
Who unlocks them. Both platforms document the same failure and give the same shape of answer. Microsoft warns that a Global Administrator "could inadvertently lock their account and require a password reset", and that either another Global Administrator or a Privileged Authentication Administrator can reset it, so you should "have at least a Privileged Authentication administrator in case a Global Administrator is locked out of their account". There's a related quirk with the same purpose: "A Global Administrator can't remove their own Global Administrator assignment", which stops an organization ending up with zero of them. Google puts it more simply: at least one user needs to be a super administrator, "but we recommend having at least two. That way, if one of you forgets your password, the other can reset it for you."
Who inherits the vendor account. This one is separate from the platform role and more often forgotten. If the person who signed up for the help desk leaves, who owns the billing relationship, the admin login and the export? At eight people that's one paragraph of a handover note, and skipping it is how companies get locked out of their own support history.
None of that argues against buying. It argues for doing these three things in the week before the trial instead of the week after something goes wrong.
What a small team needs, and the enterprise features it can safely ignore
Feature matrices in this category are built for a support organization with role separation, and most of what's on them is priced into your quote whether or not you can use it. The useful exercise at your size is subtraction: work out what you can ignore without regret, and what's left is short enough to evaluate properly.
| Feature you are being sold | What it is actually for | Where it starts paying off |
|---|---|---|
| Multi-level queue hierarchies | Routing between teams that don't sit together | A second team with its own manager |
| Agent versus supervisor permission tiers | Limiting what agents can see, change or delete | A desk big enough for somebody to supervise it full time |
| Formal SLA policies with escalation matrices | Proving a response time to a customer who audits it | A response time written into a contract you signed |
| Shift and workforce scheduling | Filling a rota across shifts and time zones | Coverage that runs beyond one working day in one place |
| CSAT survey automation | A trend line that means something statistically | Enough monthly volume for a rating to be a signal and not noise |
| Multi-brand or multi-portal support | Separate customer-facing identities on one desk | A second brand or product with its own support address |
| Approval chains | A second signature before certain replies leave | A refund or compliance policy that names an approver |
Take those out and four things are left that a small desk genuinely can't do without:
- One queue everybody can see, so the work isn't hiding in somebody's personal mailbox.
- An owner on every conversation, so "who has this" is a field and not a question in chat.
- A live signal that a colleague is already replying, since two people answering the same customer is the failure small teams tend to notice first.
- Numbers you can export, because at some point you'll want to know whether any of this worked.
That short list is roughly the shape of a shared inbox tool like TriageFlow: incoming mail gets labeled and assigned to a person automatically, with states like "needs reply" on the conversation and folders for assigned, unassigned and archived. Labels are set up with short written prompts, which is a different starting cost from designing a category schema before anything works. The wider question of which category of product to buy, and the eight criteria that decide a shortlist once you're ready to compare, is worked through in the shared inbox software buyer's guide.
Why the small business tier of an enterprise product still behaves like one
A cheaper tier is a pricing decision, not a design decision. The information architecture, the admin console and the vocabulary were built for a company with somebody whose job includes administering software, and the small-business plan inherits all of it, minus the features you weren't sold. Fewer capabilities, same amount of thinking demanded before the thing does anything useful.
There's one test that settles it, and it costs nothing to run during a trial: how far can one person get on their own, with no call and no consultant, before they need somebody who already knows the product? If the honest answer is "as far as connecting the mailbox", you've just found the configuration month from the section above, wearing a different label.
The cost of choosing wrong at this size
Here's the mechanic that actually bites. Both platform vendors publish it about their own subscriptions, which is why it's worth knowing as a pattern: a committed license count doesn't shrink when your team does.
Google's annual and fixed-term plan documentation is blunt about it. "You can't remove licenses and lower your subscription price until it's time to renew your contract." You can move people around inside what you bought, "as long as you don't exceed your number of purchased licenses", but the floor is the floor. Microsoft's guidance on deleting a user says the same thing from the other direction: deleting an account doesn't stop the bill, reducing license numbers is "a separate step that can be performed by the billing admin", and "if you're paying for an annual plan or if you're in the middle of a billing cycle, you won't be able to remove the license from your subscription until your commitment is completed".
Now put that on a company of eight that committed to twelve seats in an optimistic March. In a quiet November it's paying for twelve, and the configuration month it already spent makes moving feel more expensive than staying. That's how a small company ends up two years into a tool nobody likes.
The same Microsoft page is worth reading for a second reason, since departures are when both costs land at once: giving a colleague access to a leaver's mail "converts the deleted user's mailbox to a shared mailbox", and you have 30 days to restore a deleted account "before the user's data is permanently deleted". Offboarding has deadlines attached whether or not anyone has written them down.
Two questions to put on any quote before you sign it. What's the seat floor, and what happens if we drop below it? And when somebody leaves mid-term, can that seat be reassigned to their replacement, or does it sit paid-for and idle? The fuller set of exit questions, and how the pricing models actually work across the product categories that could serve you, lives on the buyer's guide.
When a small business does not need help desk software yet
Most articles on this term conclude that you should buy something, which is unsurprising given who publishes them. For a decent number of readers the honest answer is "not this year", and the question worth asking isn't whether the software fits your problem. It's whether your business can carry it.
Four signals, and any two together mean wait:
- Nobody can be named as the person who'll hold the admin role and still be here in a year.
- No one person has a free evening a week for the configuration month, and nobody has been given one.
- The commitment period is longer than your visibility on headcount. If you can't say how many people will be answering mail in nine months, don't buy twelve seats today.
- What people actually describe when they complain is being short-staffed, not being disorganized. Software won't fix that; it'll just measure it more precisely, and how support teams scale without breaking is the more useful read.
If two of those are true, the cheaper move is a process one: agree who owns the queue on which day, agree what "answered" means, and write both down. The agreement worth writing down before you buy anything covers the mechanics. If you're unsure whether the constraint is really headcount, a support team size calculator will get you to a rough answer in a few minutes.
Then revisit the decision when your capacity to carry one changes, which is a different event from a busy fortnight. Somebody takes on operations as an actual part of their job. Headcount settles down enough that a twelve-month commitment stops being a guess. The admin role acquires a named holder and a named backup, and somebody has an evening a week to spend. Those are the changes that turn the answer from "not yet" into "now".
Frequently asked questions
How much should a small business spend on help desk software?
There's no useful figure, because the seat floor moves the total far more than the headline rate does. Three things decide your actual bill: the minimum number of seats you must commit to, whether the plan you were shown is the one that includes reporting, and the platform license you're already paying for underneath. Where the gap between two per-seat prices is small, a twelve-seat minimum will cost an eight-person company more than the pricier plan with no minimum, so check the floor before you compare the rates. How the pricing models actually work goes through the rest of the mechanics.
Do I need a technical person to manage help desk software?
Answering mail in one of these tools isn't a technical job, so for daily use, no. Connecting it is a different matter: somebody has to hold a privileged administrator role on your mail platform to authorize the connection, and on Microsoft 365 the documentation asks you to keep that role rare. Decide who that person is before the trial, not during it.
How long does it take to set up a help desk system?
Connecting it to your mail takes an afternoon. Configuring it takes weeks of somebody's spare attention: categories, routing, canned replies, business hours, then a second pass after the first set of decisions turns out to be wrong. Vendors quote the first number, so budget for the second.
Can help desk software replace my business email?
No, and that's the good news. These tools work through a connection to the mailbox you already have, so your provider, your domain and your customer-facing address all stay where they are. What changes is what happens to a message after it arrives.
Can I switch help desk platforms later?
Technically yes, commercially perhaps not until renewal. The license commitment is the constraint, and the platform vendors document it themselves: you generally can't reduce a committed count mid-term. Before signing, ask what an export of your conversation history actually contains and in what format, since that's the other half of the exit and the half nobody checks. The numbers worth measuring before any trial will at least tell you whether a switch achieved anything.
What is the difference between a help desk and a CRM?
A help desk holds the request; a CRM holds the relationship, meaning the company, the deal and the history of who spoke to whom about what. They overlap because both store contacts, which is how small businesses sometimes buy the second expecting the first and end up with an excellent contact database that nobody answers mail from. If your problem is unanswered messages, the help desk is the one you want.