Unlike NPS, which asks about the whole relationship, CSAT asks about a single moment. That tight focus is what makes it useful for routing, coaching, and catching churn risk one ticket at a time.
CSAT, or Customer Satisfaction Score, measures how satisfied a customer felt about one specific interaction, usually on a 1 to 5 or 1 to 7 scale. The formula is the number of satisfied responses divided by total responses, multiplied by 100. CSAT is transactional, tied to a touchpoint like a support ticket or an onboarding call, which makes it the fastest signal when something starts to break.
The five things to know before launching a CSAT program, and the one mistake that quietly makes every number you report meaningless.
CSAT is a short survey asked right after a specific interaction. One question, one scale, one moment. The scale is typically 1 to 5 or 1 to 7, and the question is some version of "how satisfied were you with your experience today?" That tight scope is the whole point.
CSAT equals the number of satisfied responses, divided by total responses, multiplied by 100. On a 1 to 5 scale, satisfied usually means a 4 or a 5. The result is a percentage. A CSAT of 85 means 85 percent of respondents picked a top-two box. The denominator is responses, not sends.
Fire the survey within minutes of the interaction closing, not days later. A support ticket resolution, an onboarding call, a first order shipped, a renewal signed. The response is a reaction to that specific event, which is why the survey has to arrive while the memory is still fresh.
CSAT is not NPS. It does not predict whether a customer will stay next year or recommend you to a peer. It tells you how one interaction landed. Confusing the two leads to the common failure of celebrating a high CSAT while churn climbs quietly in the background.
Most CSAT programs collect scores, drop them in a dashboard, and stop there. The number only earns its keep when a low score triggers a callback within 24 hours, a trend triggers a coaching session, and a pattern triggers a product fix. Without the action loop, CSAT is theatre.
A customer can be satisfied with a resolution and still exhausted by the effort it took to get there. CES, Customer Effort Score, catches the exhaustion. Running both on the same ticket surfaces the "satisfied but tired" segment that often churns next quarter, even though CSAT looked healthy.
The CSAT formula is simple enough to fit on an index card. The ways teams get it wrong are more interesting than the formula itself. Response rate, scale choice, top-box definition, and timing all change the number without changing the formula on paper. The six cards below cover the version almost every team uses and the common distortions to watch for.
CSAT percent equals satisfied responses divided by total responses, times 100. On a 1 to 5 scale, satisfied is a 4 or a 5. On a 1 to 7 scale, satisfied is usually a 6 or a 7. The scale choice matters: a 1 to 5 top-two-box reads differently than a 1 to 7 top-two-box, and benchmarks are not interchangeable between them.
Teams sometimes report CSAT as the mean score, which hides the pattern. A survey with half fives and half ones averages to a three, which looks mediocre. The top-two-box percentage would show two sharply split customer groups, which is the signal that matters. Report the percentage, not the average.
A 1 to 5 scale is quick and widely benchmarked. A 1 to 7 scale gives more resolution but is slightly harder to compare across industries. Five-star systems work for consumer brands. Whatever the scale, use the same one across every touchpoint, every quarter. Changing scales mid-year breaks the trend line.
If 100 tickets close and 10 customers respond, CSAT is calculated on 10, not 100. A high score on a 10 percent response rate is usually self-selection: happy customers answered, unhappy ones ignored the email. Track response rate alongside the score, and flag any segment where it drops below 20 percent.
The standard phrasing is some version of "how satisfied were you with your experience today?" Avoid wording that steers the answer, like "how great was our team?" or "how helpful was our fantastic support?" Primed questions produce inflated scores that quietly disconnect the number from reality.
Pair the scale with a single optional open-text field: "what is the one thing we could have done better?" The qualitative replies are where coaching material lives. Score alone is a trend. Score plus comments is a learning system. The comments are also what feed into product and policy changes later.
Teams routinely conflate CSAT, NPS, and CES, then wonder why the dashboards disagree. Each score answers a different question on a different cadence. The quick comparison below is the shortest honest version. Pick the right score for the moment, run the right one at the right trigger, and the three stop fighting each other.
How satisfied were you with this specific interaction? 1 to 5 or 1 to 7 scale. Fired at a touchpoint: ticket close, onboarding call, shipment delivered. Fast, local, actionable. Best for coaching individual reps, tuning a process, and catching a bad day before it compounds.
How likely are you to recommend us to a friend or colleague? 0 to 10 scale, calculated as promoters minus detractors. Fired quarterly or at renewal milestones, not after every interaction. Best for board-level trending, segment comparison, and connecting experience to growth over quarters.
How much effort did it take to get your issue resolved? Usually a 1 to 7 agreement scale. Fired after a resolution or a self-service attempt. The best leading indicator of churn in support contexts, because exhausted customers quietly leave even when they rate the resolution satisfactory.
CSAT fires on every closed interaction. CES fires on every resolution. NPS fires on a quarterly or milestone schedule, so the sample size stays comparable and the customer is not surveyed into fatigue. Three schedules, three audiences, three use cases. Run them in parallel, not in sequence.
CSAT predicts whether the next ticket from this customer will be easier or harder. NPS predicts whether the account will renew and whether it will refer new business. CES predicts whether the customer is building up quiet frustration that will show up as a cancellation six months out.
Use CSAT when you are tuning a touchpoint. Use CES when you are redesigning a workflow. Use NPS when you are reporting to a board or comparing segments across quarters. Picking the wrong score produces dashboards that look busy and signals that disagree with each other.
Benchmarks exist and are useful as rough calibration, but the honest answer is that your own trend line matters more than any industry average. Scoring 80 is only impressive if last quarter you scored 72. The six cards below are the ranges most practitioners cite, with the usual caveats about scale, response rate, and sample size.
Business software support tends to score in the high 70s to mid 80s. Onboarding touchpoints often score lower than renewal-stage touchpoints because expectations are still forming. Watch for the first-month dip, which is usually a product-education gap rather than a support quality problem.
Shipping, returns, and refund interactions skew high when the policy is generous and skew sharply when it is not. The split between order-related tickets and account-related tickets is wide enough that reporting one average hides more than it shows. Segment the view by ticket type.
Banking, insurance, and fintech typically run lower than other industries, because the resolution a customer wants (reversing a fee, approving a claim) is often not the resolution the business can offer. The useful signal is the trend inside the "policy denied" segment, not the headline average.
Hotels, restaurants, and travel brands score high on CSAT when the experience is in person, because the recovery options are rich. A bad meal becomes a comped dessert within minutes. The score hides the subset of interactions that never got the in-person recovery chance.
Billing, scheduling, and wait-time questions dominate the ticket mix and drag the average. Clinical interactions score higher but are often not surveyed. The honest version of a healthcare CSAT report splits the clinical and the administrative tracks, because they share almost nothing.
Industry benchmarks are useful as a rough sanity check and misleading as a target. Response rate, scale, phrasing, segment mix, and sample size vary across every published number. The internal comparison that actually matters is this quarter versus last quarter, holding the method constant.
The gap between a CSAT program that drives change and one that fills a dashboard is almost entirely about operations. Timing, segmentation, action loops, and ownership decide whether the score shows up in retention next quarter. The six cards below are the design decisions worth making before the first survey goes out.
Fire the survey within five to fifteen minutes of the interaction closing, not the next morning and not a week later. Memory decays fast, and the score drifts toward the overall relationship rather than the specific moment. Delayed surveys are measuring something, just not the thing CSAT is supposed to measure.
An average CSAT across every interaction type blurs the signal. Split it by touchpoint (onboarding, support, renewal, delivery), by channel (chat, email, phone), by segment (SMB vs enterprise), and by stage of the customer lifecycle. The averages agree. The segments tell the real story.
Define a threshold for a low score and route it to a named owner, with an SLA. CSMs, support managers, or team leads call the customer back inside a day. The callback is not an upsell. It is a diagnostic, a fix, and a signal to the organization that the number is read, not just reported.
When a specific rep, team, or workflow trends down three weeks in a row, that is a coaching conversation, not a dashboard anomaly. Pair the trend with the comments to make the one-on-one specific. Vague feedback produces vague improvement. Specific feedback produces measurable change.
When the same complaint shows up in open-text comments across dozens of tickets, it belongs in the product roadmap, not just the support queue. Share the themes with product and engineering every month. CSAT becomes an input into shipping, not just a report that leadership nods at.
A customer who answers CSAT, then NPS, then CES, then a product feedback form, stops answering. Pick one survey per interaction. Rotate the full set across the year. Keep response rates above 20 percent as the health check. If the rate drops, remove a survey before you add another.
A CSAT program that lives in a separate survey tool is a CSAT program that stays disconnected from the record it was measuring. When the score lands on the customer timeline next to the ticket, the call, and the deal, action becomes a routine instead of a project. The cards below are the shape CSAT takes when it is run from inside the CRM instead of alongside it.
A ticket closes, a call wraps, an onboarding call ends. The CRM fires the CSAT survey the moment the record flips to closed, not on a nightly batch. Scores show up on the customer timeline next to the interaction that produced them, so context never has to be reconstructed later.
Support can run a 1 to 5 scale. Onboarding can run a 1 to 7. Delivery can run a 5-star rating. Each touchpoint type has its own survey template, question, and low-score threshold. One tool, every touchpoint, no spreadsheet reconciliation at the end of the quarter.
A score below the configured threshold creates a task on the account owner or routes to the on-duty CSM, with the ticket, the comment, and the customer context attached. SLA clock starts. The callback is a workflow step, not a reminder that lives in someone's head. The loop closes the same day.
CSAT trends by rep, by team, by touchpoint, by segment, visible in the same reporting workspace as pipeline and renewal forecasts. Churn risk and satisfaction live together, because they are the same conversation on different timescales. One login, one data model, one quarterly review.
Open-text comments feed a themes report, so recurring complaints surface without someone reading every reply by hand. The themes become tasks on the right team: billing complaints to finance, product complaints to engineering, process complaints to operations.
CSAT inside the CRM stops being a dashboard metric and starts being a workflow trigger. Every low score has an owner, an SLA, and a next step. Every trend becomes a coaching conversation. Every pattern becomes a roadmap item. The score earns its weekly review slot because it moves the work.
Strkr runs CSAT on every closed ticket, call, and onboarding touchpoint, routes low scores to the right CSM with an SLA, and surfaces trends next to pipeline and renewal reporting. One tool, one data model, every touchpoint. Pricing is published and the platform tour is open.
CSAT stands for Customer Satisfaction Score. The acronym is used both as a label for the metric and as a shorthand for the survey that produces the metric. In day-to-day business conversation, "CSAT" almost always refers to the score itself, usually expressed as a percentage on a 0 to 100 scale.
The CSAT formula is the number of satisfied responses divided by the total number of responses, multiplied by 100. On a 1 to 5 scale, satisfied usually means a response of 4 or 5. The result is a percentage. A CSAT of 85 means 85 percent of respondents picked one of the top two options.
A rough industry benchmark is 75 to 85 percent for most B2B software, 80 to 90 percent for e-commerce, and 70 to 80 percent for financial services. These vary widely by scale, response rate, and segment mix, so the more useful comparison is your own trend line quarter over quarter, holding the measurement method constant.
CSAT measures how satisfied a customer felt about one specific interaction, right after the interaction. NPS measures how likely a customer is to recommend the company overall, usually on a quarterly or milestone cadence. CSAT is a transactional, local signal. NPS is a relational, trending signal. They answer different questions and should not be used interchangeably.
CSAT asks how satisfied the customer was with the outcome. CES, Customer Effort Score, asks how much effort it took to get there. A customer can rate CSAT high and CES low, meaning the resolution was good but the process was exhausting. Pairing the two surfaces the "satisfied but tired" segment that often churns a quarter or two later.
Fire a CSAT survey after every closed touchpoint of the type you want to measure: ticket close, onboarding call completion, delivery, renewal signing. Avoid sending more than one survey per interaction so response rates stay healthy. If a customer has multiple interactions in a short window, throttle to one survey per week per customer.
The usual mistakes are biased wording that primes a positive answer, timing that lands days after the memory has faded, a scale that keeps changing from quarter to quarter, a response rate that nobody tracks, no open-text follow-up to explain the score, and no action loop that turns low scores into callbacks and trends into coaching sessions.
CSAT is a leading indicator, not a direct retention metric. It tells you how a specific interaction landed, which in turn predicts whether the next interaction will be easier or harder. Pair it with NPS for relationship health and CES for effort friction. All three feed retention and expansion forecasts, but none of them replace the renewal and churn numbers themselves.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
