A careful checklist for preparing a gaming complaint

When a gaming-related concern needs to be raised, a clear and cautious approach can help readers organise the issue before using any complaint channel. The aim is not to assume that a complaint will produce a particular result, but to make sure the information provided is accurate, relevant and suitable for the selected process.

Clarify the issue

Start by describing the concern in neutral language. Note what happened, when the issue arose, and which service or interaction it relates to, without adding assumptions that cannot be supported. Separate confirmed details from questions or concerns. A short timeline can make the account easier to review, but readers should include only information they are comfortable sharing through a verified channel.

Readers can review the gaming complaint form guidance as one point of reference when considering how to structure a submission. Before relying on any page, check that it is current, relevant to the issue and connected to a trustworthy submission route.

Check the process before submitting

Before entering information, readers can verify:

• whether the channel is intended for the type of concern being raised;
• whether the current official instructions describe the available process;
• what information is optional, and what the channel actually asks for;
• whether the page uses a secure connection and provides a reliable way to confirm its authenticity; and
• whether the submission can be saved or reviewed before it is sent.

Requirements and contact routes may change. Readers should consult current official requirements and use a verified submission channel rather than relying on an old copy, an unsolicited message or an unconfirmed contact detail. If the process is unclear, they can seek clarification through an independently verified official route before submitting anything.

Protect personal and account security

Share only information that is relevant and appropriate for the verified process. Do not include card images, CVV or CVC codes, PINs, one-time passwords, passwords or recovery codes in complaint files, screenshots, email, chat or support messages. Sensitive payment credentials and account-security secrets should remain private. Readers should also check screenshots and attachments for unrelated personal information before sharing them.

Review before sending

Read the completed complaint carefully for accuracy, clarity and respectful wording. Keep a private record of what was submitted and where it was sent, without assuming that a particular response or timeframe will follow. If new information appears, readers can check the current process again and decide whether an updated submission is appropriate.