A player message becomes a complaint when the player is unhappy with something the operator did or failed to do and expects it put right, whatever words they use. In a UK-licensed casino complaint handling process, your support team has to apply that test to every ordinary live chat and email, because players rarely type “formal complaint”. Most operators fall down at recognising the complaint, not at answering it. Pitbot keeps complaints with a person, but the rule that decides what counts as one has to be yours.
- Short answer: Treat any message that expresses dissatisfaction and expects the operator to act as a complaint, log it at once, and give it to a named person.
- First step: Write a one-sentence definition of a complaint into your policy and put it in front of every agent and every reviewer.
- The goal: No complaint sits in the queue as a routine query, every one has a received timestamp, and no open complaint reaches its eight-week point unnoticed.
Tips: Test your recognition rule on last month’s closed chats before you roll it out: the complaints you find hiding in them show you where the rule is too narrow.
Key takeaways
The thesis is simple: the weak point in complaint handling is the moment of recognition. A support queue needs its own rule for spotting, logging and routing complaints, and that rule cannot depend on the player’s wording.
| Point | Detail |
|---|---|
| Recognition | A message is a complaint when the player expresses dissatisfaction and expects the operator to put something right, whatever words they use. |
| Intake record | The moment an agent flags a complaint, the queue records the date and time received, the channel, the player and the issue in the player’s own words. |
| Routing | A flagged complaint goes to a named person, and no automatic reply goes out on that conversation in the meantime. |
| The clock | The eight-week point for offering ADR runs from receipt, so a complaint missed at intake leaves you late for a deadline you never knew had started. |
Table of Contents
- Step 1: Define a complaint in your policy, not in the player’s words
- Step 2: Write the recognition rule for ordinary messages
- Step 3: Log it at intake and start the eight-week clock
- Step 4: Route it to a person and stop the automatic reply
- Step 5: Let AI draft and review, but keep the person on the response
- Step 6: Track the eight weeks and offer ADR on time
- Frequently asked questions
- Sources
Step 1: Define a complaint in your policy, not in the player’s words
Your complaint policy should define a complaint by what the player is saying, not by a phrase the player must type. The licence condition asks for a policy for accepting and handling complaints in a timely, fair, open and transparent way. A policy that only wakes up when someone writes “formal complaint” does not meet that standard, because the player has no way of knowing the phrase matters.
The condition, LCCP 6.1.1 on complaints and disputes, also expects clear information for players on how to complain, the timescales and the escalation route. It requires ADR to be offered if a complaint is unresolved after eight weeks, and it says records should be available to the Commission on request. Every one of those obligations depends on the same upstream event: someone at your company noticing that a complaint has arrived.
A workable definition has three parts. First, the player is dissatisfied with something the operator did, failed to do or decided. Second, the player expects the operator to respond or put it right. Third, the channel and the wording do not matter. Live chat, email, Telegram and SMS all count, and so does a message that begins as a question and turns into a grievance two lines later. Your compliance officer should sign off the exact wording, since it is your policy and your licence.
Without a written definition, every agent invents their own. One treats a sharp tone as the trigger, another waits for a threat to go to the regulator, a third logs only what arrives by email. The inconsistency stays invisible until an auditor samples closed conversations and finds the same kind of message handled three different ways. That is a policy failure, not an agent failure, and it is cheap to fix on paper.
Put the definition where agents work, not only in a policy PDF. If you run support through a queue that handles live chat and other channels together, as described on our online casino customer support page, the definition belongs in the same place as your escalation rules.
Step 2: Write the recognition rule for ordinary messages
The recognition rule is short: dissatisfaction plus an expectation that the operator will act. Give it to agents, and to any AI drafting for them, in exactly those terms. The same topic can be a query in one message and a complaint in the next, so the topic never decides. The player’s stance does.
The player-facing advice on this subject, such as this guide to escalating a casino complaint, frames a complaint as something that depends on the player’s wording. That is useful context for players and a poor foundation for a support desk. Your agents should not wait for magic words that the player may never learn.
Here are three common topics, each read two ways. The messages are invented for illustration.
| Topic | Reads as a query | Reads as a complaint |
|---|---|---|
| Delayed withdrawal | ”Hi, how long does a withdrawal usually take?" | "My withdrawal has been pending for six days and nobody has told me why. I want this sorted.” |
| Closed account | ”Can you tell me why my account shows as closed?" | "You closed my account without warning and I think that was wrong. I want it reopened.” |
| Bonus dispute | ”Does the welcome bonus have a wagering requirement?" | "The bonus was never credited and I was told it would be. I expect it added to my balance.” |
The left column asks for information. The right column says something went wrong and names what the player wants done. Tone is a weak guide: an angry player can ask a plain question, and a calm one can write a perfectly clear complaint. Sentiment signals can prompt a second look, as we discuss in sentiment escalation with human review first, but they flag mood, not obligation.
When in doubt, log it as a complaint. A wrongly logged complaint costs a few minutes to close; a missed one costs a late ADR offer.
That asymmetry is the whole argument for resolving doubt in one direction. Build it into the rule as an instruction, not a suggestion: if an agent hesitates, the answer is to flag it and let the complaint handler decide it is only a query. Agents who fear over-reporting will under-report, so say plainly that over-flagging is the safe error and nobody is marked down for it.
Step 3: Log it at intake and start the eight-week clock
The moment an agent flags a complaint, they record five things, and the received timestamp is the one that matters most. The eight-week point for offering ADR is counted from receipt, so a missing or wrong timestamp makes every later date in the file unreliable. Records should also be available to the Commission on request, which means the entry has to be complete when it is written, not reconstructed weeks later.
Use this intake sequence:
- Record the date and time received. Use the time the player’s message arrived in the queue, not the time the agent read it.
- Record the channel. Live chat, email, Telegram or SMS, so the original message can be found again.
- Record the player. Use the full player ID, not a shortened display version, so anyone can find the same account.
- Record the issue in the player’s own words. Quote the message. Do not paraphrase it into something milder or more convenient.
- Record who it was passed to. Name the person, not the team.
Here is a short, invented example. A player writes to live chat at 21:40 on a Friday: “That’s the third time I’ve asked about my deposit bonus. Nobody has fixed it and I want it credited.” An agent could easily answer with the bonus terms and close the chat. Under the rule from Step 2, the agent flags it instead. The entry carries Friday’s date and 21:40, the channel, the player ID, the quoted sentence and the name of the complaint handler who picks it up on Monday morning. The eight weeks start on Friday, not Monday.
The complaint register itself lives in your own system, whether that is a case tool, a compliance platform or a controlled spreadsheet. The support tool points to the register entry; it does not replace it. Keep one source of truth, and make sure the reference is visible from the conversation so nobody has to search for it. For what a complete record looks like more broadly, see our piece on the fields a compliance audit trail must record.
Tips: Make the intake fields mandatory in the form that creates the register entry, so an agent cannot save a complaint without the received time and the player’s quoted words.
Step 4: Route it to a person and stop the automatic reply
Once a conversation is flagged as a complaint, it moves to a named owner and nothing automated answers on it. This is the handover rule, and it is deliberately blunt. A complaint that receives a templated reply from a bot, however polite, tells the player their grievance was processed as a routine query, and it puts words in the operator’s mouth before anyone has looked at the facts.
In Pitbot, complaints are a topic that goes to a person. Auto-send is off for every new brand, so by default no message resolves on its own, and each operator decides what, if anything, may go out unattended. Our article on human-in-the-loop AI for player support covers the reasoning behind that split, and the responsible gambling documentation describes the sensitive topics that follow the same path.
Set the handover out as a rule your team can follow without thinking:
- Name the owner. Every flagged complaint has one person responsible, written on the register entry. A shared inbox is not an owner.
- Freeze automated replies. No automatic reply goes out on the conversation while the complaint is open. If your brand has auto-send switched on, check the small-talk setting under Message Config, because a one-line greeting reply can still be sent on an escalated conversation.
- Show the handler the player. The receiving person works from the conversation panel and the player sidebar, which shows the player’s profile and activity, so they see the history before they write a word.
- Keep the conversation visible. The stats bar counts Escalated and Needs Review conversations, which gives the team lead a live view of what is waiting.
- Add a pointer. Put the register reference where the next agent will see it, such as a player note on the profile, so a second contact from the same player is not treated as a fresh query.
The failure this prevents is quiet and common: a complaint is flagged, then the player writes again an hour later and a different agent, or an automated step, answers as though nothing had happened.
Step 5: Let AI draft and review, but keep the person on the response
AI helps once the complaint is with a person, and the decision and the final wording stay with the complaint handler. The useful jobs are narrow: drafting an acknowledgement for the handler to edit, bringing the player’s history into view, and holding any reply for approval before it reaches the player.
An acknowledgement is a good candidate for a draft. It confirms receipt, says who is handling the matter and sets out the next step, and the wording is largely predictable. Pitbot can prepare that draft, and a person can review it before the player sees it. The substance of the response, what the operator concedes, offers or declines, is a decision about a licence obligation. A draft can propose language. It cannot take responsibility.
The review step matters as much as the draft. Pitbot’s quality check scores each draft, and anything below 70 goes to Needs review for an operator. A draft that scores 70 or higher still only goes to the player automatically if Send AI replies without approval is on, and otherwise it waits for a person. For complaint conversations, the practical rule is that every reply waits for the handler, whatever the score. Our guide to an AI reply review workflow for iGaming sets out how to stage that review, and the features page shows how drafting, review and human takeover fit together.
The recognition rule and the register belong to you.
Tips: Ask handlers to edit AI-drafted acknowledgements at least once a month against your complaint policy wording, so the template never drifts from what you can actually promise.
Step 6: Track the eight weeks and offer ADR on time
ADR must be offered when a complaint is still unresolved at eight weeks, and earlier if the complaint reaches deadlock. The Gambling Commission’s ADR requirements also say the clock may pause in certain circumstances, that ADR is free to the player, and that operators should answer ADR information requests within ten working days.
The page carries an update note about the Digital Markets, Competition and Consumers Act 2024 (DMCC Act 2024). Read the current version before you finalise your own timings, and have your compliance officer confirm the position, since this article cannot know what has changed since it was written.
Turn that into a routine your team can run:
- Diarise the point on day one. When the register entry is created, calculate the eight-week date from the received timestamp and write it on the entry.
- Record any pause. If the clock is paused, note the reason, the dates and who approved it, so the adjusted date can be defended.
- Treat deadlock as a trigger. If the complaint reaches a point where no resolution is possible, the ADR offer does not wait for week eight.
- Make the offer in writing. Keep a copy with the date, and make clear that ADR is free for the player.
- Set a ten-working-day target. Any ADR information request is answered inside that window, with an owner named in advance.
- Run a weekly check. Once a week, list every open complaint with its eight-week date and flag any approaching its point, so none surprises you.
Escalation inside the business matters here too. A complaint that touches a regulatory issue should reach compliance on a defined route, and our one-page escalation matrix is a practical way to set that out. The weekly check is deliberately dull. Its job is to make sure the only complaints that reach week eight are the ones you chose to leave open, never the ones you did not realise had started.
Frequently asked questions
Does a player have to say ‘formal complaint’ for it to count? No. Your policy should define a complaint by what the player is expressing, dissatisfaction with an expectation that you will put it right, and not by a phrase. Players do not know the phrase matters, so a rule that depends on it will miss most complaints.
When does the eight-week clock start? The eight-week point for offering ADR runs from the moment the complaint is received. That is why the received timestamp at intake matters. Check the current Gambling Commission guidance on pauses and on the DMCC Act 2024 before you finalise your timings.
Can an AI-drafted reply go out on a complaint? Our recommendation is that no automatic reply goes out on a flagged complaint. In Pitbot, complaints are a topic that goes to a person, and auto-send is off for every new brand. A draft can help the handler, but the handler reviews and sends it.
What should we record when a complaint is logged? Record the date and time received, the channel, the player, the issue in the player’s own words and the person it was passed to. Keep the register in your own system, with the support tool pointing to it, so it is available to the Commission on request.
What if an agent treats a complaint as a routine query? Treat it as a process failure, not a disciplinary one, and log it from the date the message was originally received. Then review how it was missed and whether the recognition rule or the training needs to change. Resolving doubt towards complaint keeps this rare.
Sources
- Gambling Commission: LCCP 6.1.1 Complaints and disputes
- Gambling Commission: Complaints and disputes, ADR requirements
- OLBG: Casino Complaint Escalation UK
