Blog · Board and management reporting · Customer service
CSAT analytics compares satisfaction responses by issue, team, and period. Work through a change caused by response mix, reconcile the counts, and decide what the service team should investigate.
CSAT analytics explains how customer satisfaction responses differ by issue, team, and period. Keep the response counts next to each percentage, then ask whether the change came from different experiences or a different mix of respondents. A company average alone cannot distinguish those explanations.
Use the satisfaction question and scoring rule your business has already approved. The example below counts ratings of four or five on a five-point satisfaction scale as satisfied. All other valid ratings remain in the denominator; missing and out-of-range answers do not.
The general metric belongs with customer satisfaction KPIs. This review focuses on investigating outcomes once the rule is fixed. Do not combine different questions, scales, or points in the customer journey simply because each export labels a column CSAT.
Choose one reporting clock. Invitation month with an equal response window is one option; service-completion month with an equal follow-up period is another. A monthly comparison becomes misleading when the earlier month had a full response window and the later month is still collecting answers.
Keep issue and team assignments as they were for the surveyed interaction. A later team reorganization should not silently rewrite the history. If an interaction involved several teams, apply a documented ownership rule instead of putting its response into every team's total.
The invitation register needs invitation ID, reporting period, issue, team, and eligibility status. The response export needs the matching invitation ID, response date, survey version, and accepted rating. Use deidentified interaction references; names, email addresses, and free-text personal details are unnecessary for this comparison.
Retain invitations that received no answer. Deduplicate accepted submissions using an agreed rule, then count valid answers and satisfied answers by segment. If the file contains only summarized counts, confirm that the groups are mutually exclusive and that each total uses the same scoring rule.
The customer satisfaction survey analysis method covers detailed export validation. For the investigation table, retain three counts: eligible invitations, valid answers to the satisfaction question, and answers meeting the satisfaction threshold.
Segment satisfaction rate = Satisfied answers / Valid satisfaction answers
Valid-answer coverage = Valid satisfaction answers / Eligible invitations
Coverage here refers to the specific satisfaction question. A customer who submits a survey but skips that question does not supply a valid satisfaction answer. If the team also reports survey participation, label it separately.
An illustrative US equipment distributor asks the same post-service question in May and June 2026. Both months have closed response windows. The table contains all eligible invitations and accepted valid satisfaction answers for the review; issues are mutually exclusive.
| Period | Issue | Eligible invitations | Valid answers | Satisfied answers | Other valid answers | Satisfaction rate | Valid-answer coverage |
|---|---|---|---|---|---|---|---|
| May | Billing | 200 | 100 | 70 | 30 | 70.0% | 50.0% |
| May | Delivery | 200 | 100 | 90 | 10 | 90.0% | 50.0% |
| May total | 400 | 200 | 160 | 40 | 80.0% | 50.0% | |
| June | Billing | 360 | 180 | 126 | 54 | 70.0% | 50.0% |
| June | Delivery | 40 | 20 | 18 | 2 | 90.0% | 50.0% |
| June total | 400 | 200 | 144 | 56 | 72.0% | 50.0% |
May's overall satisfaction is (70 + 90) / (100 + 100) = 160 / 200 = 80.0%. June's is (126 + 18) / (180 + 20) = 144 / 200 = 72.0%. The decrease is 80.0 − 72.0 = 8.0 percentage points.
Billing stays at 70 / 100 = 126 / 180 = 70.0%. Delivery stays at 90 / 100 = 18 / 20 = 90.0%. What changes is the respondent mix: billing moves from 100 / 200 = 50.0% of valid answers to 180 / 200 = 90.0%.
As a diagnostic, apply May's equal issue weights to June's issue rates. The result is 50.0% × 70.0% + 50.0% × 90.0% = 80.0%. That comparison holds the response mix constant; it is not June's reported score. In this constructed example, the entire overall decline comes from the issue mix.
All displayed percentages use one decimal place. Calculate from the counts without rounding intermediate values.
For every row, satisfied answers plus other valid answers must equal valid answers. June billing checks as 126 + 54 = 180. For the month, 144 + 56 = 200. The issue totals must also match the accepted-response export, and eligible invitations must match the invitation register.
Calculate an overall rate from summed counts. Averaging June's issue percentages would give (70.0% + 90.0%) / 2 = 80.0%, which ignores the actual respondent mix and overstates the observed overall rate.
Reconcile exclusions separately: duplicate submissions, unmatched invitations, missing answers, and invalid ratings. Do not let discarded records disappear without a count. A team should be able to reproduce both the published denominator and the records left outside it.
The service manager should investigate why billing represents more of the surveyed work. It may reflect more billing contacts, a change in invitation coverage, or a change in issue coding. The table shows the composition change; it does not establish the operational cause.
The survey owner checks wording, timing, delivery, and eligibility. Team leads review comparable issue groups. The operations owner checks whether the interaction volumes and classifications changed. Keep a CSAT dashboard for presenting these agreed measures, while retaining the underlying count table for review.
Use feedback to choose a follow-up question and an action owner. Performance.gov describes post-transaction feedback as a way to evaluate service delivery and prioritize improvements. That is a useful purpose for the company review too: identify the experience to inspect, rather than treating every movement as an agent performance verdict.
Unanswered invitations still matter. The Census Bureau explains that survey estimates can be biased when nonrespondents differ from respondents. The unchanged coverage in this example does not prove that respondents represent every customer, and the comparison does not establish statistical significance.
Bring your accepted response counts, invitation totals, and agreed segment definitions to Covirage; it maps the columns, and its tools compute and check the comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.
See Covirage for customer service teams for the wider service review.
Yes. The overall rate weights issues by their valid response counts. If a lower-scoring issue represents more responses, the combined score can fall without a change within either issue. Compare both the segment rates and the response mix.
Use the score as a starting point for investigation. Teams may handle different issue types, customer groups, and service stages. Show the number of valid responses and compare similar work before attributing a difference to a team's performance.
No. It describes participation under the stated invitation and eligibility rules. Bias depends on whether respondents differ from people who did not respond. Check coverage across important customer groups and keep the limits of a voluntary survey visible.