Most teams adopt a help desk the week after something went wrong in a shared mailbox. Knowing what the parts are for makes it much easier to choose one well.
The ticket is the unit of work
A ticket is the record of one request: who asked, what they asked, every message exchanged since, every internal note, and every change to its status, priority or owner. Everything else in a help desk exists to move tickets from new to resolved, quickly and in the right order.
The ticket number is the thing a customer quotes on the phone; the ticket's history is the thing a new agent reads when they inherit it. Both only work if every message about the request lands on the same ticket - which is why threading, the matching of replies to tickets, matters far more than it looks.
Statuses say whose turn it is
A good status model answers one question at a glance: is this waiting on us, or on someone else? New and Open mean the desk owes a reply. Waiting on customer means the ball is in their court. Resolved and Closed mean the work is done.
Statuses also drive measurement. The clock that measures your response time should pause while you wait on the customer, and keep running while you wait on a colleague. A status model that lets agents park awkward tickets somewhere the clock stops will produce flattering reports and unhappy customers.
Routing and queues
Routing decides where a new ticket goes before anyone reads it: by the address it was sent to, the customer's company, its category, its priority. Round-robin spreads work evenly within a team.
Views - awaiting my reply, unassigned in my team, at risk of breaching - replace the single unread count of a mailbox with lists that tell each person what to do next.
Service-level agreements
An SLA is a promise with a deadline: a first response within four business hours, a resolution within three business days. The help desk starts a clock for each target when the ticket arrives, pauses it while the customer has the ball, warns before the deadline, and escalates if it is missed.
Business hours matter. A target measured on a 24-hour clock is either impossible overnight or meaningless during the day.
The customer portal
A portal lets customers see their open requests, read replies and respond without searching their inbox. It reduces "any update?" emails and gives a client's colleagues visibility of requests they were copied on.
The non-negotiable property of a portal is that it shows customers only what was sent to them - never internal notes, never drafts.
How a help desk differs from similar tools
A shared inbox lets several people read one mailbox but has no owner, status or deadline per conversation. A CRM tracks the commercial relationship - deals, pipeline, accounts - and is weak at queues and SLAs. An ITSM platform adds IT-specific processes such as asset, change and problem management on top of a help desk.
- Shared inbox: shared access, no ownership or deadlines.
- CRM: relationships and revenue, not queues.
- ITSM: a help desk plus IT processes - assets, changes, problems.
- Help desk: requests, ownership, deadlines and customer communication.
Controls on what is sent
Most help desks control who can see a ticket. Fewer control what can be sent from one. For teams where a reply can create an obligation - refunds, regulated wording, legal commitments - a maker-checker step, where certain replies need a second person's approval before they leave, is the control that matters most.
SupaDesk builds this in as rule-based reply approval. Whatever tool you choose, ask how it would stop a reply that should not be sent, and how it would prove who approved one that was.