The support channels the desk has verified, and how to escalate when needed.
The customer-care page is a support page, not a editorial guide. The desk does not earn a commission for clicks to the support channels. The page lists the support channels the desk has verified, the inputs the support team will ask for, and the escalation steps when a first response is unsatisfactory.
On this page
Verified support channels
The desk has not verified a current LetsGame customer-care channel as of 22 July 2026. The verification step requires a public support page on the platform's official domain, with a working email or chat channel. The desk updates the topic below when a verified support channel is published. The desk's recommendation is to use the platform's official support channel, and to avoid third-party contact forms that claim to be the platform's support.
What the support team will ask for
When you contact the support team, the desk recommends having the following inputs ready: the email address on the account, the last successful login, the device you usually log in from, any recent transactions, and a clear description of the issue. The desk's position is that the more inputs you provide upfront, the faster the support team can respond. The support team will not ask for your password, and any request for your password is a phishing signal.
How to escalate an unsatisfactory response
If the first response is unsatisfactory, the desk recommends a three-step escalation. First, reply to the support thread with a clear summary of the issue and the response you received. Second, request a second-level review through the platform's escalation channel. Third, if the second-level review is still unsatisfactory, document the entire thread and consider filing a complaint with the consumer forum in your jurisdiction. The desk's recommendation is to document every step, and to keep the documentation in a place you can access later.
How to delete your account
If you want to delete your account, the desk recommends a three-step process. First, withdraw any remaining balance from the wallet, following the platform's withdrawal flow. Second, contact the support team through the verified channel and request account deletion. Third, request confirmation in writing that the account has been deleted, and that the data associated with the account has been removed in accordance with the platform's privacy policy. The desk's position is that account deletion is a right, and the platform is required to honour the request within a reasonable time.
Support is a discipline. Document every step, escalate when needed, and keep the record.
How to read a support channel you have never used before
A new support channel is a channel the desk has not covered. The desk's reading of a new support channel is conservative: read the email, read the chat, read the phone, and read the help centre. The four reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a new support channel, and the desk does not recommend a specific platform without the four reads. The reason is the same: a hot take is a guess, and a guess is not the product.
How the desk handles a support channel that does not respond
A support channel that does not respond is a signal to slow down, not a signal to dismiss. The desk's reading of a non-responsive support channel is conservative: read the response time, read the inputs the desk recommends, and read the corrections log. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a non-responsive support channel is verified, and the correction is the input the desk recommends reading.
How to read a support channel that asks for unusual inputs
A support channel that asks for unusual inputs is a phishing signal, not a legitimate support flow. The desk's reading of an unusual-input support channel is conservative: read the inputs, read the privacy policy, and read the publisher name. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a phishing support channel is verified, and the correction is the input the desk recommends reading.
How the desk handles a support channel that does not use the official domain
A support channel that does not use the official domain is a phishing signal, not a legitimate support flow. The desk's reading of a mismatched support channel is conservative: read the domain, read the inputs the desk recommends, and read the corrections log. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a mismatched support channel is verified, and the correction is the input the desk recommends reading.
How to read an account-deletion flow you have never used before
A new account-deletion flow is a flow the desk has not covered. The desk's reading of a new account-deletion flow is conservative: read the inputs the desk recommends, read the response time, and read the confirmation. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a new account-deletion flow, and the desk does not recommend a specific platform without the three reads. The reason is the same: a hot take is a guess, and a guess is not the product.
How the desk handles a support channel on a day with no matches
The desk does not publish a support update on a day with no matches. The desk's reading of a no-match day is conservative: read the corrections log, read the editorial policy, and read the responsible-play page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a no-match day, and the desk does not recommend a specific support channel. The reason is the same: a hot take is a guess, and a guess is not the product.
How to read a support response that does not address the issue
A support response that does not address the issue is a signal to escalate, not a signal to dismiss. The desk's reading of a non-addressing support response is conservative: read the response, compare the response to the original issue, and read the escalation policy. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a non-addressing support response is verified, and the correction is the input the desk recommends reading.
How the desk handles a support response that asks for additional documents
A support response that asks for additional documents is a signal to slow down, not a signal to dismiss. The desk's reading of a documents-requesting support response is conservative: read the request, compare the request to the original documents, and read the privacy policy. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a documents-requesting support response is verified, and the correction is the input the desk recommends reading.
How to read a support response that delays the resolution
A support response that delays the resolution is a signal to escalate, not a signal to dismiss. The desk's reading of a delaying support response is conservative: read the response, compare the response to the response time, and read the escalation policy. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a delaying support response is verified, and the correction is the input the desk recommends reading.
How the desk handles a support response that closes the ticket prematurely
A support response that closes the ticket prematurely is a signal to escalate, not a signal to dismiss. The desk's reading of a prematurely-closed support response is conservative: read the response, compare the response to the original issue, and read the escalation policy. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a prematurely-closed support response is verified, and the correction is the input the desk recommends reading.
How to read a support response that requests a survey
A support response that requests a survey is a signal to slow down, not a signal to dismiss. The desk's reading of a survey-requesting support response is conservative: read the request, compare the request to the original issue, and read the escalation policy. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a survey-requesting support response is verified, and the correction is the input the desk recommends reading.
How the desk handles a support response on a day with no matches
The desk does not publish a support response update on a day with no matches. The desk's reading of a no-match day is conservative: read the corrections log, read the editorial policy, and read the responsible-play page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a no-match day, and the desk does not recommend a specific support channel. The reason is the same: a hot take is a guess, and a guess is not the product.