Complaint Timeline Checklist for Players

Readers can write a short description covering what happened, which account activity is relevant and what needs clarification. It may help to separate confirmed details from opinions or unanswered questions. Avoid including passwords, full payment credentials or other sensitive information in general correspondence.

Useful details to check may include:

• the account name or reference requested by the service;
• the date shown on relevant account records;
• the feature, transaction or interaction connected with the issue;
• copies of messages or notices already received;
• the specific explanation or action being requested.

Before submitting anything, readers can review the published complaint instructions and verify whether different issues have separate contact channels. They can also check whether a reference code is issued, whether replies should remain in the same message thread and whether further review can be requested.

The Fair Go complaint timeline guide can be used as a starting point for identifying stages and questions to record. Readers should compare any guidance with the current information displayed through the relevant service channel.

A simple log can help readers track what has been sent and received. Each entry can note the date, communication method, subject, reference code and a brief summary. Supporting files can be stored with clear names so they are easier to match with the complaint.

Readers should verify that attachments are relevant and readable before sending them. If additional information is requested, they can confirm what is needed and use the stated submission method. Keeping wording factual and focused may reduce confusion.

At every stage, readers can check:

• whether the complaint was received;
• whether a reference code was provided;
• whether the response addresses each point raised;
• whether any requested next step is clearly explained;
• whether an internal review or external pathway is described;
• whether further correspondence needs to quote the original reference.

Readers can avoid treating an automated acknowledgement as a final response unless it clearly says so. They can also compare the reply with their original questions and list any matters that remain unanswered.

Only information relevant to the complaint should be shared. Readers can verify the recipient and communication channel before providing account-related material. Sensitive credentials should not be placed in a complaint summary.

Before closing the matter, readers can save the final correspondence, note the outcome and confirm whether any follow-up action remains. This creates an orderly record without assuming that a particular decision or resolution will occur.