CSAT (Customer Satisfaction Score) is the percentage of players who rate a support interaction positively. For an online casino, you calculate it by dividing the positive survey responses, usually ratings of 4 or 5 on a five-point scale, by all responses, then multiplying by 100. A score above roughly 80% is commonly treated as healthy, but the number only means something when the survey is consistent, the sample size is shown and the score is read next to resolution data.
This guide covers the formula, realistic targets, how to survey across channels, the factors that distort the figure and how to turn the result into better player support.
TL;DR
- CSAT = positive responses (4 and 5 on a five-point scale) ÷ total responses × 100.
- Around 80% and above is a common marker of good satisfaction, but compare your own score over time before you compare it with other operators.
- Survey once per resolved ticket, in the same channel as the conversation, and tag every result by channel.
- Always report the sample size, and read CSAT alongside first-contact resolution, reopen rate and repeat contacts.
- Human review of AI replies protects the quality that CSAT is trying to capture, and gives you an audit trail behind every score.
Table of Contents
- What CSAT measures in player support
- How to calculate CSAT
- What is a good CSAT score for an online casino?
- How to measure CSAT across channels
- What makes a casino CSAT score unreliable
- Turning CSAT into better support
- Where AI helps, and where human review matters
- A simple CSAT set-up for your casino
- How Pitbot supports a CSAT programme
- FAQ
- Sources
What CSAT measures in player support
CSAT measures how satisfied a customer is with a specific interaction, product or service. IBM describes it as positive survey responses divided by total responses, multiplied by 100. That makes it a transactional metric: it tells you how a player felt about one conversation, not how they feel about your brand overall.
That distinction matters in a casino. A player who contacts support about a delayed withdrawal, a bonus that did not credit or a verification request is often already frustrated. A low rating may reflect the withdrawal rule rather than the agent. A high rating may reflect a friendly tone on a ticket that was never really solved. CSAT is useful because it is quick and easy to read, and it is risky for the same reason.
It also sits beside other measures. Net Promoter Score asks whether a player would recommend you. First-contact resolution asks whether the issue was fixed in one go. Response and resolution times describe speed. CSAT captures the feeling at the end of a single exchange, and it works best as one signal among several.
How to calculate CSAT
The calculation is simple, and the discipline lies in defining each part of it the same way every time.
- Ask one question. For example: “How satisfied were you with the help you received?” Use a five-point scale from very dissatisfied to very satisfied.
- Count positive responses. The usual definition is ratings of 4 and 5 on a five-point scale, as set out in SurveyMonkey’s guide to calculating CSAT.
- Divide by total responses. Use responses received, not surveys sent. Exclude skipped or partial responses.
- Multiply by 100. The result is your CSAT percentage.
- Report the sample size. A score without the number of responses behind it cannot be interpreted or compared.
A worked example
Suppose a casino support team sends a survey after each resolved live chat ticket in one week and receives 240 completed responses. Of those, 130 players chose 5 and 62 chose 4, so 192 are positive.
192 ÷ 240 = 0.80, so CSAT is 80% (n = 240).
Now imagine the next week brings 40 responses and 36 positive. That is 90%, but on a sample of 40 it is far less trustworthy than 80% on 240. This is why the n value belongs next to every figure you put on a dashboard.
Some teams use a 1 to 10 scale instead. Testronic’s guidance on player support metrics notes that player surveys can use that scale with the same positive-over-total approach. Whichever scale you choose, fix the definition of “positive” in writing and do not change it mid-year. If you do, mark the date on your reports, because the trend line breaks at that point.
What is a good CSAT score for an online casino?
There is no single official benchmark for casino CSAT. Different sources give different ranges, and all of them come from vendor or publisher content rather than a regulator. A reasonable working view:
| Score | How to read it |
|---|---|
| Below 50% | Clear dissatisfaction. Investigate ticket types and channels first. |
| 50% to 70% | Mixed. Look for specific topics, such as withdrawals or verification, dragging the average down. |
| 70% to 80% | Acceptable, with room to improve. |
| 80% to 90% | Strong. Testronic calls a score above 80% a good indicator of player satisfaction. |
| Above 90% | Excellent, provided the sample is large and resolution data backs it up. |
So is 80% good? Usually yes. Is 90% good? Yes, but ask how many players responded and which players. A casino that only surveys quick, easy tickets will report a flattering figure that hides its hardest cases.
The more useful question is not “how do we compare?” but “are we improving?” iGaming Times makes this point: internal benchmarking over time, with constant definitions and segmentation by ticket type or outcome, is more informative for operational improvement than comparing absolute CSAT figures with other companies. Survey instruments, collection points and response rates differ so much between operators that a cross-company comparison is rarely like for like.
How to measure CSAT across channels
Players reach a casino through live chat, email, SMS and increasingly Telegram. Each channel has its own rhythm, and your survey should respect it.
Survey in the channel the player used
The guidance from Questback on trustworthy CSAT is to send the survey in the same channel and as close to the interaction as possible. A live chat player should see a one-tap rating at the end of the chat. An email player should get a short rating link in the closing message. A Telegram player should be asked inside Telegram. Pushing someone from a chat to an emailed survey a day later lowers response rates and shifts who answers.
Tag every result by channel
Tag each response with its channel, so you can compare like with like. Live chat tends to be fast and conversational, and email tends to carry complex cases such as account verification or dispute documentation. A blended score hides those differences. If your email CSAT sits ten points below chat, the cause may be slower resolution on email rather than poorer agents, and only a channel tag lets you see that.
Survey once per resolved ticket
Survey fatigue is a real data-quality problem. Questback notes that surveying too often, for instance after every message instead of once per resolved ticket, significantly lowers response rates and degrades quality. One survey per resolved case is the cleanest rule. For a player who writes in three times about the same issue, treat it as one case with one rating.
Keep a single player record
Channel tags only help if you can see the whole journey. A player who starts in chat, follows up by email and finishes by SMS should have one history, so the rating lands on the right case. Our guide to the components of an omnichannel player record sets out what operators need to join that up.
What makes a casino CSAT score unreliable
A number can be precise and still misleading. The usual causes are:
- Different instruments and collection points. A rating after the chat is not the same as a rating in an email a day later. iGaming Times lists survey instruments, collection points and response rates among the factors that affect reliability.
- Contact outcomes. Aggregate scores can be distorted by what happened to the player. A player whose withdrawal was declined for a valid compliance reason may rate low whatever the quality of the reply.
- Low or self-selected response. Players at the extremes respond most. A small, skewed sample gives a volatile score.
- Inconsistent definitions. Counting a 3 as positive one month and not the next makes trends meaningless. Exclude skipped and partial responses every time.
- Missing sample size. Without n, nobody can tell a stable 85% from a lucky one.
Read CSAT beside resolution metrics
A friendly, quick answer can earn a high rating even when the problem is still open. iGaming CX, in its CX KPI dashboard article, recommends reading CSAT alongside first-contact resolution, ticket-reopen rate, repeat contacts, response time and resolution time, and treating it as one quality signal rather than a standalone truth. In practice, put these five on the same page as CSAT:
- First-contact resolution rate.
- Ticket-reopen rate.
- Repeat contacts from the same player on the same issue.
- Median first response time.
- Median resolution time.
If CSAT rises while repeat contacts also rise, players are being pleasantly told something that does not fix their problem. For a wider view of how operators structure these measures, including regulatory expectations, see our piece on casino support KPIs, LCCP 3.4.3, AI and human review.
Turning CSAT into better support
A score on its own changes nothing. The value comes from what you do when it moves.
Find the cause before you coach
When CSAT falls, the instinct is to retrain the whole team. iGaming Times suggests a sharper approach: use satisfaction data to investigate the ticket types, topics or channels behind the drop, rather than defaulting to general coaching. Build a weekly cut of CSAT by topic: withdrawals, deposits, bonuses, verification, account access, responsible gambling queries. One topic usually explains most of a dip.
Add quality reviews
CSAT tells you how players felt. Internal quality reviews tell you why. Scoring a sample of conversations for tone, accuracy and empathy gives you a second angle and catches problems that players do not mention in a survey. Compare the two: if reviewers rate a conversation highly and the player rated it low, the issue is probably policy or process, not the agent.
Read the comments
Add an optional free-text field after the rating, shown most prominently to low scorers. A few dozen comments will often name the same two or three frictions: unclear verification steps, slow payout updates, answers that ignore the player’s earlier messages. Those are fixes you can make in templates, knowledge content and escalation rules.
Protect vulnerable players from the survey itself
Satisfaction surveys are marketing-adjacent contact. If a player has been flagged for responsible gambling concerns, think carefully about whether any non-essential outreach should reach them. Operators in Great Britain work under the Gambling Commission’s licence conditions on customer interaction, so involve your compliance officer in deciding when surveys are suppressed.
Where AI helps, and where human review matters
AI can lift the inputs to CSAT: faster first replies, consistent tone, replies in the player’s language and around-the-clock coverage. Automatic language detection alone removes a common source of poor ratings, namely a player answered in a language they do not read comfortably.
But speed is not satisfaction. A fast wrong answer on a payout or a bonus term will score badly and may create a compliance issue as well. That is why the design of the workflow matters as much as the model behind it. In a setup where every AI-drafted reply is checked by a member of staff before it reaches the player, the team can keep the speed while controlling accuracy and tone. Our overview of automating routine queries while escalating risk shows which query types suit automation and which should go straight to a person.
Two practical points for CSAT reporting when AI is involved:
- Tag AI-assisted and fully human conversations separately. You want to know whether reviewed AI replies hold CSAT at the level of your best agents.
- Keep the audit trail. When a score drops, being able to open the conversation, see the draft, the reviewer’s edit and the final message turns a vague number into a specific lesson.
Our perspective
We build player support for casinos, so we see the same pattern again and again: operators treat CSAT as a verdict on their agents, when it is really a verdict on the whole chain, from the first reply to the final fix.
Our view is that a satisfaction score is only as trustworthy as the process that produces the replies. That is why every AI-generated answer in Pitbot is reviewed by your staff before it reaches a player. Speed comes from the AI. Accuracy, tone and regulatory care come from the reviewer. The two together are what players rate.
We also think CSAT should never be read alone. Sentiment detection and escalation mean an unhappy player reaches a person quickly, and VIP queue management keeps your most valuable relationships from waiting. Multilingual replies and consistent personas mean a player’s experience does not depend on which shift they happen to write in.
Finally, a score you cannot explain is a score you cannot improve. Our audit trail records each decision behind a reply, so when CSAT moves, you can open the conversations and see why.
pitbot
A simple CSAT set-up for your casino
If you are starting from scratch, this is a sensible first version.
- Define the question and scale. One question, five points, “positive” means 4 and 5.
- Trigger on resolution. Send when a ticket is marked resolved, once per case.
- Use the same channel. Chat survey in chat, email survey in email, Telegram and SMS prompts in their own thread.
- Tag the data. Channel, topic, language, VIP or standard queue, human or AI-assisted.
- Report n. Every figure on the dashboard shows its sample size, and small samples are flagged.
- Pair with resolution metrics. First-contact resolution, reopen rate and repeat contacts sit next to CSAT.
- Review monthly. Look at the weakest topic and channel, read the comments, pick one fix and measure it the next month.
- Keep definitions fixed. Document any change and annotate the trend.
That is enough to give you a score you can defend in a management meeting or a compliance review.
How Pitbot supports a CSAT programme
Pitbot is an AI-powered support platform for online casino operators. It combines several AI providers with human review, so each reply is checked before it goes out, and it brings email, live chat, SMS and Telegram into one dashboard. Automated sentiment detection and escalation, VIP queue management, multilingual capability, responsible gambling detection with outreach suppression and operational analytics are all part of the same workspace, alongside the audit trail described above.
For teams that want cleaner CSAT data and faster, compliant replies, see how AI customer support for online casino and iGaming operators works, or browse the full feature list.
If you would like to see it applied to your own channels and queues, you can start from the Pitbot home page and request a demo.
FAQ
Is 80% CSAT good for an online casino?
Yes, in most cases. Around 80% and above is widely treated as a good indicator of satisfaction, and Testronic uses that threshold for player support. Check the sample size and your resolution metrics too, because a high score on a small or selective sample says little.
How do I calculate my CSAT score?
Count the survey responses rated 4 or 5 on a five-point scale, divide by the total number of responses and multiply by 100. Exclude skipped or partial responses and always publish the number of responses beside the percentage, as SurveyMonkey’s guide advises.
What does CSAT stand for?
CSAT stands for Customer Satisfaction Score. It measures how satisfied a customer is with a specific interaction, product or service, according to IBM’s explanation of CSAT. In casino support, that usually means one conversation about a deposit, withdrawal, bonus or account query.
Is 90% customer satisfaction good?
It is excellent if it comes from a large, representative sample and your first-contact resolution and repeat-contact figures support it. If it comes from a few dozen responses or only the easiest tickets, treat it cautiously. Track the trend over time rather than chasing a single figure.
Should casinos compare their CSAT with other operators?
Be careful. Survey wording, timing and response rates differ between companies, so absolute comparisons mislead. iGaming Times recommends benchmarking against your own history with constant definitions and segmenting by ticket type or outcome.
Sources
- What is CSAT and How to Calculate It? (IBM)
- How To Calculate CSAT Score: Formula, Strategy & Guide (SurveyMonkey)
- Five Key Metrics For Delivering Exceptional Player Support (Testronic)
- CSAT you can trust and act on (Questback)
- Measuring and Improving Service (iGaming Times)
- The Essential CX KPI Dashboard: 15 Metrics Every Operator Should Track (iGaming CX)
