Verified channels
The platform’s verified customer-care channels are listed in the platform’s help center. The channel list is the most reliable source. Channels outside the help center are not verified.
- Live chat (in-app and web)
- Email support (published address)
- In-app complaint route
- Help center (self-service)
What real support does not ask
Real support does not ask for your password, OTP, or full card number. If a “support” chat asks for any of these, it is a phishing page. End the conversation, change your password, and use the platform’s in-app complaint route.
Customer-care questions
How long does email support take?
Replies may take 24 to 72 hours. Live chat is faster.
Is there a phone helpline?
Some platforms publish a phone helpline. The help center is the most reliable published source.
The complaint archive
The complaint archive is the historical record of the platform’s customer-care interactions. The archive is the binding source for the historical record. The archive is updated when a new complaint is logged.
The complaint archive is not a public registry; the player’s personal information is redacted. The aggregate statistics (response time, resolution time) are the binding source for the platform’s customer-care performance.
Quality of the response
The quality of the customer-care response is measured by three signals: response time, resolution rate, and customer satisfaction. The published help center is the binding source for the platform’s quality metrics.
The player should provide clear, concise information in the complaint. The complaint ID is the binding source for any subsequent reference; the player should keep the complaint ID until the complaint is resolved.
More customer-care questions
How do I know the response is real?
Real support does not ask for the password, OTP, or full card number. If the support chat asks for any of these, it is a phishing page. End the conversation and report the contact to the platform’s in-app complaint route.
How do I escalate a complaint?
Use the platform’s in-app complaint route. The complaint is logged, assigned to the platform’s compliance team, and tracked to a resolution. The escalation steps are published in the help center.
The full customer-care desk
The customer-care desk is the platform’s binding source for the support flow. The desk is staffed 24/7; the response time-band is published in the help center. The desk is the binding source for the platform’s customer-care commitments.
The desk publishes the update in the help center; the player should verify the published date before relying on any channel.
A closer look at the live chat
The live chat is the platform’s binding source for the real-time support. The live chat is typically staffed 24/7; the response time-band is published in the help center. The live chat is the binding source for the platform’s real-time support.
The live chat is the binding source for the platform’s customer-care commitment. The live chat is the binding source for the platform’s player support.
A closer look at the email support
The email support is the platform’s binding source for the asynchronous support. The email support is typically staffed 24/7; the response time-band is published in the help center. The email support is the binding source for the platform’s asynchronous support.
The email support is the binding source for the platform’s customer-care commitment. The email support is the binding source for the platform’s player support.
The full customer-care desk
The customer-care desk is the platform’s binding source for the support flow. The desk is staffed 24/7; the response time-band is published in the help center. The desk is the binding source for the platform’s customer-care commitments.
The desk publishes the update in the help center; the player should verify the published date before relying on any channel.
The full in-app complaint
The in-app complaint is the binding source for the platform’s complaint route. The complaint is logged, assigned to the platform’s compliance team, and tracked to a resolution. The in-app complaint is the binding source for the platform’s complaint escalation.
The in-app complaint is the binding source for the platform’s compliance. The complaint is the binding source for the player’s escalation; the player should always use the in-app complaint route.
Response time-bands
Live chat typically responds within minutes. Email support may take 24 to 72 hours. The in-app complaint route falls between the two: it is logged immediately and escalated to the platform’s compliance team within a fixed window (typically 7 to 14 days).
Response time-bands are published in the help center. The published time-band is the binding source; the player should escalate if the time-band is exceeded.
Escalation and the complaint route
The platform’s in-app complaint route is the binding escalation channel. The complaint is logged, assigned to the platform’s compliance team, and tracked to a resolution. The player receives a complaint ID; the complaint ID is the binding source for any subsequent reference.
If the complaint is not resolved within the published window, the escalation steps are published in the help center. The escalation steps typically include a regulator complaint route, an alternative dispute resolution route, and a court route as a last resort.
Language support
The platform’s support is offered in English and a small set of regional languages. The published language list is the binding source. If the player’s preferred language is not on the list, English support is the fallback.