# Customer support, feedback and product glossary

> Definitions of support, feedback and product terms, each with its own page.

Source: https://quackback.io/glossary

- [Acceptance Criteria](https://quackback.io/glossary/acceptance-criteria.md): Acceptance criteria are the specific conditions that a user story or feature must satisfy to be considered complete. They define the boundaries of a feature in testable terms, ensuring the development team and product owner agree on what "done" means. Well-written acceptance criteria prevent scope creep and reduce rework by making expectations explicit before development begins.
- [AI Copilot for Support](https://quackback.io/glossary/ai-copilot.md): An AI copilot is an assistant that works beside a support agent rather than talking to customers. It drafts replies, summarizes long conversations, answers the agent's questions from internal knowledge and rewrites messages, while the agent decides what to send.
- [AI Support Agent](https://quackback.io/glossary/ai-support-agent.md): 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. Unlike a scripted chatbot, it writes each answer from your content.
- [Backlog Grooming](https://quackback.io/glossary/backlog-grooming.md): Backlog grooming (also called backlog refinement) is the recurring practice of reviewing, updating, and prioritizing items in a product backlog. During grooming sessions, the team adds detail to upcoming stories, removes obsolete items, re-estimates effort, and reorders based on new information. It keeps the backlog healthy and sprint-ready.
- [Business Hours (Office Hours)](https://quackback.io/glossary/business-hours.md): Business hours, or office hours, are the times your support team is working, set per timezone with holidays excluded. Help desks use them to pause SLA clocks outside working time and to tell customers when to expect a reply.
- [Changelog](https://quackback.io/glossary/changelog.md): A changelog is a chronological record of product updates, new features, bug fixes, and improvements shared with users. It serves as both a communication tool and a historical reference for what has changed in a product over time. Well-maintained changelogs keep users informed, demonstrate momentum, and close the feedback loop by showing that user input leads to real product changes.
- [Churn Rate](https://quackback.io/glossary/churn-rate.md): Churn rate is the percentage of customers who stop using a product or cancel their subscription within a given time period. It is calculated by dividing the number of customers lost during the period by the number at the start. A high churn rate signals product-market fit problems, unmet user needs, or competitive pressure that requires immediate attention.
- [Closed-Loop Feedback](https://quackback.io/glossary/closed-loop-feedback.md): Closed-loop feedback is the practice of following up with customers after they provide feedback to let them know what action was taken. It completes the feedback cycle by connecting input to outcome. Most companies collect feedback. Few close the loop. Teams that do see higher satisfaction, stronger retention, and more willingness from customers to share future input.
- [Continuous Discovery](https://quackback.io/glossary/continuous-discovery.md): 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. It involves weekly customer touchpoints, structured opportunity mapping, and rapid assumption testing. The goal is to maintain a constant flow of user insight that informs every sprint.
- [Customer Advisory Board](https://quackback.io/glossary/customer-advisory-board.md): A customer advisory board (CAB) is a selected group of customers who provide strategic feedback on product direction, market trends, and company decisions. Unlike open feedback channels, a CAB offers curated, in-depth input from your most engaged or representative customers. It builds stronger relationships while giving the product team high-quality directional signals.
- [Customer Effort Score](https://quackback.io/glossary/customer-effort-score.md): 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. It is typically captured through a post-interaction survey asking users to rate their agreement with a statement like "the company made it easy for me to handle my issue." Lower effort correlates strongly with customer loyalty and repeat purchases.
- [Customer Experience](https://quackback.io/glossary/customer-experience.md): Customer experience (CX) is the total perception a customer forms about a brand based on every interaction across the entire relationship. It spans marketing, sales, onboarding, product usage, and support. CX is shaped by both deliberate design choices and the gaps between them. Companies that treat CX as a system rather than a department consistently outperform on retention and growth.
- [Customer Feedback Loop](https://quackback.io/glossary/customer-feedback-loop.md): 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. Closing the loop is what separates companies that listen from companies that just collect data. It turns feedback into a relationship-building mechanism.
- [Customer Retention](https://quackback.io/glossary/customer-retention.md): Customer retention is the ability of a company to keep its existing customers over a given period. It measures how many customers continue using and paying for a product rather than leaving for a competitor or canceling entirely. Retention is driven by product value, customer experience, and the ongoing match between what users need and what you deliver.
- [Customer Satisfaction](https://quackback.io/glossary/customer-satisfaction.md): Customer satisfaction (CSAT) measures how well a product or service meets customer expectations. It is typically assessed through post-interaction surveys where users rate their experience on a scale. Common satisfaction metrics include CSAT scores, Net Promoter Score, and Customer Effort Score. High satisfaction correlates with retention, expansion revenue, and positive word of mouth.
- [Definition of Done](https://quackback.io/glossary/definition-of-done.md): A definition of done (DoD) is a shared checklist of criteria that a product increment must meet before the team considers it complete. It typically includes code quality standards, testing requirements, documentation, and deployment readiness. For user-requested features, the DoD should also verify that the original user problem is actually solved.
- [Digital Suggestion Box](https://quackback.io/glossary/digital-suggestion-box.md): A digital suggestion box is an online tool that replaces the physical suggestion box with a structured feedback collection system. It allows users, customers, or employees to submit ideas, feature requests, and improvement suggestions through a web interface. Modern digital suggestion boxes include voting, categorization, and status tracking, evolving into full feedback management platforms.
- [Dual-Track Agile](https://quackback.io/glossary/dual-track-agile.md): Dual-track agile is a development approach where discovery and delivery run as parallel tracks within the same team. The discovery track focuses on understanding user problems and validating solutions. The delivery track builds and ships validated features. Both tracks operate continuously, with discovery feeding a stream of de-risked ideas into the delivery backlog.
- [Feature Parity](https://quackback.io/glossary/feature-parity.md): Feature parity means matching the functionality of a competing product or an existing version of your own product. Teams pursue feature parity during platform migrations, product rewrites, or when entering a market with established competitors. It is a strategic choice that balances meeting baseline expectations with the risk of building a copycat product instead of innovating.
- [Feature Prioritization](https://quackback.io/glossary/feature-prioritization.md): Feature prioritization is the process of deciding which features to build first based on impact, effort, user demand, and strategic fit. It uses structured frameworks like RICE, ICE, and MoSCoW to replace gut-feel decisions with repeatable scoring methods. Effective prioritization connects customer feedback data directly to development planning so teams build what users actually need.
- [Feature Request](https://quackback.io/glossary/feature-request.md): A feature request is a user suggestion for new functionality or an improvement to an existing product. Feature requests represent raw demand signals from the people who use your product daily. Feedback tools organize, deduplicate, and rank these requests so product teams can identify patterns and prioritize what to build next based on real user needs rather than internal assumptions.
- [Feature Voting](https://quackback.io/glossary/feature-voting.md): Feature voting is a mechanism that lets users upvote feature requests to signal demand. It transforms qualitative feedback into quantitative data by showing exactly how many people want a specific capability. Voting surfaces the features with the broadest user appeal and gives product teams a defensible way to prioritize their roadmap based on actual user demand rather than guesswork.
- [Feedback Board](https://quackback.io/glossary/feedback-board.md): A feedback board is a public or private forum where users submit, discuss, and vote on product feedback. It acts as a structured channel between a product team and its users, replacing scattered emails and support tickets with a single visible space. Feedback boards organize suggestions by status and popularity, making it easy to see what users want most and what the team is working on.
- [First Contact Resolution](https://quackback.io/glossary/first-contact-resolution.md): First contact resolution (FCR) is the share of customer issues resolved in the first interaction, with no follow-up, transfer or reopen needed. A high FCR usually means agents have the knowledge and authority to solve problems on the spot.
- [First Response Time](https://quackback.io/glossary/first-response-time.md): First response time (FRT) is how long a customer waits between sending a support request and getting the first reply from a person. It is usually reported as a median, in business hours, and it is one of the strongest drivers of customer satisfaction.
- [Help Desk](https://quackback.io/glossary/help-desk.md): 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. Most help desks combine a shared inbox, ticketing, saved replies, SLAs and reporting.
- [Human Handoff](https://quackback.io/glossary/human-handoff.md): 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. A clear handoff is the most important safety net in AI support.
- [ICE Framework](https://quackback.io/glossary/ice-framework.md): The ICE framework is a lightweight scoring model for prioritizing features and experiments. Each item is rated on three dimensions: Impact (how much it moves a key metric), Confidence (how certain you are in the estimate), and Ease (how simple it is to implement). ICE trades the granularity of RICE for speed, making it ideal for teams that need quick prioritization decisions without extensive data.
- [Idea Management](https://quackback.io/glossary/idea-management.md): Idea management is the systematic process of collecting, evaluating, and implementing ideas from users, employees, or stakeholders. It goes beyond simple suggestion collection by adding structure for scoring, prioritizing, and tracking ideas through a pipeline from submission to delivery. Effective idea management connects user creativity to product execution.
- [Impact Mapping](https://quackback.io/glossary/impact-mapping.md): Impact mapping is a strategic planning technique that connects business goals to deliverables through a structured map. It works backward from a goal to identify actors (who can influence the outcome), impacts (how their behavior needs to change), and deliverables (what the team can build to create that change). It prevents teams from building features that do not connect to outcomes.
- [Incident Communication](https://quackback.io/glossary/incident-communication.md): Incident communication is how a company keeps customers informed while something is broken: acknowledging the problem, posting regular updates, and explaining the fix afterwards. Done well, it protects trust even when the outage itself can't be avoided.
- [Internal Notes](https://quackback.io/glossary/internal-notes.md): Internal notes are messages inside a support conversation that only your team can see. Agents use them to share context, ask a colleague for help with an @mention, or record what was tried, without the customer seeing it.
- [Jobs to Be Done](https://quackback.io/glossary/jobs-to-be-done.md): Jobs to Be Done (JTBD) is a framework for understanding why customers buy or use a product. Instead of focusing on demographics or features, JTBD asks what "job" the customer is trying to accomplish. A job is the progress a person seeks in a specific circumstance. Products succeed when they help customers complete their jobs better than alternatives.
- [Kano Model](https://quackback.io/glossary/kano-model.md): The Kano model is a framework for classifying product features based on their relationship to customer satisfaction. It defines five categories: must-be (expected basics), one-dimensional (more is better), attractive (unexpected delighters), indifferent (no impact), and reverse (actively unwanted). The model helps teams balance investments between table-stakes functionality and differentiating features.
- [Knowledge Base](https://quackback.io/glossary/knowledge-base.md): A knowledge base is a searchable library of help articles that answers customer questions without a support conversation. A public knowledge base is usually published as a help center; an internal one gives agents approved answers to reuse.
- [Live Chat Support](https://quackback.io/glossary/live-chat.md): Live chat support lets customers message your team in real time from a chat window on your website or inside your product. It is the fastest support channel for customers, and it works best with clear availability, quick routing and an AI or self-service layer for simple questions.
- [Macros (Saved Replies)](https://quackback.io/glossary/macros.md): A macro is a saved reply that an agent inserts with one click, often with placeholders for the customer's name and other details. Many help desks let a macro also run actions, such as tagging, assigning or closing the conversation.
- [MCP (Model Context Protocol)](https://quackback.io/glossary/model-context-protocol.md): The Model Context Protocol (MCP) is an open standard for connecting AI assistants to the tools and data they need. An MCP server exposes actions, such as searching feedback or replying to a conversation, that any MCP-compatible client, like Claude or Cursor, can call with the user's permission.
- [MoSCoW Method](https://quackback.io/glossary/moscow-method.md): 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). It is widely used in agile and project management to set clear expectations about scope and delivery.
- [Multilingual Customer Support](https://quackback.io/glossary/multilingual-support.md): Multilingual customer support means helping customers in their own language across chat, email and self-service. Teams do it with native-speaking agents, translated help content, and increasingly with AI translation of conversations in both directions.
- [Net Promoter Score](https://quackback.io/glossary/net-promoter-score.md): 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. Those scoring 9-10 are promoters, 7-8 are passives, and 0-6 are detractors. NPS is calculated by subtracting the percentage of detractors from the percentage of promoters, yielding a score between -100 and +100.
- [North Star Metric](https://quackback.io/glossary/north-star-metric.md): A north star metric is the single metric that best captures the core value your product delivers to customers. It aligns every team around one measurable outcome that reflects real user value, not just business revenue. The right north star metric correlates with long-term growth because it measures whether users are getting what they came for.
- [Product Backlog](https://quackback.io/glossary/product-backlog.md): A product backlog is an ordered list of everything a product team believes it needs to build, fix, or improve. It serves as the single source of work for the development team and is continuously refined as user feedback, market conditions, and business goals evolve. The product owner maintains the backlog and decides priority.
- [Product Discovery](https://quackback.io/glossary/product-discovery.md): Product discovery is the process of deciding what to build before committing engineering resources. It involves understanding user problems, generating solutions, and testing assumptions through prototypes and experiments. The goal is to reduce risk by validating that a solution is valuable, usable, feasible, and viable before full development begins.
- [Product Operations](https://quackback.io/glossary/product-operations.md): Product operations (product ops) is a function that supports product managers by streamlining processes, managing tools, and surfacing data. Product ops teams handle the operational work that enables PMs to focus on strategy and discovery. They standardize how feedback is collected, how experiments are tracked, and how insights flow between teams.
- [Product Strategy](https://quackback.io/glossary/product-strategy.md): Product strategy is the high-level plan that connects your product vision to execution. It defines who your target users are, what problems you solve for them, how you differentiate from competitors, and what outcomes you aim to achieve. A strong product strategy turns user feedback and market insight into a focused roadmap instead of a scattered list of features.
- [Product-Market Fit](https://quackback.io/glossary/product-market-fit.md): Product-market fit is the point where a product satisfies strong market demand. It means you have found a group of users who need what you have built and are willing to pay for it, recommend it, or depend on it. Measuring product-market fit requires combining quantitative signals like retention and NPS with qualitative feedback about why users stay or leave.
- [Public Roadmap](https://quackback.io/glossary/public-roadmap.md): A public roadmap is a product roadmap shared externally with customers, showing planned, in-progress, and completed features. It gives users visibility into what the team is building and why. Public roadmaps build trust by demonstrating that user feedback influences product direction. They also reduce inbound support questions about when specific features will ship.
- [Release Notes](https://quackback.io/glossary/release-notes.md): Release notes are documentation that describes the changes, improvements, and fixes included in a software release. They inform users about what is new, what has changed, and what has been fixed. Well-written release notes close the feedback loop by showing users that their requests were heard and acted upon, building trust and encouraging continued engagement.
- [Resolution Time](https://quackback.io/glossary/resolution-time.md): 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. It is usually reported as a median in business hours, alongside first response time.
- [Retrieval-Augmented Generation (RAG)](https://quackback.io/glossary/retrieval-augmented-generation.md): Retrieval-augmented generation (RAG) is a way of making an AI model answer from your own content. The system first searches your sources for relevant passages, then asks the model to write an answer using only those passages, usually with citations.
- [RICE Framework](https://quackback.io/glossary/rice-framework.md): The RICE framework is a quantitative scoring model for prioritizing features and projects. It evaluates each item on four dimensions: Reach (how many users it affects), Impact (how much it moves a key metric), Confidence (how certain you are in your estimates), and Effort (how much time it takes to build). The formula produces a single score that enables objective comparison across competing ideas.
- [Round-Robin Assignment](https://quackback.io/glossary/round-robin-assignment.md): Round-robin assignment hands new support conversations to each available agent in turn, so work is spread evenly across the team. Load-balanced assignment is a variant that gives the next conversation to whoever has the fewest open ones.
- [Self-Service Support](https://quackback.io/glossary/self-service.md): 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. It resolves simple questions faster for the customer and leaves your agents more time for the hard ones.
- [Shared Inbox](https://quackback.io/glossary/shared-inbox.md): A shared inbox is one queue of customer conversations that a whole team works from, with each conversation assigned to an owner. It replaces a shared email login or a forwarding alias, so nothing is answered twice and nothing is missed.
- [SLA (Service Level Agreement)](https://quackback.io/glossary/service-level-agreement.md): 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. SLAs can be promised in a contract or set internally, and they are usually measured in business hours.
- [SLA Breach](https://quackback.io/glossary/sla-breach.md): 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. Teams track breaches to find staffing and routing gaps, and act on approaching breaches before they happen.
- [Sprint Planning](https://quackback.io/glossary/sprint-planning.md): Sprint planning is the agile ceremony where the team decides what work to commit to in the upcoming sprint. The product owner presents prioritized backlog items, the team discusses scope and feasibility, and together they agree on a sprint goal. Effective sprint planning connects user feedback to concrete development commitments within a fixed timebox.
- [Status Page](https://quackback.io/glossary/status-page.md): 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. Customers check it, or subscribe to it, instead of contacting support during an outage.
- [Support Automation](https://quackback.io/glossary/support-automation.md): 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. It keeps agents on the work that needs judgment.
- [Ticket Deflection](https://quackback.io/glossary/ticket-deflection.md): 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. A high deflection rate means your team spends its time on the questions that need a person.
- [Ticket Escalation](https://quackback.io/glossary/ticket-escalation.md): Ticket escalation moves a support issue to someone with more expertise or authority, such as a senior agent, a specialist team or engineering. Clear escalation paths stop customers bouncing between teams and keep the original agent informed.
- [Ticket Routing](https://quackback.io/glossary/ticket-routing.md): 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. Good routing gets each conversation to someone who can solve it, without a manual triage step.
- [Ticketing System](https://quackback.io/glossary/ticketing-system.md): 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. It is how support teams manage work that takes longer than a single reply.
- [Tracker Ticket (Problem Ticket)](https://quackback.io/glossary/tracker-ticket.md): A tracker ticket, sometimes called a problem ticket, groups many customer tickets caused by the same underlying issue. The team works the problem once, and updating the tracker updates every linked customer ticket.
- [User Story](https://quackback.io/glossary/user-story.md): 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. User stories keep development teams focused on delivering value rather than completing tasks.
- [Value Hypothesis](https://quackback.io/glossary/value-hypothesis.md): A value hypothesis is a testable assumption about why customers will use your product. It states the specific value a user will receive and the evidence that would prove or disprove it. Validating the value hypothesis early prevents teams from building products that work technically but fail to solve a real problem users care about.
- [Voice of the Customer](https://quackback.io/glossary/voice-of-the-customer.md): Voice of the Customer (VoC) is a research methodology for capturing customer needs, expectations, and preferences. It involves collecting feedback through surveys, interviews, support interactions, and feedback boards, then analyzing that data to understand what customers truly value. VoC programs turn scattered user input into structured insights that drive product, marketing, and support decisions.
