Help Desk Software Glossary and Key Terms
The help desk vocabulary in plain words, written for buyers. Each term defined, and where it maps to cost or a specific tier, we say so.
The help desk vocabulary, in plain words
Help desk buying gets harder when vendors and reviewers use the same words to mean different things. This glossary defines the terms that actually affect your decision, written for a buyer rather than a vendor. Where a term maps to cost or to a specific tier, we say so, because in help desk software the language of support is often the language of upsell.
Use it alongside our how to choose and pricing guides, where these terms do the real work of separating tools.
Glossary of help desk terms that matter
Software that gathers customer requests from channels like email, chat, and phone into one shared workspace, then gives agents the tools to track, route, and resolve them as tickets.
A single tracked request with a status, owner, and full history. The ticket is the unit of work in a help desk, and almost every report and SLA is measured against it.
An agent is a person who answers tickets; a seat is the paid license that lets them log in. Most help desks charge per seat, per month, so seat count is the main driver of cost.
A teammate who can read tickets and add internal notes but not reply to customers, usually free or low cost. Useful for engineers or managers who assist without needing a full seat.
A team mailbox where every agent sees the same queue, with assignment and collision detection so two people do not answer the same message. The lightest form of help desk, favored by tools like Help Scout and Front.
A promised response or resolution time, such as first reply within four business hours. SLA tracking and breach alerts are common buying triggers and are often gated to higher tiers.
A reusable response, and sometimes a set of actions, that an agent applies in one click. Often called a canned response. The fastest way to keep answers consistent across a team.
Rules that act on a ticket when a condition is met, such as tagging, assigning, or escalating without manual effort. Depth of automation is a frequent reason to move up a plan.
How tickets reach the right agent. Round robin spreads work evenly; skills based routing sends tickets to agents with the matching expertise. Skills based routing is typically a higher tier feature.
One workspace that handles email, live chat, social, and phone together, so an agent sees the full history regardless of channel. Full omnichannel is usually a mid or upper tier feature.
A library of articles customers can read to solve problems on their own. A strong help center deflects tickets before they reach an agent, which is where help desks earn their keep.
A signal that another agent is already viewing or replying to a ticket, so two people do not send duplicate answers. Small in name, large in saved embarrassment on busy queues.
CSAT is a customer satisfaction score gathered after a ticket closes. First response time is how long a customer waits for a first human reply. The two metrics most teams watch first.
Automated assistants that suggest replies, summarize tickets, or answer common questions without a human. Often sold as a paid add on or reserved for upper tiers, so price the AI separately.
An alternative to per seat pricing where the bill scales with monthly ticket or conversation volume rather than agent count. Used by tools like Gorgias, and a better fit for high volume ecommerce teams.
An integration connects the help desk to other tools, such as a CRM, an ecommerce platform, or billing. An API lets developers build their own connections; integration depth is a top buying factor.
Where the vocabulary meets the bill
A general map of which help desk concepts unlock at which class of plan as of June 2026. Exact gating differs by vendor; check the vendor for current packaging and pricing.
A help desk is software that collects customer requests from channels like email, chat, and phone into tickets, then gives agents the tools to track, route, and resolve them in one shared place.
A ticket is a single tracked request with a status and history. A conversation is the back and forth inside it. Some tools, such as Gorgias, bill by ticket or conversation volume rather than purely by agent seat, so the distinction can affect cost.
SLA management, skills based routing, automation and triggers, AI agents, and advanced reporting are the features most often gated to higher tiers. Knowing which you truly need tells you the tier to budget for. Check the vendor for current packaging.
One email when the rankings move. The shortlist, the tradeoffs, the price changes. No filler.