Good complaint management in gambling means three things: a written process players can find, fixed clocks you can prove you met, and a record of every decision. In Great Britain those clocks are set by the Gambling Commission. Other regulators set their own, so the safest design is one process that meets the strictest rule you operate under.
This guide is for operators, compliance officers and support leads. It covers what counts as a complaint, how to receive and investigate one, what to record, when to hand a case to an independent adjudicator, and how to check that your team handles cases consistently.
TL;DR
- A complaint is any expression of dissatisfaction about the conduct of your licensed activities. It does not need to use the word “complaint”.
- In Great Britain, acknowledge within three working days (24 hours for 24-hour facilities) and finish the whole process within eight weeks.
- Log every complaint not resolved at first contact, keep the records, and be ready to give them to the regulator on request.
- After eight weeks, or at deadlock, the player can go to an approved ADR provider. You cannot restrict their right to go to court.
- Sample your own replies for accuracy, and route responsible gambling and payment cases to the front of the queue.
Table of Contents
- What counts as a complaint
- The clocks you have to meet
- Receiving and acknowledging a complaint
- Categorising and prioritising
- Investigating fairly
- Records and evidence
- When to hand over to ADR
- Oversight and audit controls
- Measuring and improving quality
- Our perspective
- How Pitbot supports a complaints process
- Common mistakes to avoid
- FAQ
- Sources
What counts as a complaint
The Gambling Commission defines a complaint as an expression of dissatisfaction made to a licensee about any aspect of the conduct of licensed activities. Two things follow from that wording.
First, the player does not have to say “I want to complain”. A message that says a withdrawal has been held for nine days and nobody has replied is a complaint. So is a frustrated live chat about a bonus that did not credit. Your agents, and any AI tool you use, need to recognise dissatisfaction by its content, not by a keyword.
Second, complaints resolved at the first stage need not be recorded for the regulator’s returns. That is a reporting rule, not a licence to ignore them. Plenty of operators still keep their own record of first-contact fixes, because that is where they learn which journeys fail.
Typical subjects include:
- Delayed or declined withdrawals and verification checks
- Bonus terms and wagering disputes
- Game malfunctions and voided bets
- Account closures, restrictions and self-exclusion handling
- Marketing sent to a player who opted out or who should have been suppressed
- Staff conduct and response speed
The clocks you have to meet
The Gambling Commission’s complaints and disputes requirements of December 2020 set the timeframes for licensed operators in Great Britain. Here they are next to the Ontario standard, for operators who work in both markets.
| Step | Great Britain | Ontario (iGaming Ontario) |
|---|---|---|
| Right to complain | At least six months from the date of the incident | See the regulator’s standards |
| Acknowledgement | Within 24 hours for 24-hour facilities, otherwise within three working days | Within one business day |
| Complete internal process | No more than eight weeks from receipt, unless the customer fails to engage | See the regulator’s standards |
| Referral to ADR | After eight weeks, or sooner at deadlock | See the regulator’s standards |
Sources: Gambling Commission requirements and iGaming Ontario’s service standards.
The practical lesson is to design to the shortest clock. If you serve several jurisdictions, set your acknowledgement target at one business day everywhere. It costs little and removes the need for agents to remember which rule applies to which player.
The eight weeks include internal escalation. If a first-line agent sits on a case for three weeks and then passes it to a manager, the manager has five weeks left, not eight. Build your workflow so the clock is visible on every case.
Receiving and acknowledging a complaint
Players complain wherever they already talk to you: email, live chat, SMS, social messages, Telegram. A process that only accepts complaints through a web form will miss a large share of them and breach the principle that the process must be accessible. The Commission’s guidance calls for a clear, written and accessible complaints process, so publish it where players log in and link it from every support channel.
What a good acknowledgement contains
Keep it short and in plain language. It should include:
- A reference number the player can quote
- A restatement of the complaint in one sentence, so the player knows you understood it
- The name or team of the person handling it
- When the player will next hear from you
- What happens if they are not satisfied, including the ADR route and its timing
One operator-side policy, from a Curaçao-licensed casino’s published dispute procedure, promises an initial expected timeline or next-update target, normally within seven days. That is a useful habit even where the law does not demand it: a player who knows the next date is far less likely to chase you.
Incomplete complaints
Sometimes you cannot act on what you have been given. The same published policy lets the operator ask for more information in writing and close the case if the complainant stays silent for five business days. If you adopt something similar, state the rule in your own procedure, ask clearly for the specific missing item, and note that the Commission’s eight-week limit applies unless a customer fails to engage. Record each request and each silence, because you will need that evidence if the player later says nobody asked.
Categorising and prioritising
Not every complaint deserves the same speed. Sort each one on arrival by subject and by risk. A simple scheme works:
| Priority | Examples | Handling |
|---|---|---|
| Urgent | Signs of gambling harm, self-exclusion failures, account security, unauthorised payments | Same day, senior reviewer, suppress marketing to that player |
| High | Withdrawal delays, VIP player disputes, repeated contact on the same issue | Within one working day, named owner |
| Standard | Bonus terms, game queries, general service | Normal queue, clock visible |
The published policy mentioned above notes that complaints involving responsible gaming, account security or payment issues may be prioritised or escalated immediately. That fits what most compliance teams already do. A complaint from a player who is also showing risk markers is a safer-gambling event first and a service event second. Read more on that link in our page on responsible gambling automation.
Tag every case with one primary category. Free-text reasons are useful, but only fixed categories let you count trends. Review the category list quarterly so “other” never becomes your biggest bucket.
Investigating fairly
Investigation is where most complaints are won or lost, and where consistency matters most. A workable sequence:
- Gather the facts. Account history, transaction logs, game round data, chat and email transcripts, and the terms the player accepted at the time.
- Separate the claim from the evidence. What exactly does the player say happened, and what do your records show?
- Apply your terms and the rules consistently. Compare against how similar cases were decided. Inconsistent outcomes are what players and adjudicators notice.
- Decide, with reasons. Write the decision in language the player can follow, with the clause or fact it rests on.
- Offer the next step. If you uphold only part of the complaint, say so, and explain the ADR route in the same message.
Whoever investigates should not be the person whose conduct is being complained about. For anything involving staff behaviour or a large payout, a second reviewer should check the draft decision before it goes out.
Records and evidence
The Commission’s guidance says operators must keep records of formal complaints and disputes and make them available to the Commission on request. Separately, the regulatory returns guidance expects you to log complaints that occur in the reporting period, whatever the outcome, provided they were not resolved immediately at the first stage.
In practice, a complete case file holds:
- Date and time received, channel, and who received it
- The complaint in the player’s own words
- Category, priority and the deadline clock
- Every message sent and received, including the acknowledgement
- Evidence reviewed: transactions, game logs, verification documents, terms version
- Who handled the case, who reviewed it and when
- The outcome, the reasons, and any redress given
- A closure status and summary of actions. One published operator policy requires the case owner to update the management system with exactly that on closure.
A complete file is also your best defence. If an ADR provider asks why a decision was made, you want to answer in minutes from one place, not by hunting across inboxes. Our article on the player record components operators need goes into how to keep one record across channels.
When to hand over to ADR
In Great Britain an unresolved dispute can go to an approved ADR entity after eight weeks, or earlier if the customer and operator reach deadlock. Two points matter:
- Tell the player. Your final response, or the eight-week letter, should name the ADR provider you use and explain how to reach it.
- Do not block the court route. Licence holders must not subject ADR services to terms that remove or restrict a customer’s right to bring court proceedings.
The Commission has described the wider structure in its paper on complaints processes in the gambling industry: the operator, the ADR provider and the Commission each have a distinct role, shaped by UK ADR regulations and the licence conditions. The Commission does not usually decide individual disputes. That is the ADR provider’s job, and the Commission looks at patterns in how operators behave.
Outside Great Britain the route differs. Ontario sets its own service standards for complaints and disputes, and other regulators have their own bodies. Map each licence you hold to its escalation path and keep that map next to your procedure.
Oversight and audit controls
A written procedure is not oversight. Oversight is evidence that the procedure was followed on this case, by this person, on this day. Controls that work:
- Clock alerts. Warnings at day two of the acknowledgement window and at weeks four and six of the eight-week window.
- Second-line review. Compliance samples closed cases each month for correct categorisation, fair outcomes and plain-language replies.
- Escalation triggers. Automatic referral to a senior reviewer for urgent categories, repeat contacts and high-value players.
- Management information. Monthly counts by category, channel, outcome and time to close, reported to the person accountable for compliance.
- Root-cause actions. Every spike in a category produces an owner and a fix, such as clearer bonus wording or faster verification.
Measuring and improving quality
Speed alone is a poor measure. An Australian regulator’s guidance on complaints monitoring, written for telecoms but applicable in principle to any complaint-heavy service, recommends quality management that measures accuracy and defect rates through unbiased statistical sampling of interactions. Take the method, not the sector: pick a random sample of closed cases each month and score them against a short checklist.
A useful checklist asks:
- Was the complaint recognised and logged correctly?
- Was the acknowledgement on time and in plain language?
- Did the decision cite the facts and terms?
- Was the ADR route explained where it applied?
- Was any vulnerability signal acted on?
Also watch first-contact resolution. A customer-operations standard notes that solving problems at the first contact leads to fewer repeat transactions and a lower staffing requirement. In gambling, every repeat contact about the same withdrawal is also a step toward a formal complaint.
Our perspective
We build support software for online casinos, and the pattern we see is consistent: complaints rarely start as complaints. They start as an ordinary support question that was answered slowly, answered wrongly or answered without noticing the player’s mood. By the time it is formal, the cheap fix has gone.
That is why we think the safest design puts a person between the AI draft and the player. Pitbot drafts replies using several AI providers, and a member of your staff reviews every reply before it is sent. Speed comes from the draft; judgement and accountability stay with your team. Every decision lands in an audit trail, which is the thing a regulator or ADR provider will ask for.
We also think sentiment detection matters more than most operators expect. A message that reads as angry, or that hints at gambling harm, should leave the normal queue and reach a senior person with marketing suppressed. Detecting it early is cheaper than investigating it later.
Our view is that complaint management is not a separate department. It is the end of the support process, and the better the support process, the less often you reach it.
— pitbot
How Pitbot supports a complaints process
Pitbot is an AI player support platform for online casino operators. It brings email, live chat, SMS and Telegram into one workspace. Replies are human-reviewed, sensitive cases escalate automatically, VIP queues are managed separately, and the audit trail records each decision. Responsible gambling detection can suppress outreach to at-risk players. We do not publish a price, so book a demo to see how it would fit your process.
See AI customer support for online casinos for the full picture, or browse the platform features. For the compliance angle in more depth, read our 90-day compliance communication plan, and for the SMS channel in particular, our guide to SMS support compliance.
Common mistakes to avoid
- Treating only formal letters as complaints. The definition is about dissatisfaction, not wording.
- Starting the eight-week clock late. It runs from receipt, not from when the case reached the right team.
- Burying the ADR route. Name the provider and explain the process in the final response.
- Inconsistent outcomes. Similar cases should end the same way, and the reasons should be on file.
- Marketing during an open complaint. A promotional message to a player who is disputing a withdrawal, or showing harm signals, invites a second complaint.
- Keeping records in several places. One case, one file, across all channels.
FAQ
How long does a UK-licensed operator have to resolve a complaint?
The whole process, including internal escalation, must take no more than eight weeks from receipt, unless the customer fails to engage. After that, or earlier at deadlock, the player can refer the dispute to an approved ADR provider.
How quickly must we acknowledge a complaint?
In Great Britain, within 24 hours for 24-hour gambling facilities and within three working days otherwise. Ontario’s standard is one business day. Setting a single one-business-day target across markets is the simplest approach.
Do we have to record every complaint?
You must keep records of formal complaints and disputes and provide them to the Commission on request. Complaints resolved at the first stage need not be recorded for the regulatory return, though many operators keep them anyway to spot trends.
How long can a player wait before complaining?
Gambling Commission guidance says operators must allow customers to raise a complaint for at least six months from the date of the incident. Your procedure should say so.
Can AI handle gambling complaints?
AI can draft replies, sort cases and flag sentiment quickly. Because the accountability stays with the licensee, a human should review what goes to the player, and the decision trail should be kept.
Sources
- Gambling Commission: complaints and disputes procedural, information provision and reporting requirements (December 2020)
- Gambling Commission: regulatory returns guidance, operational information
- Gambling Commission: complaints processes in the gambling industry
- iGaming Ontario: complaints and disputes service standards
- Crypto.Games: policy for handling dispute resolutions
- ACMA: guidance on complaints monitoring and analysis
- COPC Customer Experience Standard, Release 7.0
