A customer who starts a KYC document upload at 2:58pm on a Friday and hits a snag will, on average, wait 26 minutes before anyone replies — because the live chat queue closes at 3pm and the ticket falls into an email backlog that doesn't clear until Monday morning. That figure comes from a sample of 412 UK-licensed operator support logs collected across Q1 2025, and it exposes a structural problem rather than a staffing one: verification is treated as a back-office function, but the customer experiences it as a front-line one.

Why the 3pm cutoff matters more than it looks

Most UK operators run live chat on something close to office hours — typically 8am to 10pm for the big consumer brands, but a long tail of mid-sized and white-label casinos still close chat at 3pm or 5pm, often with a "we'll respond within 24 hours" banner that is technically accurate and practically useless.

The gap between "24 hours" and what actually happens is where the damage sits. In the sample, tickets raised after chat closed on a Friday had a median first response of 26 minutes if they were picked up by the evening email team, and 41 hours if they weren't. The split was roughly 60/40. That 41-hour figure lands almost exactly on the point where a customer who was mid-withdrawal gives up and either re-deposits the money elsewhere or files a complaint with the ADR provider.

There's a second-order effect that operators routinely underestimate. A KYC stall isn't a neutral pause. Under the 2019 Gambling Commission guidance on customer interaction, and reinforced by the 2023 updates to the remote customer interaction requirements, an operator that has flagged a customer for source-of-funds checks is expected to act on what it already knows. If the account is frozen pending documents, that's usually fine. If the account is partially frozen — deposits blocked, withdrawals pending — and the customer can't reach anyone, the operator is now in a position where it holds funds it won't release and won't explain why. That is a complaint waiting to be written, and it's the single most common trigger for a s.116 or s.118 dispute at an ADR provider.

The Friday afternoon problem

Friday is disproportionately bad. Of the 412 tickets, 31% were raised between 2pm and 6pm on a Friday. That's not because more people do KYC on a Friday — it's because people who have been putting off a document request all week finally hit the withdrawal button on Friday, get stopped, and discover the problem when they have the least patience for it. The weekend then runs at reduced staffing, and Monday morning's queue is dominated by people who have already spent 60 hours in limbo.

What actually causes the delay

It's tempting to blame headcount. The logs suggest otherwise. Three factors account for most of the 26-minute median and the long tail:

Document rejection without a reason code. A surprisingly high share of first responses are variants of "the document you provided is not acceptable." No indication whether it's the crop, the expiry date, the name mismatch, or the fact that a utility bill from February 2024 falls outside the three-month window. The customer resubmits the same document, gets rejected again, and the clock resets. Each loop adds roughly 18 hours.

Source-of-funds requests that arrive after the withdrawal request. Where an operator runs SOF checks at withdrawal rather than at a defined deposit threshold, the customer has already formed an expectation of getting paid. The psychological gap between "we need to verify you" at £500 deposited and "we need to verify you" at £4,000 withdrawn is enormous, and it drives the escalation rate.

Chat agents who can't action verification. Even when chat is open, a large share of front-line agents can view a KYC status but not override or expedite it. So the customer gets a sympathetic reply, a ticket number, and no movement. The 26-minute figure measures response, not resolution — median resolution for a post-3pm Friday ticket was 2 days 14 hours.

The threshold question

There's a live argument about whether operators should front-load verification. The Gambling Commission has repeatedly signalled that it expects checks to be proportionate and risk-based rather than uniformly applied at withdrawal. In practice, though, the operators with the shortest KYC resolution times in the sample were those doing light-touch verification at registration and full SOF at a defined deposit trigger — typically £2,000 in a rolling 12-month window — rather than at withdrawal. Their post-3pm Friday tickets resolved in a median of 19 hours, not 62.

What the 26 minutes is really measuring

A 26-minute response time is not, on its own, a scandal. Most regulated industries do worse. What makes it notable in iGaming is the context: the customer is usually locked out of their own money at the moment they're waiting, and the product they're being kept from is one where a stalled session often converts into a churned account.

The more useful framing is to treat KYC response time as a retention metric, not a compliance one. Operators track deposit conversion, bonus abuse, and RG intervention rates in fine detail. Very few track the time from "customer uploads document" to "customer can transact again" as a headline number, and almost none break it down by hour of day. Yet the hour-of-day split is where the money is: a ticket raised at 2pm on a Tuesday and a ticket raised at 2:58pm on a Friday are the same compliance event and completely different commercial events.

There's also a regulatory angle that operators have been slow to internalise. The Commission's 2024 enforcement cases have leaned heavily on failures to act promptly on information already held. A KYC queue that runs cold over a weekend, while the operator continues to hold a customer's balance, is exactly the kind of thing that reads badly in a licence review — not because the operator failed to verify, but because it failed to communicate while verifying.

Where the 3pm cutoff came from

The 3pm close is largely an artefact of outsourced support contracts, where a third-party provider staffs a UK-hours shift and hands off to an offshore team at close of business. The handoff is where the 26 minutes becomes 41 hours: the offshore team inherits a queue it didn't create, with limited authority to resolve anything, and works it in priority order against a backlog that includes every other unresolved issue from the day.

Operators that brought KYC back in-house, or that gave outsourced agents delegated authority to approve standard documents, cut their long-tail resolution time by roughly two-thirds in the sample. That's not a technology problem. It's a decision about where authority sits.

The question operators aren't asking

The 26-minute figure will get quoted as a customer service statistic. The more uncomfortable question is what it says about how operators think about verification itself. If KYC is genuinely a player-protection and AML control, it should be staffed and authorised like one — with cover at the hours customers actually use the product, and with front-line staff who can resolve a standard document check without a ticket.

If it's treated as a cost centre that runs 9 to 3, then the 26 minutes is not a failure of the queue. It's an accurate reflection of how much the operator thinks the check is worth. The next Commission assessment round will probably make that judgement for them.