Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesA help desk is the function or system a support team uses to record, route, and resolve customer or employee questions, problems, and service requests. The terms below explain how requests move through support, what common service metrics measure, and how a help desk relates to a service desk and IT service management (ITSM). Labels and metric rules can differ by organization and software, so platform-specific definitions should not be treated as universal standards.
Help desk, service desk, and ITSM
Help desk
A help desk is a central function or system for assisting customers or employees with questions, issues, and service requests. It commonly records requests and helps the team prioritize and resolve them. Support may be delivered through channels such as email, phone, chat, text, and self-service. Salesforce describes the help desk as often focused on responding to reported issues; organizations may use the term differently. Salesforce’s help desk explainer
As an Amazon Associate I earn from qualifying purchases.
Service desk
In Salesforce’s framing, a service desk is a broader IT support function that handles incidents and more general IT demands while connecting support with organizational service needs. Some companies use “help desk” and “service desk” interchangeably, so the name alone does not establish the team’s scope.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteITSM
IT service management, or ITSM, is the broader approach to structuring, delivering, and improving IT services. A help desk or service desk may be one part of an ITSM operation; ITSM is not simply another name for the support queue.
#1 Best Overall
Requests, people, and workflow
Ticket or support request
A ticket is a tracked record of a customer’s or employee’s issue or request and the work done to handle it. A ticket can preserve its conversation and status as it moves between people or teams. The fields and workflow depend on the organization’s software and configuration.
Agent
An agent is a support worker who handles or contributes to requests. Platforms may assign agents different roles and permissions; Zendesk’s glossary, for example, describes role distinctions within its own product. Zendesk glossary
Assignment and group
Assignment directs a ticket to an individual agent or a team. In Zendesk terminology, a group collects agents and can be used in ticket workflows. Other platforms may use different labels or structures.
Priority
Priority signals a request’s relative urgency or importance so the team can handle it according to policy. Do not assume that every system uses the same scale, levels, or criteria: one team’s “high” priority may not mean the same thing as another’s.
Routing
Routing directs an incoming request to a queue, group, or agent. Rules may take account of the channel, issue type, or team responsibilities, but the available methods are product- and configuration-specific.
Rank #2
Escalation
Escalation moves a request to a specialist, a higher support tier, or a decision-maker when the current handler cannot resolve it or policy calls for additional attention. Zendesk also uses “agent escalation” for transferring an automated conversation to a live agent; that is a particular product usage, not the only meaning of escalation.
Status
A ticket’s status indicates where it sits in the workflow. Status names and the events that change them depend on the platform and team rules; a status label should be read in the context of that system rather than assumed to have one industry-wide definition.
Response, resolution, and service targets
First response time or first reply time
First response time (FRT) describes how long it takes to send an initial qualifying response. Zendesk defines its “first reply time” as the minutes from ticket creation to the first public agent comment. That product definition does not automatically describe every organization’s reporting: the start event, what counts as a reply, and whether the clock uses business hours can vary. Zendesk’s definition of first reply time
Resolution time
Resolution time measures elapsed time until a request is considered resolved under the team’s chosen rules. The start event, resolution event, operating hours, and treatment of pauses affect what the number means. Zendesk documents multiple time-based metrics, so reports should be interpreted using the exact field definition in the platform. Zendesk Support metrics and attributes
Requester wait time
Requester wait time is a platform metric for time attributed to waiting for the requester. The precise clock behavior is specific to the product and its configuration; do not infer it from the name alone.
Rank #3
SLA, target, achieved, and breached
A service-level agreement (SLA) or service target states a commitment for handling support work. A system may track targets for first reply, next reply, requester wait, agent work, or total resolution. Which hours count and whether a clock pauses depend on the team’s policy and configuration.
“Achieved” or “breached” indicates whether a configured target was met for the relevant ticket and metric. A breach is evidence that the particular target was missed; by itself, it does not establish that the entire support relationship failed. Zendesk’s metrics documentation describes platform-specific SLA attributes and timing measures.
First-contact resolution and customer feedback
FCR or first contact resolution
First contact resolution (FCR), also called first call resolution, is the proportion of issues fully resolved during the first interaction. The label “first call” can be misleading when support also happens over chat, email, or a portal: a team should define whether “first” means the first phone call or the first interaction across channels.
For a consistent calculation, the team must define what counts as an issue, a completed resolution, and a first interaction. It should also decide whether a later follow-up, callback, escalation, or reopening means the issue was not resolved on first contact. Atlassian notes that unclear definitions can distort FCR comparisons. Atlassian’s FCR explainer
CSAT
Customer satisfaction (CSAT) is a rating or survey measure associated with a support interaction. Zendesk records ticket satisfaction ratings, but there is no single scale or formula established here as universal. When reporting CSAT, explain the survey question, response scale, and which interactions are included; otherwise, figures from different teams may not be comparable. Salesforce’s ITSM metrics overview
Self-service and persistent messaging
Help center
A help center is a customer-facing self-service portal that may combine a knowledge base, community, and request portal. It gives customers another way to find information or submit a request; visiting or searching a help center is not, by itself, proof that a problem has been resolved.
Knowledge base
A knowledge base is the collection of official support content within a help center. Zendesk describes its knowledge base as organized into articles, sections, and categories. The exact structure and publishing controls vary across products.
Messaging
In Zendesk’s terminology, messaging is a persistent conversation channel that retains context and history and can be available through a website, help center, or app. This is a vendor-defined description; other products may use “messaging” differently. Zendesk glossary
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to read support metrics without misreading them
Metrics answer different questions. FRT concerns the initial response; resolution time concerns elapsed time to a defined resolution; requester wait time attributes time to waiting for the requester; CSAT captures a customer rating; and FCR concerns whether an issue was completely resolved during the first interaction. One measure cannot stand in for all the others.
Free tools Windows power users keep installed
One-click scans. No signup required.
Before comparing teams, periods, or channels, document the metric’s scope and rules:
- Events: State what starts and stops the clock, and what event qualifies as a response or resolution.
- Clock: Specify business hours or calendar time, holidays, pauses, and how requester waiting is treated.
- Channel: Clarify whether the measure covers phone alone or includes chat, email, portal, and other channels.
- FCR policy: Define how follow-ups, callbacks, escalation, and reopening affect first-contact resolution.
- Target scope: Name the SLA metric and ticket scope when reporting achievement or breach.
These distinctions matter because two dashboards can use similar metric names while measuring different events or clocks. Zendesk’s documentation is useful for understanding Zendesk fields, while Atlassian’s FCR guidance explains the definition problem; neither should be read as a universal rulebook for every help desk.
Choosing help-desk terminology for a team
Agree on the operational meaning before adopting a label or comparing results. For a small customer-support team, a useful glossary should say what qualifies as a ticket, who can own or reassign it, how priority is set, when a request is escalated, and what event marks resolution. If the team reports service performance, add the clock and channel rules for each metric. If it offers self-service, distinguish an article view or portal visit from a resolved issue.
When assessing support software, compare the channels it supports, ticket workflow, self-service and knowledge-base capabilities, reporting definitions, configuration, and integrations against the team’s actual needs. The terminology and examples in product documentation explain that vendor’s features; they do not establish an independent ranking or a universal feature set.
Recommended Free Tools
Frequently Asked Questions
Is first response time the same as resolution time?
No. First response time ends at a qualifying initial reply, while resolution time ends at the team-defined resolution event. Each measure has its own clock rules.
Does an SLA breach mean the support team failed overall?
Not necessarily. It means a specific configured target was missed for the relevant ticket and metric; the target, scope, and clock rules determine what that status signifies.
Does a help center visit count as a resolution?
Not on its own. A help center provides self-service resources or a way to submit a request, but a visit or search does not establish that the issue was solved.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
