How to reach a human at the platform.
What is published by the platform for first-line customer care, plus the second-line escalation pathway for unresolved cases.
How to reach a human at the platform.
Customer-care pathways describe how a reader reaches a human at the platform. The page below describes what is published by the platform and what is unknown to this publication.
Most regulated platforms publish an email contact in the Help centre. The published turnaround is typically 24 to 72 hours. The email is the cleanest contact channel for verification or KYC issues and for any written record the reader needs to keep.
In-app chat
In-app chat is published by some regulated platforms. The published turnaround is typically minutes for routine questions and hours for verification issues. The chat transcript is the cleanest record for routine questions.
Phone
Phone contact is published by some regulated platforms. The published hours are usually business hours in the platform's primary market. Phone is the cleanest channel for urgent account-access issues but the rarest published channel.
What is unknown
The current contact details for the platform are not maintained by this publication. Consult the platform's Help centre for the current values. The platforms used by this publication route are described in the disclosure.
Where to escalate when first-line channels fail.
A short note on the second-line escalation pathway. The first-line channels above are usually sufficient; the second-line path is reserved for cases where the first-line response is unsatisfactory or absent.
Named grievance officer
Regulated platforms publish the name and contact of the grievance officer in the Terms page. The officer responds within seven working days of a written complaint. The complaint should include the users identifier, the issue summary and the requested resolution.
Public authority
If the grievance officer does not respond within seven working days, the next step is to raise the issue with the relevant public authority under the Online Gaming Act 2025 framework. The authority and the contact are described in the same framework.
How to write a complaint the platform will respond to.
A clean complaint includes four elements: the registered identifier, the issue summary, the requested resolution and the dates. The identifier lets the platform confirm the account without asking for sensitive data. The issue summary describes what happened, in chronological order, with one event per paragraph. The requested resolution states what the reader wants — a withdrawal, a KYC re-check, an account recovery. The dates pin the events to a timeline.
A complaint that includes those four elements is faster to action than a complaint that does not. A complaint missing the identifier is returned to the reader for more detail; a complaint missing the dates is treated as a general observation rather than an actionable issue.
How long the platform has to respond
Most regulated platforms publish a turnaround window in the Help centre. The window for routine issues is 24 to 72 hours; the window for withdrawal and KYC issues is the same; the window for unresolved issues escalated to the grievance officer is seven working days. If the platform misses its own turnaround, the next step is a written complaint to the named grievance officer.
The escalation ladder, in plain language.
The escalation ladder is the path the reader follows when the platform's response is unsatisfactory or absent. The ladder has three rungs: customer-care, named grievance officer, public authority. Each rung has a published turnaround; each rung escalates the urgency and the regulatory reach.
Rung one: customer-care
Customer-care is the first rung. The cleanest channels are email and in-app chat; both produce a written transcript. The email and chat turnaround is published in the Help centre; common values are 24 to 72 hours. Phone is the rarest published channel and is the cleanest path for urgent account-access issues.
Rung two: named grievance officer
The named grievance officer is the second rung. The officer's name and contact are published in the platform's Terms page. The officer responds within seven working days of a written complaint. The complaint should include the user's identifier, the issue summary, the requested resolution and the dates.
Rung three: public authority
The public authority is the third rung. The authority's name and contact are described in the Online Gaming Act 2025 framework. The authority's turnaround is published in the framework. The reader who escalates to the public authority should retain copies of all customer-care and grievance officer correspondence.
Writing an effective complaint
An effective complaint includes four elements: the registered identifier, the issue summary, the requested resolution and the dates. A complaint with all four elements is faster to action than one without. A complaint missing the identifier is returned for more detail; a complaint missing the dates is treated as a general observation.
What the publication is not
The publication is not the platform's customer-care pathway. The platform operates its customer-care pathway; the publication describes the path. Where the path's behaviour disagrees with the publication's description, the reader should consult the platform's own documentation.
What a good response looks like.
A good response addresses every element of the complaint: the registered identifier, the issue summary, the requested resolution and the dates. A good response commits to a specific next step and a specific timeline. A good response cites the platform's policy where the policy applies.
What a poor response looks like
A poor response ignores elements of the complaint. A poor response offers a generic apology without committing to a specific next step. A poor response does not cite the platform's policy where the policy applies. A poor response is the basis for escalation to the named grievance officer.
The escalation ladder
The ladder has three rungs: customer-care, named grievance officer, public authority. Each rung has a published turnaround. The reader escalates when the rung's turnaround is missed or the response does not address the complaint. The ladder is described in detail earlier in this chapter.
When to skip a rung
A reader may skip a rung where the issue is critical. A reader who has been locked out of the wallet due to a KYC error and who cannot reach customer-care may escalate directly to the named grievance officer. The reader who skips a rung should retain evidence of the skipped rung's unavailability.
What the publication is not
The publication is not the platform's customer-care pathway. The platform operates its customer-care pathway; the publication describes the path. Where the path's behaviour disagrees with the publication's description, the reader should consult the platform's own documentation.