Glossary
Customer support, feedback and product glossary
68 customer support, AI, feedback and product management terms, each defined in plain language with how to put it into practice.
A
Acceptance Criteria
Acceptance criteria are the specific conditions that a user story or feature must satisfy to be considered complete.
AI Copilot for Support
An AI copilot is an assistant that works beside a support agent rather than talking to customers.
AI Support Agent
An AI support agent is a language model that answers customer questions in a support channel, using your help articles and other approved sources, and hands the conversation to a person when it can't help.
B
Backlog Grooming
Backlog grooming (also called backlog refinement) is the recurring practice of reviewing, updating, and prioritizing items in a product backlog.
Business Hours (Office Hours)
Business hours, or office hours, are the times your support team is working, set per timezone with holidays excluded.
C
Changelog
A changelog is a chronological record of product updates, new features, bug fixes, and improvements shared with users.
Churn Rate
Churn rate is the percentage of customers who stop using a product or cancel their subscription within a given time period.
Closed-Loop Feedback
Closed-loop feedback is the practice of following up with customers after they provide feedback to let them know what action was taken.
Continuous Discovery
Continuous discovery is the practice of regularly talking to users and incorporating their feedback into product decisions, rather than doing research only at the start of a project.
Customer Advisory Board
A customer advisory board (CAB) is a selected group of customers who provide strategic feedback on product direction, market trends, and company decisions.
Customer Effort Score
Customer Effort Score (CES) is a metric that measures how easy it is for customers to accomplish a specific task with your product or support team.
Customer Experience
Customer experience (CX) is the total perception a customer forms about a brand based on every interaction across the entire relationship.
Customer Feedback Loop
A customer feedback loop is the continuous cycle of collecting feedback from users, analyzing it for patterns, acting on the insights by building or improving features, and then communicating those changes back to the users who provided the input.
Customer Retention
Customer retention is the ability of a company to keep its existing customers over a given period.
Customer Satisfaction
Customer satisfaction (CSAT) measures how well a product or service meets customer expectations.
D
Definition of Done
A definition of done (DoD) is a shared checklist of criteria that a product increment must meet before the team considers it complete.
Digital Suggestion Box
A digital suggestion box is an online tool that replaces the physical suggestion box with a structured feedback collection system.
Dual-Track Agile
Dual-track agile is a development approach where discovery and delivery run as parallel tracks within the same team.
F
Feature Parity
Feature parity means matching the functionality of a competing product or an existing version of your own product.
Feature Prioritization
Feature prioritization is the process of deciding which features to build first based on impact, effort, user demand, and strategic fit.
Feature Request
A feature request is a user suggestion for new functionality or an improvement to an existing product.
Feature Voting
Feature voting is a mechanism that lets users upvote feature requests to signal demand.
Feedback Board
A feedback board is a public or private forum where users submit, discuss, and vote on product feedback.
First Contact Resolution
First contact resolution (FCR) is the share of customer issues resolved in the first interaction, with no follow-up, transfer or reopen needed.
First Response Time
First response time (FRT) is how long a customer waits between sending a support request and getting the first reply from a person.
H
Help Desk
A help desk is software that collects customer support requests from every channel into one queue, so a team can assign them, answer them, track them to resolution and measure how well it is doing.
Human Handoff
Human handoff is the moment an AI agent or chatbot passes a customer conversation to a person, ideally with a summary of what has happened so the customer doesn't have to repeat themselves.
I
ICE Framework
The ICE framework is a lightweight scoring model for prioritizing features and experiments.
Idea Management
Idea management is the systematic process of collecting, evaluating, and implementing ideas from users, employees, or stakeholders.
Impact Mapping
Impact mapping is a strategic planning technique that connects business goals to deliverables through a structured map.
Incident Communication
Incident communication is how a company keeps customers informed while something is broken: acknowledging the problem, posting regular updates, and explaining the fix afterwards.
Internal Notes
Internal notes are messages inside a support conversation that only your team can see.
J
Jobs to Be Done
Jobs to Be Done (JTBD) is a framework for understanding why customers buy or use a product.
K
Kano Model
The Kano model is a framework for classifying product features based on their relationship to customer satisfaction.
Knowledge Base
A knowledge base is a searchable library of help articles that answers customer questions without a support conversation.
L
Live Chat Support
Live chat support lets customers message your team in real time from a chat window on your website or inside your product.
M
Macros (Saved Replies)
A macro is a saved reply that an agent inserts with one click, often with placeholders for the customer's name and other details.
MCP (Model Context Protocol)
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to the tools and data they need.
MoSCoW Method
The MoSCoW method is a prioritization technique that sorts requirements into four categories: Must have (critical for launch), Should have (important but not essential), Could have (desirable if time permits), and Won't have (explicitly excluded for now).
Multilingual Customer Support
Multilingual customer support means helping customers in their own language across chat, email and self-service.
N
Net Promoter Score
Net Promoter Score (NPS) is a customer loyalty metric based on a single question: "How likely are you to recommend this product to a friend or colleague?" Respondents answer on a 0-10 scale.
North Star Metric
A north star metric is the single metric that best captures the core value your product delivers to customers.
P
Product Backlog
A product backlog is an ordered list of everything a product team believes it needs to build, fix, or improve.
Product Discovery
Product discovery is the process of deciding what to build before committing engineering resources.
Product Operations
Product operations (product ops) is a function that supports product managers by streamlining processes, managing tools, and surfacing data.
Product Strategy
Product strategy is the high-level plan that connects your product vision to execution.
Product-Market Fit
Product-market fit is the point where a product satisfies strong market demand.
Public Roadmap
A public roadmap is a product roadmap shared externally with customers, showing planned, in-progress, and completed features.
R
Release Notes
Release notes are documentation that describes the changes, improvements, and fixes included in a software release.
Resolution Time
Resolution time is how long it takes to fully resolve a customer's issue, from the first message until the conversation or ticket is closed.
Retrieval-Augmented Generation (RAG)
Retrieval-augmented generation (RAG) is a way of making an AI model answer from your own content.
RICE Framework
The RICE framework is a quantitative scoring model for prioritizing features and projects.
Round-Robin Assignment
Round-robin assignment hands new support conversations to each available agent in turn, so work is spread evenly across the team.
S
Self-Service Support
Self-service support lets customers find answers and fix problems without contacting your team, through a help center, in-app help, AI answers or a community.
Shared Inbox
A shared inbox is one queue of customer conversations that a whole team works from, with each conversation assigned to an owner.
SLA (Service Level Agreement)
In customer support, an SLA (service level agreement) is a set of time targets a team commits to, such as how quickly a customer gets a first reply and how quickly the issue is resolved.
SLA Breach
An SLA breach happens when a support conversation or ticket misses a target in its service level agreement, such as the first response or resolution deadline.
Sprint Planning
Sprint planning is the agile ceremony where the team decides what work to commit to in the upcoming sprint.
Status Page
A status page is a public web page that shows whether a service and its components are working, lists current incidents and scheduled maintenance, and keeps a history of past uptime.
Support Automation
Support automation uses rules and AI to handle repeatable support work without an agent: routing new conversations, applying SLAs, sending replies outside hours, asking for ratings, and closing idle threads.
T
Ticket Deflection
Ticket deflection is the share of customer questions resolved through self-service, such as help articles, AI answers or a status page, instead of reaching an agent.
Ticket Escalation
Ticket escalation moves a support issue to someone with more expertise or authority, such as a senior agent, a specialist team or engineering.
Ticket Routing
Ticket routing is the set of rules that decides which team or agent receives a new support conversation, based on things like channel, topic, customer or language.
Ticketing System
A ticketing system tracks each customer issue as a ticket with an ID, an owner, a status and a history, from the first report until it is resolved.
Tracker Ticket (Problem Ticket)
A tracker ticket, sometimes called a problem ticket, groups many customer tickets caused by the same underlying issue.
U
User Story
A user story is a short description of a feature written from the end user's perspective, typically following the format "As a [user], I want [goal], so that [benefit]." It captures what a user needs and why, without prescribing how to build it.
V
Value Hypothesis
A value hypothesis is a testable assumption about why customers will use your product.
Voice of the Customer
Voice of the Customer (VoC) is a research methodology for capturing customer needs, expectations, and preferences.