Tag why casino and sportsbook customers contact support
Gives every conversation one contact reason, a root cause and a product, from withdrawal delays and verification to bonus terms and disputed bets, so reports show why people contact you and what keeps causing it.
Try it on this example
Channel (email, web chat, chat app, SMS, call): Call
The whole conversation, oldest message first
- What is the main reason the customer contacted support?Bet settlement100%
- What caused the contact, as far as the conversation shows?Customer misunderstanding65%
- Which product does the contact concern?Sportsbook100%
- Could the customer have found the answer in the help centre or the account pages?Yes64%
- Does the customer name or describe another betting or casino operator?Yes98%
- Does the customer ask for something the product does not offer?Yes92%
These are real answers stored from one run on this example.
The prism behind it
Tag why casino and sportsbook customers contact support
Fields
- Channel (email, web chat, chat app, SMS, call)
- The whole conversation, oldest message first
Context
We are Kestrel Play, an online casino and sportsbook with live casino and poker. The text is one support conversation, oldest message first, and may have no speaker labels; the customer is the person who contacted support. The answers tag each conversation for reporting. Replace the reasons, causes and products below with your own lists; keep one list per question.
Questions
What is the main reason the customer contacted support? Choice
Choose the single dominant reason, not every topic mentioned.
What caused the contact, as far as the conversation shows? Choice
Choose insufficient information rather than guess at a cause the conversation does not establish.
Which product does the contact concern? Choice
Could the customer have found the answer in the help centre or the account pages? Yes / No
Yes: The question has a general answer, such as a published timescale, a rule or where a setting is, needing no agent judgement or account access. No: It needed agent judgement, access to the account or an action only staff can take.
Does the customer name or describe another betting or casino operator? Yes / No
Yes: Another operator, brand or site is named or clearly described. No: No other operator is referred to.
Does the customer ask for something the product does not offer? Yes / No
Yes: The customer asks for a new feature, game, market, payment method or change in how something works. No: No such request appears; reporting that something is broken does not count.
Lens columns
contact_reason, contact_reason_probability, root_cause, root_cause_probability, product, product_probability, self_service_possible, self_service_possible_probability, competitor_mentioned, competitor_mentioned_probability, feature_request, feature_request_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.