If you can't understand ``what customers are feeling'' numerically, you won't be able to prioritize improvements, predict the risk of cancellation, or know the direction of product development.Each of the three metrics, NPS, CSAT, and CES, answers different questions—simultaneously tracking “long-term relationships,” “quality of individualized attention,” and “process friction.”For the first time, a complete picture of the customer experience can be seen. This chapter systematically explains the definition and usage of the three indicators, survey design, workflow coordination, analysis and improvement actions, and the mechanism for delivering VoC to Sales and Product.
Although the three indicators are often confused, they are completely different in what they measure.NPS is the strength of the relationship, CSAT is the quality of the response, and CES is the ease of the process.Measure. If used incorrectly, data will accumulate that cannot answer the correct questions. First, let's understand the definition of each indicator, how to calculate it, and the optimal timing for distribution.
| index | Optimal delivery timing | Estimated response rate | Target score (BtoB SaaS) |
|---|---|---|---|
| NPS | 30 days after initial ticket close / Every 90-180 days thereafter / 60 days before renewal | 15〜30% | Aim for +30 or more |
| CSAT | Within 1-4 hours after ticket close / After onboarding is completed | 20〜35% | 85% or more (percentage of satisfied/very satisfied) |
| CES | After closing a ticket with multiple interactions / After a self-service experience | 15〜25% | Average score 3.0 or less (on a 7-point scale) |
Suddenly distributing NPS, CSAT, and CES simultaneously will cause response fatigue and reduce the response rate for all indicators.Start with CSAT——CSAT after a ticket is closed is easy to operate and has a high immediate effect. A step-by-step approach that adds NPS once CSAT stabilizes and introduces CES once process improvement discussions become active will increase retention rates.
The golden rule for surveys is to keep the questions short, timely, and relevant to the context. Long surveys reduce response rates, and off-timing surveys lead to memory fading and inaccurate responses.HubSpot's survey function (setting location: Service → Feedback Survey) allows you to create, distribute, and aggregate three types: NPS, CSAT, and CES.。
Simply sending out surveys and looking at the results will not increase customer satisfaction.Create a system that automatically takes follow-up actions the moment a low score is received.maximizes the value of the feedback program. HubSpot allows you to set up a workflow that is triggered by "submitting feedback" and can perform different automatic actions depending on the score.
① Create a new one under Automation → Workflow → “Contact Base”. ② Trigger: Set to “Send feedback → Select survey name → Score is below 〇”. ③ Action: Combine "Create task", "Send internal email" and "Update properties". ④ Important:Be sure to include the setting "Do not run this workflow again within X days"CSAT achievement rate
Don’t just react to individual scores;Periodically analyze trends in aggregated data and lead to system-level improvements.is the original purpose of a feedback program. By combining HubSpot's feedback analysis tab with custom reports, you can identify which categories, people, and processes are reducing customer satisfaction.
Feedback data is not just for the CS team.``What customers are dissatisfied with'' is directly connected to the Product team's roadmap, ``What customers are evaluating'' is directly connected to the sales team's proposal talk, and ``signs that the customer is thinking of canceling'' is directly connected to AE update response.. Designing a mechanism to deliver VoC collected through Service Hub to the entire organization increases the strategic value of the support team.
| Delivery destination | Delivery content | frequency | Implementation method |
|---|---|---|---|
| Sales（AE） | Customer list with updated NPS/CSAT score trends, detractor flag, and "cancellation risk" properties of assigned customers | Weekly (every Monday) | Automatically send HubSpot reports via email / Automatically post to Slack #sales-csalert channel |
| Product | Top 10 feature requests extracted from free descriptions of feedback - Function names with the most mentions of being "difficult to use" - Categories of causes of CES deterioration | Monthly (1st Monday) | CS leader creates monthly report → Post to Notion / Confluence → Product Announced regularly |
| Marketing | Excerpts from comments from NPS recommenders (9 to 10 points), list of case study candidates, and frequently used keywords for “reasons for recommending” | monthly | List contacts with NPS score 9-10 and free text → Share to Marketing |
| Management/company-wide | Monthly NPS/CSAT trend graph/Monthly comparison/Detractor comment summary (anonymized)/Improvement action progress | Monthly (first company-wide meeting of the month) | Screen project HubSpot dashboard + share 1-page summary PDF to Slack |
In many organizations, support teams are considered "cost centers." butA team that can analyze hundreds of feedbacks per month and provide Product with customer insights that inform product improvements.is recognized by management as a strategic business partner. The VoC program is not only a measure to increase customer satisfaction, but also a measure to increase the CS team's presence within the organization. Establish a routine for presenting feedback summaries at monthly company-wide meetings.
NPS measures ``strength of relationships (long-term loyalty),'' CSAT measures ``quality of individualized response (immediate evaluation),'' and CES measures ``process friction (amount of effort).'' By designing a set of the three, you can see the entire picture of the customer experience. Start with CSAT and add more in stages.
Maximum number of questions is 3. Free writing is optional. Delivery to the same customer is limited to once a month. CSAT has the highest response rate 1-4 hours after the ticket is closed. NPS is standard 30 days after the first close and every 90 to 180 days thereafter.
CSAT2 or below → task to agent in charge, NPS critic → urgent task to manager. By setting up this workflow, the experience of ``I sent a criticism via survey and got a call the next day'' turns a critic into a promoter.
Rather than just tracking the overall CSAT average, analyze the breakdown by category, person in charge, and channel. The discovery that ``the CSAT of the technical defect category is low'' directly leads to specific improvement actions such as ``enhancing the technical KB and setting up a progress reporting workflow.''
Create a system to categorize the themes of critics' comments, count the number of feature requests, and summarize the cause categories of CES deterioration on a monthly basis and announce them on a regular product basis. When the CS team is recognized as a "source of information that contributes to product improvement," its presence within the organization increases.
Last content viewed date/viewed article