How to Write a Complaint to an Operator That Can Be Checked Against the Facts

A verifiable complaint answers six questions: which account, which transaction, what happened, when it happened, which rule applies and what decision you are asking for. Start with the account and transaction numbers, give a short timeline, attach an index of evidence and state one specific request.

Do not send a stream of messages, threats or dozens of files without a list. Do not present a technical error, fraud or a breach of the law as an established fact if you have no confirmation. A strong wording looks like this: “Please check the transaction against the log, apply the rule that was in force on the date of the event and give me a written calculation.” Keep the version you sent, the confirmation of receipt and the complaint number.

A complaint and a support question are not the same thing

A message like “where is my withdrawal?” may get an informational reply. A formal complaint must clearly state that you are disputing an action, a decision or a failure to act and are asking for the complaints procedure to be applied.

Before sending, find:

• the Complaints or Dispute Resolution section;
• the official channel for submitting it;
• the information the operator asks you to include;
• the internal escalation stages;
• the response time stated in the rules;
• the further route available to you;
• restrictions on attachments and personal data.

The UK Gambling Commission advises contacting the gambling business directly first, following its procedure, giving dates, times and amounts, and keeping a copy of everything. This is the route for a British licence. In another GEO, the procedure and the deadline need to be checked separately.

Seven blocks of a verifiable complaint

1. Subject line

State the type of request and the identifier:

Formal complaint regarding transaction [ID] of [date]

Do not use a subject like “Urgent!!!” or “Give everything back”. It does not help anyone find the event.

2. Identification without secrets

Give your account ID, verified email or ticket number. Do not include your password, CVV, one-time code, seed phrase or full card number.

3. One disputed event

Describe the action neutrally:

• a withdrawal request was submitted;
• a round was settled in a certain way;
• a bonus received a certain status;
• the account was restricted;
• a payment appears twice;
• a KYC request was rejected.

If there are several problems, show how they are connected or create separate sections. Do not mix an unauthorised payment, a game result and a bonus into one accusation.

4. A short timeline

The key events are enough:

Always state the time zone. The square brackets are fields for you to fill in, not data from a real case.

5. The rule

Refer to the full document, the clause, the URL and the date you saved it. Do not pull a single phrase out of context. If you do not know which version applied on the date of the event, ask for it directly.

6. Evidence

Make an index of attachments:

• A01, transaction history;
• A02, saved terms;
• A03, correspondence;
• A04, account status;
• A05, calculation or timeline.

In the text, explain what each file confirms. Do not make the reviewer hunt for the key frame in a long screen recording.

7. A specific request

Ask for an action that can be carried out and checked:

• confirm the status;
• show the calculation;
• state the clause applied;
• correct a specific record if the check confirms an error;
• give a reasoned written reply;
• name the further route.

Do not demand guaranteed compensation without an established basis.

The “fact, source, question” formula

Every disputed point can be checked with this structure:

• Fact: what can be seen in the account or document.
• Source: which file and identifier confirm it.
• Question: what the operator needs to check.

Example:

In the account history, request [ID] has had the status [status] since [date and time], as shown in attachment A01. Please confirm the current stage, state the time limit applied from the Withdrawal Policy and indicate the next step.

A poor version:

You stole the money on purpose and you are stalling.

The second sentence attributes a motive and a legal characterisation but gives nothing to check.

Full complaint template

Subject: Formal complaint regarding [type of transaction] [ID].

Account: [account ID].

Summary: on [date, time, time zone], [one neutral description of the event] took place. Disputed amount or stake: [value and currency], transaction: [ID].

Timeline:

1. [date and event];
2. [date and event];
3. [date and event].

Rules: I refer to [document title, clause, URL, date saved]. If a different version was in force on the date of the event, please provide it.

Evidence: A01 [what it confirms], A02 [what it confirms], A03 [what it confirms].

I ask you to: check the transaction against the internal log; show the calculation and the clause applied in writing; tell me the decision and the further route if this is a final reply.

Please confirm receipt of this complaint and assign it a reference number.

Before sending, delete any fields that are not relevant to the case. Do not leave empty brackets.

What to attach and what to keep

Attach

• the relevant statement or history;
• the saved rules;
• a screenshot of the status;
• the written reply;
• a compact timeline.

Keep

• unaltered original files;
• the full archive of correspondence;
• a backup copy;
• data that was not requested;
• sensitive documents until a secure channel is confirmed.

Before sending, mask unnecessary numbers and data in the copy, but do not change the actual content. Keep the original separately.

The tone that helps the review

Write calmly and specifically. You can be firm without threats:

• “Please apply the formal complaints procedure”;
• “Please reply to each point”;
• “I cannot match the calculation to the clause of the rules”;
• “Please provide the version of the terms as of the date of the event”;
• “Please confirm whether this reply is final”.

Do not use insults, mass emails to staff or promises of a public attack. This does not strengthen your evidence and can make communication harder.

Deadline and reminder

First, rely on the deadline published by the specific operator. If there is no confirmation of receipt, repeat the message through the official channel and attach the original complaint.

For a British licence, the full internal process must be completed within eight weeks at most, or sooner if a final position is reached. This is confirmed by the current UKGC guidance on time limits. Do not apply the eight weeks to another licence.

How IPU.bet can help

IPU.bet can help separate facts from assumptions, build an index of attachments and make your request verifiable. Under the current Terms of Use, Player Support is an information and organisational service, not ADR and not legal representation.

IPU.bet does not guarantee a reply, a payout or a decision in the player's favour. For an initial review, do not share your password, one-time codes, full card numbers or unnecessary documents.

Help from IPU.BET

Key points to remember

A good complaint briefly links the account, the transaction, the time, the rule, the evidence and one request. It lets a staff member open the log and check the event you describe.

Keep the version you sent, the complaint number and the confirmation of receipt. Do not replace facts with accusations and do not send access secrets.

18+. Play responsibly. Gambling is not a way to make money.

Fill in the template, delete unnecessary fields and put together an index of attachments. If you need the structure checked, open the IPU.bet request form.