Live chat replies in 90 seconds; the email sits 4 days

A test of 14 licensed operators found live chat answered in a median 92 seconds, while email tickets sat for four days before a human replied. The gap wasn't a staffing quirk at one or two brands. It held across every operator tested, in three languages, over a two-week window in March.

That number matters more than most support metrics because it tells you where the real support desk lives. Not in the inbox. In the chat window, where the operator can still influence whether you deposit, withdraw, or leave.

Why live chat wins by default

Live chat is cheap per contact and expensive per resolution. A single agent can juggle three or four concurrent chats; the same agent handles one email at a time. That math pushes operators to route volume into chat and treat email as overflow. The 4-day median isn't neglect — it's triage.

There's a second reason. Chat keeps you on-site. Email sends you away, and a player who leaves to check their inbox is a player who might not come back that session. Chat is a retention tool wearing a support badge.

The practical effect for you: if your issue is time-sensitive, chat is the only channel with a realistic shot. If it needs documents, screenshots, or a paper trail, chat is often the wrong tool — agents will tell you to email anyway, and now you've burned 90 seconds to be told to wait four days.

What "90 seconds" actually measures

First response, not resolution. The test counted the time until a human (or a human-sounding bot) sent a substantive reply. Median first response: 92 seconds. Median resolution in chat: 11 minutes for simple queries, and effectively never for anything involving a payment dispute — those got kicked to email 71% of the time.

So the headline number is real, but read it precisely. Fast hello, slow fix.

The four-day email isn't uniform

The 4-day figure is a median, and the distribution is ugly. Simple account questions — password resets, bonus code errors — often came back inside 12 hours. Anything touching withdrawals, KYC, or self-exclusion dragged. The slowest single reply in the test was 9 days, on a document verification query at a mid-sized operator.

That split is predictable once you know how desks are staffed. Front-line chat agents handle the easy 80%. The remaining 20% — the disputes, the escalations, the compliance-sensitive stuff — lands with a smaller, slower team that also handles regulatory correspondence. Your withdrawal question is queuing behind a licensing matter.

The compliance angle nobody advertises

Some of the delay is deliberate. Operators are required to investigate certain complaints, keep records, and respond in writing. A 4-day turnaround on a disputed withdrawal isn't always laziness — it's a paper trail. Chat doesn't produce one cleanly, which is part of why agents push you to email the moment things get serious.

If you're in a jurisdiction with a formal complaints process, that email timestamp is your evidence. Screenshot the chat, but send the email.

What the gap means for how you use support

Treat the two channels as different products.

Chat is for: confirming a bonus is active, asking why a withdrawal is pending, checking whether a document was received, anything you want answered in the next two minutes.

Email is for: disputes, anything you might escalate to a regulator, requests where you need a written record, and issues that will take more than one message to resolve.

The trap is using chat for something that needs email, getting a fast "we'll look into it," and assuming it's handled. It isn't. A chat agent closing the window is not a ticket. If you don't have an email reference number, you don't have a case.

One more thing worth doing: send the email first, then open chat and reference the ticket number. You get the speed of chat and the timestamp of email. Agents can pull the ticket and often resolve it faster because the paper trail already exists.

Where the numbers get uncomfortable

The 92-second median hides a long tail. In the test, 8% of chat sessions got no human reply at all — just a bot loop that never escalated. Those sessions averaged 6 minutes before the tester gave up. Meanwhile, the operators with the fastest chat also had the slowest email, which suggests the same resource being pointed at whichever channel leadership cares about this quarter.

There's a responsible gambling dimension here that operators rarely put in the support brochure. A player trying to activate a self-exclusion or a deposit limit is, by definition, in a time-sensitive situation. If that request routes to a 4-day email queue, the delay is doing real harm. The better operators route RG requests to chat or a dedicated line. The test found 5 of 14 doing this. The rest treated it like any other ticket.

That's the number I'd want to see published before any others.

So which channel should you trust?

Neither, fully. The 90-second chat reply is genuine, and it's genuinely useful for the 80% of questions that are simple. The 4-day email is also genuine, and for the 20% that matter most — money, documents, disputes — it's the only channel that counts.

The open question is whether the gap is a staffing problem or a design choice. Operators could staff email better. They mostly don't, because chat keeps you on the page and email doesn't. As long as that's true, expect the split to hold: instant greetings, slow answers, and a support experience that's fast exactly where it's cheap to be fast.

If you're mid-dispute and the chat agent is typing, ask yourself which channel you're actually in. The reply will come in 90 seconds. The resolution might come in four days — or not at all.