Customer Satisfaction Score
Customer Satisfaction Score (CSAT) in Salesforce is a post-interaction survey metric that measures how satisfied customers are with the support, service, or experience they received.
Definition
Customer Satisfaction Score (CSAT) in Salesforce is a post-interaction survey metric that measures how satisfied customers are with the support, service, or experience they received. The standard pattern is to send a short survey (one question, sometimes two or three) after a Case is closed, asking the customer to rate their experience on a numeric or smiley-face scale, and to compute CSAT as the percentage of responses at the top of the scale.
CSAT is one of three customer-experience metrics that most service organizations track. Net Promoter Score (NPS) measures advocacy intent on a 0-to-10 scale. Customer Effort Score (CES) measures how much work the customer had to do. CSAT measures immediate satisfaction. Salesforce Service Cloud supports all three through Surveys (the standard product) or third-party survey tools (Qualtrics, SurveyMonkey, Medallia) integrated through APIs. The CSAT score lands back on the Case record and rolls up into Service Cloud dashboards and Service Analytics.
How CSAT is measured in Salesforce
The survey send and response cycle
The typical flow: a Case closes, a Flow on the Case triggers a Salesforce Surveys send (or a third-party survey tool send), the customer receives an email with a single CSAT question, the customer clicks a rating, and the response writes back to a Survey Response record linked to the Case. The Case CSAT field updates from the response, and downstream dashboards aggregate the data.
Scale choice: 1-5, 1-10, smiley faces
Different CSAT implementations use different scales. The most common is a 5-point scale where 4 and 5 count as satisfied. Some use 1-10 with 9 and 10 as satisfied. Some use 3-emoji surveys (sad, neutral, happy) for mobile-first audiences. The math changes per scale; CSAT is always percentage of top-of-scale responses divided by total responses. Pick one and stick to it; mid-program scale changes break time-series comparisons.
Salesforce Surveys: the native option
Salesforce Surveys is the platform-native survey tool. It supports rating questions, multiple-choice, free-text, and conditional logic. Responses are stored in Survey Response records linked to the originating Case, Account, or any custom object. CSAT calculations can run as formula fields on Case (Case.CSAT__c = Survey Response.Rating) or aggregate across many responses through reports.
Third-party CSAT tools and how they integrate
Many service organizations use Qualtrics, SurveyMonkey, Medallia, Delighted, or Wootric instead of Salesforce Surveys. The reasons vary: richer survey logic, better mobile UX, multi-channel delivery (email, SMS, in-app), or pre-existing enterprise contracts. These tools integrate with Salesforce through managed packages or custom APIs; CSAT writes back to a Case custom field or a Survey Response object.
Reporting and benchmarking
CSAT reports are the foundation of service operations dashboards. Common cuts: CSAT by agent (identify high and low performers), CSAT by Case Reason (which issue types frustrate customers most), CSAT by region or segment (geographic and demographic patterns), and CSAT time series (trend by month or quarter). Industry benchmarks vary; B2B SaaS support typically targets 85 to 95 percent CSAT, retail support 75 to 85 percent.
Tying CSAT to coaching and compensation
Many service organizations tie agent CSAT scores to performance reviews and compensation. This is operationally sensitive: agents who handle harder cases naturally score lower, so raw CSAT comparisons can be unfair. Mature programs normalize CSAT by case complexity (number of touches, escalation, resolution time) or use a peer comparison rather than absolute thresholds.
Response rates and self-selection bias
CSAT response rates typically run 5 to 20 percent. The customers who respond are not representative of all customers; respondents skew toward strongly positive or strongly negative experiences (the satisfied middle does not bother). Mature CSAT programs adjust for self-selection bias and pair CSAT with operational metrics (first-contact resolution, average handle time) for a fuller picture.
How to set up a CSAT program in Salesforce
Setting up CSAT in Salesforce takes a few steps: configure a survey tool, build a Flow to trigger sends, store responses on the Case, and build dashboards. The data pipeline is straightforward; the operational discipline of acting on results is harder.
- Pick a survey tool
Salesforce Surveys (native, lower cost) or a third-party tool (Qualtrics, SurveyMonkey, Medallia, Delighted). Pick based on existing tooling, feature requirements, and budget.
- Design the CSAT survey
One question on a clear scale. Resist the temptation to add five more questions; longer surveys kill response rates. The single question should map directly to CSAT (How would you rate your experience).
- Build the trigger Flow
Create a record-triggered Flow on Case that fires when Status changes to Closed. The Flow sends the survey through the chosen tool. Add a delay of 1 to 24 hours after close to let the customer reflect.
- Store responses on the Case
Configure the survey tool to write back to a Case custom field (CSAT_Rating__c) and the survey response object. This is what dashboards aggregate.
- Build CSAT dashboards
Service Cloud Service Analytics has pre-built CSAT dashboards. Customize for your team. At minimum: overall CSAT, CSAT by agent, CSAT by Case Reason, CSAT time series.
- Operationalize the responses
Build a Flow that flags low-CSAT cases for manager review. Train managers to follow up with both the agent and the customer. CSAT data is only useful if someone acts on it.
- Response rates of 5 to 20 percent are normal. Self-selection bias is real; do not draw conclusions from small samples.
- Mid-program scale changes (1-5 to 1-10, or text to emoji) break time-series. Pick a scale up front and stick with it.
- Tying CSAT to compensation without normalizing for case complexity is unfair to agents handling harder cases.
- Survey fatigue affects response rates. If a customer files 10 cases in a month and gets 10 surveys, they ignore all of them. Cap survey frequency per customer.
- CSAT data has a delay (24 hours to weeks). Real-time dashboards on CSAT lag the source events; account for the lag when interpreting trends.
Trust & references
Cross-checked against the following references.
- Salesforce Surveys OverviewSalesforce Help
- Service Analytics OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Customer Satisfaction Score.
- Cases OverviewSalesforce Help
- Flow OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does CSAT measure?
Q2. How is CSAT typically calculated?
Q3. What's the difference between CSAT and NPS?
Discussion
Loading discussion…