Help Desk & Contact Center Glossary: 55 Terms Every Support Team Should Know
55 help desk and contact center terms explained in plain language, from SLA and AHT to occupancy rate and skill-based routing, with links to deeper guides on each one where they exist on this site.
Last updated: 2026-09-16
Why this glossary exists
Across the other 122 Help Desk, Call Center, and Contact Center guides on this site, we routinely use terms like SLA, occupancy rate, or skill-based routing without stopping to redefine them in every article. This page collects the roughly 55 terms that come up most often in one place, grouped by what they actually describe: metrics a team reports on, the mechanics inside a ticketing tool, how contacts get routed between channels, how a contact center staffs and scores itself, and the business terms that show up on a vendor's pricing page.
Each definition below is written the way we would explain it to someone joining a support team for the first time, not the way a vendor's own glossary phrases it to sound more impressive than the underlying idea. Where a term connects to a deeper guide already on this site, such as the full formula and benchmarks behind AHT and FCR, the definition links straight to it instead of repeating a shortened version here.
Core support metrics
| Term | What it means |
|---|---|
| SLA (Service Level Agreement) | A commitment, often contractual, that spells out how fast a team will first respond to and fully resolve a request, usually split by ticket priority so a critical outage gets a faster clock than a general question. |
| First Response Time (FRT) | The time between a customer submitting a ticket and an agent's first reply. Most SLA policies set a separate, shorter target for this than for full resolution. |
| First Contact Resolution (FCR) | Whether a request gets solved during the very first interaction, with no follow-up needed. See our Average Handle Time and First Call Resolution guide for the formula and 2026 benchmarks by industry. |
| One Contact Resolution (OCR) | A stricter version of FCR used in call center benchmarking: it only counts an issue as resolved if the customer never reaches out again on any channel, not just the one they started on. Not to be confused with optical character recognition, the document-scanning technology that shares the same initials. |
| Average Handle Time (AHT) | How long an agent spends on one contact, added up across talk time, hold time, and after-call wrap-up work. A shorter AHT is not automatically better; see the guide above for what happens when a team optimizes it without also watching FCR. |
| Customer Satisfaction Score (CSAT) | A post-interaction rating, usually a 1-5 scale, asking whether the customer was happy with that specific ticket or call. It measures a single moment, not the overall relationship. Our customer satisfaction survey questions guide covers how to phrase the question itself. |
| Net Promoter Score (NPS) | A single 0-10 “how likely are you to recommend us” question, sorted into promoters (9-10), passives (7-8), and detractors (0-6). The score is the percentage of promoters minus the percentage of detractors, so it can run anywhere from -100 to 100. See our best NPS software roundup. |
| Customer Effort Score (CES) | Asks how easy, not how happy, a customer found the process of getting an issue resolved. High effort predicts churn even when CSAT looks fine, since someone can be satisfied with the outcome and still frustrated they needed three channels to get there. |
| Backlog | Every ticket that is open and unresolved at a given moment, regardless of whether it is currently breaching an SLA. A growing backlog with a stable SLA-breach rate usually means volume is outpacing headcount before it shows up as a service failure. |
| Ticket Volume | The raw count of tickets created in a given period. On its own it says nothing about whether a team is coping; pair it with backlog and AHT before drawing conclusions. |
| Resolution Time | The full time from ticket creation to close, as opposed to first response time. This is the number most SLA policies actually enforce as the customer-facing promise. |
Ticketing and workflow terms
| Term | What it means |
|---|---|
| Ticket | The record a help desk creates for one customer request, tracked from open to closed with a full history of every reply, internal note, and status change attached to it. |
| Ticket Status | The stage a ticket sits in (open, pending, on hold, solved, closed). “Pending” typically means waiting on the customer and stops the SLA clock in most tools; “on hold” usually means waiting on an internal team and keeps the clock running. |
| Priority vs. Severity | Priority is how urgently a ticket needs attention relative to everything else in the queue; severity is how serious the underlying problem actually is. A high-severity bug affecting one customer might carry lower priority than a low-severity billing question from an enterprise account about to renew. |
| Macro / Canned Response | A pre-written reply template an agent can insert with one click, then edit before sending. Cuts response time on repetitive questions but erodes trust fast if agents send it unedited to a question it does not quite fit. |
| Trigger / Business Rule / Automation | A trigger fires immediately when a ticket meets a condition, such as a new ticket from a VIP tag routing to a senior agent. A business rule runs on a schedule instead of an event, such as nudging any ticket untouched for 24 hours. “Automation” is the umbrella term most vendors use for both. |
| Escalation | Moving a ticket to a more senior agent, a different team, or a higher support tier, usually because the front-line agent lacks the access, expertise, or authority to resolve it. |
| Merge / Split Ticket | Merging combines duplicate tickets from the same customer about the same issue into one thread. Splitting breaks one ticket covering several unrelated requests into separate tickets so each can be tracked and closed on its own timeline. |
| Tag | A label attached to a ticket for filtering and reporting, such as “billing,” “bug,” or “churn-risk.” Unlike category, most help desks let one ticket carry several tags at once. |
| SLA Policy | The configured rule set inside a help desk that defines response and resolution targets by priority level, and triggers alerts or escalations when a ticket is at risk of breaching one. |
| Business Hours | The window during which SLA clocks run. A ticket submitted at 9pm against a 9-to-5 SLA does not start its response-time clock until the next business day, which is a common source of “why did this breach” confusion. |
| Queue | A holding area for tickets waiting to be picked up, usually filtered by channel, product, priority, or team, so agents pull from the queue that matches what they are equipped to handle. |
Routing, channels, and self-service terms
| Term | What it means |
|---|---|
| Round-Robin Routing | New tickets get assigned to agents in a fixed rotating order, regardless of what each agent is currently working on. Simple to configure, but it can hand a five-minute question to an agent who is mid-way through a 45-minute case. |
| Skill-Based Routing | Tickets get matched to agents based on tagged skills, language, product expertise, or certification, rather than a plain rotation. Needs a maintained skills taxonomy to work well, and drifts out of date if nobody owns it. |
| Omnichannel vs. Multichannel | Multichannel means a company offers several channels, such as email, chat, and phone, that operate as separate silos. Omnichannel means those channels share one customer and conversation history, so an agent on a phone call can see the chat that same customer had yesterday. Our multi-channel customer support software guide covers what actually delivers the omnichannel version versus what only claims to. |
| Shared Inbox | A single inbox multiple agents can see and reply from, built on top of email, without the ticketing structure, SLAs, automations, and reporting, that a full help desk adds. See our shared inbox vs. help desk breakdown for when a shared inbox stops being enough. |
| Unified Inbox | A single screen that pulls tickets from multiple channels, email, chat, social, into one queue, so an agent is not switching between separate tools per channel. |
| Interactive Voice Response (IVR) | The automated phone menu, “press 1 for billing,” that routes a caller before a human ever picks up. |
| Automatic Call Distributor (ACD) | The system behind an IVR that actually routes an incoming call to a specific queue or agent based on rules, distinct from the menu the caller hears. |
| Chatbot / Conversational AI | A chatbot follows scripted decision trees with a fixed set of possible replies. Conversational AI generates responses dynamically from a knowledge base or model, and can handle a question its designer never explicitly anticipated. See our AI customer support software guide for what “AI” actually means across current vendors. |
| Co-Browsing | An agent and customer view, and sometimes control, the same browser session together in real time, used for walking someone through a form or settings page rather than describing it over chat. |
| Knowledge Base | A self-service library of help articles a customer can search before, or instead of, contacting support. See our best knowledge base software roundup. |
| Deflection Rate | The percentage of potential contacts resolved through self-service, a knowledge base article or a chatbot, instead of reaching an agent. A rising deflection rate only counts as a win if CSAT on the deflected path holds up too. |
| Live Chat | Real-time, synchronous text conversation on a website, as opposed to asynchronous email or ticket-based support. See our best live chat software roundup. |
Contact center operations terms
| Term | What it means |
|---|---|
| Occupancy Rate | The percentage of an agent's logged-in time spent actively handling contacts, including after-call work, versus sitting idle waiting for the next one. High occupancy sounds efficient but leaves no slack for volume spikes. |
| Shrinkage | The percentage of an agent's paid time that is unavailable for taking contacts at all: breaks, training, meetings, coaching sessions, absenteeism. A staffing plan that ignores shrinkage will always look understaffed once it meets a real schedule. See our call center workforce management software guide for how forecasting tools account for it. |
| Service Level | The industry's standard way of expressing how quickly calls get answered, phrased as “X% of calls answered within Y seconds”, an “80/20” service level means 80% of calls answered within 20 seconds. Distinct from average speed of answer, which is a mean rather than a threshold. |
| Average Speed of Answer (ASA) | The average time a caller waits in queue before reaching an agent, expressed as a single mean number rather than the threshold-based service level above. |
| Abandon Rate | The percentage of callers who hang up before reaching an agent, usually tracked alongside ASA since long queue times are the main driver. |
| Predictive Dialer | An outbound dialing system that calls multiple numbers per available agent, predicting when someone will answer and when an agent will free up, to minimize agent idle time between calls. Carries real compliance exposure; see our predictive dialer and call abandonment compliance guide. |
| Workforce Management (WFM) | The discipline, and the software category, covering forecasting of contact volume and scheduling the right number of agents with the right skills to meet it. See our contact center scheduling software guide. |
| QA Scorecard | A rubric with weighted categories, such as greeting, accuracy, tone, and compliance, a reviewer uses to score a recorded call or chat transcript, producing a consistent quality number instead of a subjective impression. |
| Calibration Session | A recurring meeting where multiple QA reviewers score the same recorded interaction independently, then compare and reconcile scores, to keep scoring consistent across reviewers over time. See our contact center QA software guide for tools built around this workflow. |
| Tier 1 / Tier 2 / Tier 3 Support | Escalation levels by complexity. Tier 1 handles common, scripted issues; Tier 2 handles problems that need deeper product knowledge or account access; Tier 3 usually means engineering or specialist involvement for issues that are effectively bugs or edge cases. |
Software and business model terms
| Term | What it means |
|---|---|
| Per-Agent / Per-Seat Pricing | A SaaS billing model charging a fixed monthly fee per named agent or logged-in seat, regardless of how many tickets that agent handles. The most common model among the help desks covered on this site. |
| Usage-Based Pricing | Billing tied to volume, tickets, contacts, or, with several AI copilots, resolutions, rather than headcount. A common add-on structure for AI features layered on top of a per-agent base plan. |
| Freemium | A permanently free tier with a real feature or seat cap, distinct from a time-limited free trial that expires. Vendors have been shrinking or removing freemium tiers across this category over the past two years, so check whether a “free plan” mentioned in an older guide still exists before relying on it. |
| White-Labeling | Reselling a vendor's software under a different company's own branding, with no visible trace of the original vendor. Relevant mainly to agencies and BPOs offering support-as-a-service under their own name. |
| API | A defined way for one piece of software to read or write data in another, letting a help desk sync tickets with a CRM or a custom internal tool without a human copying data between the two. |
| Webhook | A one-way notification an app sends automatically the moment something happens, such as a ticket closing or a tag getting applied, letting another system react without repeatedly polling for changes. |
| Integration | A pre-built connection between a help desk and another tool, a CRM, a phone system, a chat app, that a team turns on rather than builds from scratch against a raw API. |
| Help Desk vs. ITSM | A help desk is built for customer-facing support tickets. IT service management (ITSM) tools apply a more formal, ITIL-derived process, incident, problem, and change management, to internal IT requests. The line has blurred as help desks add ITSM features, but the underlying process rigor still differs. |
| Business Process Outsourcing (BPO) | A third-party company that runs support operations on a client's behalf, often across multiple clients from the same physical or virtual floor, as opposed to an in-house team employed directly by the company whose product they support. |
| In-House vs. Outsourced Support | In-house agents work directly for the company and typically develop deeper product knowledge over time. Outsourced agents, via a BPO, usually cost less per hour but require more upfront training investment and process documentation to reach the same quality bar. See our customer service outsourcing cost guide for real pricing. |
| Data Migration | Moving tickets, contacts, and knowledge base content from one help desk to another, usually the easy part of a platform switch. See our help desk software migration data guide for what does not transfer automatically and what a realistic timeline looks like. |
How to cite this glossary
Cite this page
CommsAdvisor. “Help Desk & Contact Center Glossary: 55 Terms Every Support Team Should Know.” Last updated September 16, 2026. https://commsadvisor.com/help-desk-contact-center-glossary/
Frequently asked questions
Is CSAT the same as NPS?
No. CSAT measures satisfaction with one specific interaction, right after it happens. NPS measures overall willingness to recommend the company based on the whole relationship. A customer can give a ticket a perfect CSAT score the same week an NPS survey rates the company poorly, if that one interaction went well but the broader relationship has not.
What is the actual difference between a help desk and a shared inbox?
A shared inbox is email multiple agents can see and reply from together. A help desk adds the structure a shared inbox does not have: SLA tracking, automations and triggers, tagging and reporting, and usually multi-channel support beyond email. See the shared inbox vs. help desk guide for exactly when a team outgrows the simpler tool.
Does a lower average handle time always mean a more efficient team?
No, and this is one of the more common misreadings of a support dashboard. A shorter AHT that comes with a falling first contact resolution rate usually means the same issue is generating repeat contacts instead of getting solved once. See the Average Handle Time and First Call Resolution guide for a real account of what that trade-off costs.
What does it mean when a ticket “breaches SLA”?
It means the ticket crossed its committed response or resolution time target before an agent addressed it. A well-configured help desk flags a ticket as at risk before the breach happens, not just after, so an agent or supervisor has a window to intervene.
Is first contact resolution the same benchmark across every industry?
No. A healthy FCR rate for a retail order-status line and a SaaS technical support queue are not the same number, because the underlying issues take different amounts of expertise to close on the first try. See the industry benchmark table in the Average Handle Time and First Call Resolution guide.