How to Complain to a Bookmaker: Step‑By‑Step Complaint Roadmap

Pick the medium with both speed and retrievability in mind

Different channels trade off speed and evidence quality. Written channels — email, support tickets, and chat transcripts — produce timestamps and text that are easy to save and attach to a formal complaint. Verbal channels — phone calls — can be fast but are harder to prove unless a recording or written follow-up exists.

If live chat is slow, consult the guide to live-chat wait times to decide whether waiting or switching makes sense.

Quick practical rules

• Prefer email or support tickets for anything that may become a formal complaint. Save copies and BCC an archive address.
• Use live chat for fast triage but immediately request a transcript and screenshot the final screen.
• Use phone only for urgent stops (frozen bets, security). After a call, send an email summarising the conversation and ask the agent to confirm in writing.

When switching helps vs hurts

• Smart: switch when speed prevents further loss, then follow up in writing to create a record.
• Harmful: switch repeatedly between channels, which fragments evidence and weakens timelines. Consolidate every contact into a single, dated complaint record.

Quick template

Subject: Formal complaint — account [account number], bet reference [ID], date [DD/MM/YYYY]

Dear [Complaints team/Name],

1. Factual timeline (concise):

• [DD/MM] [HH:MM] — placed bet ID [####]; receipt screenshot attached.
• [DD/MM] [HH:MM] — outcome/error/interaction with agent [name], chat log attached.
• [DD/MM] [HH:MM] — attempted resolution via frontline support (reference [ticket #]).

2. Issue summary (one sentence):

• Clear statement of what went wrong and why it breaches the terms or policy.

3. Desired outcome (precise):

• Refund stake of £X and void bet, or full settlement of £Y, and written confirmation within 14 days.

4. Attachments (listed):

• Screenshots, transaction IDs, chat transcript, audio file (if applicable), proof of identity.

Why address the right person

Sending this to the named complaints handler or escalation manager speeds response, preserves escalation records and reduces repeated frontline rerouting. When frontline support fails, follow the steps in the guide to contact the complaint manager for escalation contact details and expected timelines.

Keep language factual, stick to documented times and amounts, and request a clear deadline for response.

Operators reject complaints for repeatable, fixable reasons. Use narrow, evidence‑first responses and start with the practical tactics to force a proper review.

Narrow, immediate tactics

• Insufficient evidence. Provide a one‑line timeline (UTC), transaction IDs and annotated screenshots; attach the original chat transcript and highlight the exact quote.
• Deadline or delay alleged. Show email headers/file metadata or device timestamps; ask for discretion if evidence was preserved on time.
• T&Cs cited as blanket defence. Quote the specific clause, explain how its application here is inconsistent, and point to the operator’s own rule examples.
• Settlement or grading error. Request a manual re‑grade, provide third‑party event feeds or video stills if available.

If the first reply is unsatisfactory, explicitly request a written internal review before considering external escalation.

Escalation becomes appropriate after a clear internal attempt has failed: a formal complaint submitted, a reasoned response from the bookmaker, and either no remedy or an unsatisfactory outcome.

Minimum internal history to keep:

• the original formal complaint and its date;
• the bookmaker’s written response(s) and reference numbers;
• all supporting evidence (timestamps, transaction IDs, screenshots, chat logs, agent names).

What an external adjudicator needs

• a concise chronology of events;
• copies of the formal complaint and the bookmaker’s replies;
• the primary evidence items listed above;
• any relevant terms or rules cited in the dispute.

If internal steps fail, follow the formal escalation process to IBAS.

Realistic timelines and outcomes

• Internal response: often 7–28 days; escalate if unresolved after ~8 weeks.
• Ombudsman review: commonly 4–12 weeks depending on complexity.
• Outcomes: fully upheld, partially upheld, or rejected — typical remedies are refunds, stake returns, or no redress.