Customer support works best when teams can see both speed and outcomes. First response, resolution, and effort answer different questions; a low ticket count can still hide unresolved customer problems. Use clear definitions and pair operational targets with customer evidence.
🧭 Jump to a term
Customer experience and resolution: Customer satisfaction score (CSAT) · Customer effort score (CES) · Net Promoter Score (NPS) · First-contact resolution (FCR) · First response time · Resolution time
Workload and support operations: Average handle time (AHT) · Ticket backlog · Service-level agreement (SLA) · Helpdesk · Support macro · Escalation
Self-service and demand signals: Ticket deflection · Self-service support · Contact rate · Where is my order? (WISMO)
⭐ Know these first
Start with Customer satisfaction score (CSAT), First-contact resolution (FCR), First response time, Service-level agreement (SLA), Where is my order? (WISMO). Then follow the grouped learning order below.
📎 How to read this page
What it means gives the precise meaning. Operator translation gives the version you might hear in a real ecommerce meeting. In real life shows an illustrative example. Watch out and the confusion boxes show where a familiar term can mislead.
📈 Read the relationships first
These combinations are diagnostic hypotheses, not proof of causality. Compare the same period and scope, then investigate the mechanism.
Fast first response + long resolution time
Usually means: Means the customer heard back quickly but waited for a solution. Check next: handoffs, case complexity, and update cadence.
High first-contact resolution + low CSAT
Usually means: Can signal premature case closure or a poor experience despite no repeat contact. Check next: survey comments and reopen rates.
Low ticket volume + high WISMO elsewhere
Usually means: May mean tracking tools or contact routes are hiding demand. Check next: order-status visits and repeated contacts.
AHT falls + repeat contacts rise
Usually means: Can suggest agents are ending interactions before the issue is solved. Check next: quality and resolution together.
Customer experience and resolution
01 · 🟢 Core
Customer satisfaction score (CSAT) = Satisfaction rating after an interaction
🧠 What it means
A survey measure asking customers to rate their satisfaction with a specific interaction, product, or experience.
💬 OPERATOR TRANSLATION
“Did this interaction satisfy the customer, on the chosen scale?”
🛍️ In real life
A support team asks a short satisfaction question after an order issue is resolved.
⚠️ Report response rate, question wording, scale, and channel; survey respondents may not represent all customers.
🔗 Related: Customer effort score (CES) · Net Promoter Score (NPS) · First-contact resolution (FCR) · ↑ all terms
02 · 🔵 Operations
Customer effort score (CES) = Customer-reported effort to complete a task
🧠 What it means
A survey measure of how easy or difficult customers say it was to complete an interaction or task.
💬 OPERATOR TRANSLATION
“How much work did the customer feel they had to do?”
🛍️ In real life
After a return, a brand asks how easy it was to find instructions and complete the process.
⚠️ CES scales and direction vary; define which end means easier.
🔗 Related: Customer satisfaction score (CSAT) · Net Promoter Score (NPS) · First-contact resolution (FCR) · ↑ all terms
03 · 🔵 Operations
Net Promoter Score (NPS) = Promoters minus detractors share
🧠 What it means
A relationship or transactional survey score calculated as the percentage of promoters minus the percentage of detractors using a 0–10 likelihood-to-recommend question.
💬 OPERATOR TRANSLATION
“Subtract detractors from promoters; passives count in neither group.”
🛍️ In real life
A brand groups survey responses into detractors, passives, and promoters using the stated threshold.
⚠️ NPS is not a percentage of satisfied customers; explain survey timing and response bias.
🔗 Related: Customer satisfaction score (CSAT) · Customer effort score (CES) · First-contact resolution (FCR) · ↑ all terms
04 · 🟢 Core
First-contact resolution (FCR) = Issue solved in the initial contact
🧠 What it means
The share of support cases resolved during the first interaction without requiring a follow-up, using a defined case and repeat-contact window.
💬 OPERATOR TRANSLATION
“Did the customer get the issue solved without coming back?”
🛍️ In real life
A shopper's address-change request is completed in one chat with no later correction.
⚠️ Define what counts as a contact, resolution, and repeat within the window.
🔗 Related: Customer satisfaction score (CSAT) · Customer effort score (CES) · Net Promoter Score (NPS) · ↑ all terms
05 · 🟢 Core
First response time = Time until first human or automated reply
🧠 What it means
The elapsed time from a customer's support request to the first response, measured under a defined business-hours and channel policy.
💬 OPERATOR TRANSLATION
“How long before anyone replies the first time?”
🛍️ In real life
A ticket arrives at 9 a.m. and receives its first agent reply at 10 a.m.; first response time is one hour under elapsed-time reporting.
⚠️ Separate automated acknowledgement from substantive human response and calendar from business time.
🔗 Related: Customer satisfaction score (CSAT) · Customer effort score (CES) · Net Promoter Score (NPS) · ↑ all terms
06 · 🔵 Operations
Resolution time = Time until the request is considered resolved
🧠 What it means
The elapsed time between case creation and the point it meets the organization's resolution criteria.
💬 OPERATOR TRANSLATION
“How long did it take to solve the customer's issue?”
🛍️ In real life
A replacement case remains open until the replacement is shipped and the customer receives confirmation.
⚠️ Define resolution, reopened cases, pauses, and business-hour treatment consistently.
🔗 Related: Customer satisfaction score (CSAT) · Customer effort score (CES) · Net Promoter Score (NPS) · ↑ all terms
Workload and support operations
07 · 🔵 Operations
Average handle time (AHT) = Average agent time per interaction
🧠 What it means
The average time agents spend handling interactions, commonly including talk or chat time and after-contact work, as defined by the support operation.
💬 OPERATOR TRANSLATION
“Average time spent working each interaction under your team's formula.”
🛍️ In real life
A support team divides total handle minutes by handled contacts for the same period.
⚠️ Faster is not always better; pair AHT with quality and resolution measures.
🔗 Related: Ticket backlog · Service-level agreement (SLA) · Helpdesk · ↑ all terms
08 · 🔵 Operations
Ticket backlog = Open support cases awaiting work
🧠 What it means
The number or volume of customer support cases that remain unresolved or unprocessed at a point in time.
💬 OPERATOR TRANSLATION
“How many customer issues are still waiting in the queue?”
🛍️ In real life
A support lead tracks open cases by age, priority, and channel at the end of each day.
⚠️ Backlog count hides age and complexity; segment by urgency and case type.
🔗 Related: Average handle time (AHT) · Service-level agreement (SLA) · Helpdesk · ↑ all terms
09 · 🟢 Core
Service-level agreement (SLA) = Defined support service target
🧠 What it means
A documented service commitment that sets expected response or resolution targets and the conditions under which they apply.
💬 OPERATOR TRANSLATION
“The service target and rules that tell everyone what response to expect.”
🛍️ In real life
A business commits to respond to priority cases within a stated business-hours window.
⚠️ An SLA target is not the same as actual performance; publish scope and exclusions.
🔗 Related: Average handle time (AHT) · Ticket backlog · Helpdesk · ↑ all terms
10 · 🔵 Operations
Helpdesk = System for managing support requests
🧠 What it means
Software used to receive, organize, route, track, and report customer support requests.
💬 OPERATOR TRANSLATION
“The shared workbench where support requests are managed.”
🛍️ In real life
A helpdesk routes billing questions to one queue and shipping questions to another.
⚠️ A system organizes work; it does not guarantee a helpful answer.
🔗 Related: Average handle time (AHT) · Ticket backlog · Service-level agreement (SLA) · ↑ all terms
11 · 🔵 Operations
Support macro = Reusable response template
🧠 What it means
A saved message or response structure agents can use and adapt for recurring questions.
💬 OPERATOR TRANSLATION
“A starting answer that saves typing but still needs the customer's context.”
🛍️ In real life
An agent inserts a return-instructions macro and confirms the order's eligibility before sending.
⚠️ Review templates for accuracy, tone, and policy changes.
🔗 Related: Average handle time (AHT) · Ticket backlog · Service-level agreement (SLA) · ↑ all terms
12 · 🔵 Operations
Escalation = Routing a case to a higher-level or specialist owner
🧠 What it means
The transfer of a customer issue to a person or team with additional authority, expertise, or responsibility.
💬 OPERATOR TRANSLATION
“Move a case when the current owner cannot resolve it properly.”
🛍️ In real life
A suspected payment error is escalated to a specialist with access to transaction logs.
⚠️ Keep ownership visible and explain the handoff to the customer.
🔗 Related: Average handle time (AHT) · Ticket backlog · Service-level agreement (SLA) · ↑ all terms
Self-service and demand signals
13 · 🔵 Operations
Ticket deflection = Resolving need without opening a support ticket
🧠 What it means
A reduction or avoidance of support contacts when customers find a suitable answer through another channel, such as self-service content.
💬 OPERATOR TRANSLATION
“Help customers solve the issue without needing a ticket when that actually works.”
🛍️ In real life
A clear tracking page answers order-status questions before a customer contacts support.
⚠️ Fewer tickets do not prove customer success; check repeat contacts and satisfaction.
🔗 Related: Self-service support · Contact rate · Where is my order? (WISMO) · ↑ all terms
14 · 🔵 Operations
Self-service support = Customer-accessible help without an agent
🧠 What it means
Support tools or content that allow customers to find answers or complete tasks independently.
💬 OPERATOR TRANSLATION
“Let customers solve common issues on their own, with a clear path to an agent if needed.”
🛍️ In real life
A shopper uses a returns portal to request a label and check eligibility.
⚠️ Keep information current and make human support accessible for exceptions.
🔗 Related: Ticket deflection · Contact rate · Where is my order? (WISMO) · ↑ all terms
15 · 🔵 Operations
Contact rate = Support contacts relative to an order or customer base
🧠 What it means
A normalized measure of customer support contacts divided by a stated denominator such as orders, customers, or shipments.
💬 OPERATOR TRANSLATION
“How many support conversations occur per unit of business volume?”
🛍️ In real life
A store tracks support contacts per 100 orders to compare weeks with different sales volume.
⚠️ State the denominator and count repeat contacts consistently.
🔗 Related: Ticket deflection · Self-service support · Where is my order? (WISMO) · ↑ all terms
16 · 🟢 Core
Where is my order? (WISMO) = Order-status inquiry
🧠 What it means
A customer support contact asking for an order's current status, location, or expected delivery.
💬 OPERATOR TRANSLATION
“The customer cannot see where the order is or when it will arrive.”
🛍️ In real life
A shopper contacts support after the tracking page has not updated for several days.
⚠️ Address the underlying tracking, carrier, and expectation problem rather than only closing the ticket.
🔗 Related: Ticket deflection · Self-service support · Contact rate · ↑ all terms
🔀 First response vs resolution time
First response measures the wait for an initial reply. Resolution time runs until the issue meets the team’s resolution criteria.
🔀 CSAT vs CES vs NPS
CSAT asks about satisfaction, CES asks about effort, and NPS asks likelihood to recommend using a distinct scoring formula.
🔀 Ticket deflection vs customer success
Deflection means a contact did not become a ticket. Confirm the customer found a complete answer and did not return later.
🔀 SLA target vs actual performance
An SLA defines the expected service level. Actual response and resolution data show what customers experienced.
🤔 Still confused?
Follow this thread: Customer satisfaction score (CSAT) → Average handle time (AHT) → Ticket deflection. That sequence moves from the basic object or relationship to the decisions and checks it supports.
Sources and scope
Primary documentation checked on 27 September 2026. Platform features and eligibility can change; examples and cartoon situations are illustrative.
