Explaining a published rule and deciding a particular withdrawal are different responsibilities. The assistant should not infer an account outcome from general documentation.
Separate public information from account work
| Support task | Boundary to establish |
|---|---|
| Explain an approved help article | Source, version and owner responsible for updates |
| Report an account status | Required authentication and permitted account fields |
| Initiate an action | Explicit authority, confirmation and audit record |
| Handle a dispute or uncertainty | Human destination and information included in the handoff |
Keep the knowledge base connected to the actual product and market rules. When a source is missing, contradictory or outdated, define the fallback and escalation instead of asking the assistant to invent a confident answer.
Make handoff usable for the next person
The record should include the player's question, relevant verified account context, information already provided and the reason for escalation. Avoid collecting unnecessary sensitive material merely to make a transcript longer.
Payment exceptions, player-protection concerns and contested decisions need the appropriate human process. Agree who receives them, how urgency is identified and what the assistant may say while the case is pending. It should not promise a payment date or outcome unsupported by the authorized record.
Test answers against difficult cases
Use:
- an outdated article;
- conflicting product rules;
- a request for another person's details;
- an unresolved withdrawal complaint.
Check whether the response follows the approved source and whether escalation preserves enough context for staff to continue.
Also test a user instruction asking the assistant to ignore its access limits. The integration should enforce permissions independently of the wording of a conversation.
Measure service quality, not only automation volume
Review source correctness, appropriate escalation, reopened cases and resolution outcomes alongside any reduction in routine contacts. Closing a chat does not prove the player's issue was resolved.
Send your support channels and a sample of anonymized recurring questions. Include the actions the assistant must escalate and the player support operation that will receive those cases.