Help desk: when a small team needs one, and how to cope before then

A help desk is the single place people bring problems — customers reporting something broken, or colleagues who cannot print. Its job is to make sure every request is seen, owned by somebody, and either resolved or explicitly closed. Software is one way to do that and not the only one, which is the part most comparison articles skip.

The honest framing for a small business is a threshold question rather than a product question. Below a certain volume, a shared mailbox with three agreed rules outperforms a help desk system, because the tool costs setup time and discipline that the volume does not justify. Above it, the mailbox starts silently dropping people, and by the time you notice, the ones who gave up are not there to tell you.

Signs you have outgrown a shared mailbox

• Two people reply to the same message, or nobody does because each assumed the other had.
• You cannot answer how many requests came in last month, or how long they took.
• The same question arrives weekly and gets answered from scratch every time.
• Something was missed and there is no way to find out when, or whether it happened before.
• Coverage depends on one person, and their holiday is visibly a risk.
• You need to tell a customer where their request stands and have to search a mailbox to find out.

One or two of these is manageable. Four is a system you have already outgrown, and the cost of not moving is invisible — it lands as churn rather than as a complaint.

Running support well before you buy anything

1. One address, published, that everyone uses. Requests arriving in five different inboxes cannot be managed by any method.
2. An owner per request, assigned the moment it arrives rather than by whoever feels responsible.
3. Three states only: new, waiting on us, waiting on them. Elaborate status schemes are where small teams lose to their own process.
4. A response-time promise you can actually keep, stated publicly. A slower promise met beats a fast one missed.
5. A written answer to every question you have answered twice, kept somewhere both the team and customers can reach.
6. A weekly ten-minute look at what came in. This is where the pattern shows up, and the pattern is usually worth more than the individual fixes.

The most valuable output of a help desk is not the resolved requests — it is the list of what people keep asking. Five recurring questions almost always point to a product problem, a confusing page or a missing document, and fixing the cause removes the requests entirely. Teams that only measure resolution speed get faster at answering questions that should never have been asked.

Help desk, service desk, ticketing system

The terms are used interchangeably in marketing and mean slightly different things in practice. A help desk fixes problems — something is broken, make it work. A service desk is broader, covering requests as well as faults, and is the vocabulary used inside IT operations. A ticketing system is the underlying mechanism any of them run on. For a business under fifty people the distinction rarely matters; it becomes real when the volume of requests that are not faults — access, equipment, onboarding — starts to exceed the faults.

Where Ettex fits, and where it does not

Being direct: we do not make a help desk. Ettex Chat is a team messaging product, not a customer support platform, and there is no ticket queue, no service level tracking, no customer portal and no live chat widget. If you have concluded from the list above that you need a help desk, buy one — the category is mature and inexpensive.

What Ettex covers is the surrounding work. The recurring answers belong in Ettex Docs where both the team and customers can be pointed at them; the intake form for a structured request in Ettex Forms; the customer context in Ettex CRM. The shape of a good request is covered separately in support ticket, and measuring whether people are satisfied afterwards in customer satisfaction score.