A Practical Checklist for Raising and Tracking a Complaint

When a concern arises, a clear and methodical approach can make the complaint easier to explain and track. Readers can focus on preserving accurate records, identifying the relevant policy and stating the resolution they are seeking. The following checklist is procedural and does not assess any operator or individual complaint.

Define the issue clearly

Before contacting support, write a short summary of the concern. Separate confirmed events from assumptions and note the sequence in which they occurred. Include relevant account references or transaction identifiers without placing sensitive information in public posts.

Readers can use the Fastpay complaints guide as a starting point when organising the questions they want to raise.

A useful summary can cover:

• what action or entry caused concern;
• where the issue appeared;
• which policy or account term may be relevant;
• what has already been communicated; and
• what specific remedy or explanation is being requested.

Preserve supporting records

Keep copies of messages, account notices, transaction references and the terms that were visible when the issue arose. Screenshots can help preserve on-screen information, but readers should also retain original messages where possible. Avoid editing files in a way that removes context.

Check that each record can be matched to the relevant event. A simple chronological list can make a complex complaint easier to follow. Sensitive details should be redacted before anything is shared outside the appropriate support or dispute channel.

Compare the issue with the published terms

Readers can review the terms, complaint policy and account rules that apply to the matter. Look for sections covering eligibility, account restrictions, game rules, transaction handling and dispute escalation. If wording is unclear, quote the relevant clause in the complaint and ask for an explanation in plain language.

Do not assume that a general statement overrides a more specific condition. Compare related sections and note any apparent inconsistency as a question rather than presenting an unsupported conclusion.

Write a focused complaint

Use a descriptive subject line and keep the opening concise. State the issue, list the key references and explain the requested remedy. Neutral language helps keep attention on the evidence. Avoid threats, repeated messages or unrelated allegations.

Before sending, verify that:

• names and account references are accurate;
• the sequence of events is internally consistent;
• attachments relate directly to the concern;
• private information is shared only through an appropriate channel; and
• the requested response is clear and practical.

Track correspondence and escalation

Save each reply and note any reference assigned to the complaint. Keep follow-up messages in the same thread where practical so the history remains easy to review. If escalation is available, check the published procedure and provide the existing complaint reference rather than starting again without context.

When reviewing a reply, compare it with the questions originally raised. Identify which points were addressed and which still need clarification. A short, itemised follow-up can be more useful than repeating the entire complaint.

Final review

Before taking another step, check the full record for accuracy, relevance and privacy. Readers should distinguish between dissatisfaction, a request for clarification and an allegation requiring evidence. A structured complaint cannot determine the outcome, but it can present the issue in a form that is easier for the appropriate recipient to assess.