A leadership review opens with three metrics: NPS at 42, CSAT at 91 percent, CES at 4.8 out of 7. Everyone nods. Nobody can explain what they mean together because the surveys fired on different triggers, against different audiences, with different anchors. HubSpot makes all three easy to ship and easier to misuse.
What each one actually measures
- NPS (Net Promoter Score): “How likely are you to recommend us?” 0 to 10. Promoters minus detractors. Predicts referral and retention over 6 to 12 months.
- CSAT (Customer Satisfaction): “How satisfied were you with this interaction?” 1 to 5 or 1 to 7. Measures the moment.
- CES (Customer Effort Score): “How easy was it to get your issue resolved?” 1 to 7. Predicts churn better than CSAT for support touches.
Pick one per use case. Do not run NPS and CSAT against the same touch — you train customers to ignore both.
Trigger logic
Customer interaction -> Survey
First-time activation -> none (too early)
30 days post-onboarding complete -> NPS
Post-ticket close -> CES
Post-major release -> CSAT (product satisfaction)
Quarterly relationship -> NPS (rolling)
Set in Service Hub > Feedback Surveys. For ticket close triggers, configure the workflow to delay 24 hours so the customer rates the resolution, not the response.
Avoid the rolling sample bias
NPS quarterly waves capture seasonal customers. If your survey only fires when a customer logs in, you sample engaged users and miss the silent churn risk. Send to a rolling sample of all active customers, gated by minimum tenure (60 days):
Filter: Customer status = Active
Filter: Tenure days >= 60
Filter: Last NPS sent >= 90 days ago OR null
Sample: random 25% per month
Run it via an active list and a scheduled workflow.
Open-text follow-up is where the value lives
The score gives you the trend. The free text gives you the action. Configure follow-up questions:
NPS detractor (0-6): "What's the main reason for your score?"
NPS passive (7-8): "What would have made this a 9 or 10?"
NPS promoter (9-10): "What do we do better than alternatives?"
Pipe responses into a tagged list. Tag taxonomy: pricing, product gap, support quality, onboarding, integration, other. Review monthly with product and CS leadership.
Closing the loop with workflow
Detractor responses without follow-up are insulting. Auto-create a task for the CSM within 24 hours:
// Workflow: NPS response received, score <= 6
await hsClient.crm.objects.tasks.basicApi.create({
properties: {
hs_task_subject: `Detractor follow-up: ${contact.firstname} ${contact.lastname}`,
hs_task_body: `NPS ${response.score}. Reason: ${response.comment}`,
hs_task_priority: "HIGH",
hubspot_owner_id: contact.csm_owner_id,
hs_timestamp: Date.now() + 24 * 3600 * 1000
}
});
return { outputFields: { task_created: true } };
Reporting calibrated against benchmark
Industry NPS benchmarks vary wildly: SaaS software 30s, telecom single digits, luxury retail 70s. Reporting your number against last quarter’s number teaches you whether you moved. Reporting against an industry benchmark teaches you whether you are competitive. Track both.
Surveys you do not run
A “bonus” question tacked onto every survey halves response rate. Cap NPS at score plus one open-text. Cap CES at one rating plus optional comment. Long surveys signal you do not respect the customer’s time, which is itself the data point you were trying to capture.
What to do this week
Map each customer touchpoint to one survey type, retire any survey that fires more than once per quarter against the same audience, and configure detractor follow-up tasks before next month’s CSAT review.