PlayerDesk · The product we ship today

Your support should scale with your markets. Not with your headcount.

Tier-1 player support across chat, email and voice — with its own quality control built in.

PlayerDesk is three systems working together: an agent that resolves the routine majority 24/7 in 20+ languages, a quality-control layer that grades every conversation against your own QA protocol, and a detector that finds the players about to become VIP while they are still in the chat.

The money problem

A 24/7 support desk of 30–40 seats costs a mid-size casino €15–30K/month, and it is staffed for peak all year. Every new market adds native speakers, a training cycle and a night shift — paid for before you know whether the market is worth having. The alternative, slower response times, quietly kills conversion and retention.

Most "AI chatbots" make this worse rather than better. They resolve around a fifth of the queue from an FAQ, players learn to type "agent" as their opening line, and your team handles the same volume with the annoyance added. You pay twice.

What changes for you

The routine majority is resolved instantly, around the clock, in every language you sell in. Your agents keep the work that needs a person. And for the first time you can put a number on how well any of it was done — by the AI and by your team.

New markets without new hires

A new language is a configuration change, not a recruitment cycle. Test the market before you staff for it.

Cost per contact, not per seat

Volume growth, night coverage and holiday peaks stop translating one-for-one into payroll.

VIPs never get a bot

Known VIPs route straight to their manager. Players on their way to VIP get flagged to your team while still in the chat.

Quality with a number on it

Every conversation scored against your own QA protocol — the AI's and your agents', on the same scale.

Component 01

The support agent

PlayerDesk is a multi-agent system, not a single chatbot. Specialised agents handle intent triage, knowledge retrieval, action execution, VIP checks, escalation and real-time QA. Schema-Guided Reasoning keeps responses structured and predictable, which is what makes them auditable and what keeps hallucination down.

The difference a player notices is that it can do things. It reads your PAM: whether the deposit landed, where the withdrawal is, whether the documents passed, why the free spins did not trigger. That is most of an iGaming Tier-1 queue, and it is exactly the part a help-centre bot cannot reach.

"Why a routine chat gets resolved without a human — and a VIP never does."

Orchestrator Routes the message, coordinates agents, owns the decision flow
Triage AgentIntent, language, urgency, VIP check
Knowledge AgentFAQ, policies, rules, bonuses
Action AgentPAM / payments / KYC API calls
Escalation AgentHand-off to human + ready summary. VIP route always hits a human.
Response AgentGenerates the player-facing answer
QA AgentReal-time hallucination + tone check

Channels: live chat, email and inbound voice run on the same brain, the same knowledge and the same escalation rules — so a player gets the same answer whichever way they ask.

Component 02

Auto quality control

Every operator already has a quality protocol: a scorecard your QA lead works through — was the player greeted properly, was identity verified, was the policy quoted correctly, was the next step offered, was the case closed cleanly. And every operator applies it to a handful of conversations a week, because a human can only read so many.

PlayerDesk takes that same scorecard — yours, not ours — and applies it to every single conversation. The rubric your team already agreed on becomes a structured evaluation, run over 100% of chats, emails and calls instead of a weekly sample.

Your rubric, not a vendor's

We encode the protocol your QA team already uses. No new definition of "good" to negotiate internally.

Humans scored on the same scale

Your agents are graded by the same rubric as the AI, so the comparison is real and the coaching is specific.

It is the release gate

A topic goes to full automation only when its score clears a threshold you set — and rolls back automatically if it decays.

Drift is caught, not discovered

Score by topic, language and shift, tracked over time. A knowledge-base change that quietly broke an answer shows up the same week.

The honest part: who grades the grader?

An automated evaluator is only worth what its agreement with your own QA leads is worth. So the first thing built is a labelled baseline: your QA team scores a set of real conversations by hand, and the evaluator's agreement with them is measured and reported before it is trusted with anything (the method, with a free template, is in our QA scorecard guide). That labelled set stays with you and becomes a regression test that does not age.

This is the same approach as the QA system we shipped inside a large European iGaming operator running six brands in 2024–2025: a hand-scored baseline first, the evaluator calibrated against it, and only then the coverage that no QA team can reach by hand — from roughly 2% of conversations reviewed to 100%.

How we prove it works →

Auto quality control is also the answer to the question every board asks after month three: is this thing still as good as it was when we bought it? Without it, the only honest answer is a shrug and a CSAT score almost nobody fills in.

Component 03

VIP protection and pre-VIP discovery

These are two different problems and they are worth separating, because one protects revenue you already have and the other finds revenue you do not have yet.

VIP protection — the players you already know

Your PAM knows who they are. The moment a known VIP opens a conversation, the triage agent routes them out of automation entirely and to their own manager, with the context already summarised. There is no scenario in which a VIP is handled by a bot because the queue was busy. This is a rule, not a probability.

Pre-VIP discovery — the players you don't know yet

Your PAM cannot tell you about a player who has not yet deposited like a VIP. But how someone talks to support very often gives it away before their deposit history does: what they ask about deposit ceilings and payment methods before a first large transfer, how specific their questions about withdrawal times and limits are, whether they ask about cashback terms the way somebody who plays elsewhere at high stakes asks, how they respond to a standard offer.

PlayerDesk scores those behavioural signals live and flags the player to your VIP team while the conversation is still open — not in a report next month, when they have already found a better host somewhere else. Depending on the tier, the rules you set can change the tone, lift a limit, or take the player out of automation and put a person on them immediately.

A signal, not a verdict

Your VIP team gets a ranked lead with the reasoning shown, and confirms it. The system never silently reclassifies a player.

Measured against conversions

Precision is tracked against players your team actually confirmed — so the signal is worth something or it gets retuned.

Tier-aware handling

Different tone, different limits, or straight to a human. Your rules, applied consistently on every shift.

The component that earns

The other two lower a cost line. This one adds to the revenue line — which is usually what makes the business case easy.

Voice, on the same brain

Chat and email carry most Tier-1 volume — but voice is where the P&L math changes fastest. A 24/7 voice desk for a mid-size operator runs €8–15K/month for a volume that is a fraction of the day shift; cut the shift and 25–35% of night calls go unanswered.

PlayerDesk includes a real-time voice loop for inbound calls: telephony connector (Twilio / Vonage / SIP) → speech to text → the same triage, knowledge and action agents used for chat → speech back. Escalation is rule-based plus signal-driven: VIP detected, RG keyword, low confidence, three failed clarifications. When a human picks up, they get the full conversation summary — not a cold hand-off.

Quality control and pre-VIP detection apply to calls exactly as they apply to chats. Every call is logged with reasoning traces and API-call receipts, ready for compliance review.

Voice channel in detail →

Where your players' data actually goes

This is the first question we get from every operator, and it deserves a precise answer rather than a reassuring one.

PlayerDesk is installed inside your infrastructure. Your player database, your event stream, your conversation history and your audit log stay where they are today. Nothing is copied to Arctura; we operate no player database and hold no copy of your book.

Identities are removed before anything leaves your perimeter. A redaction pass replaces player ID, name, email, phone, document and card numbers with tokens, and your own systems re-attach the identity on the way back. The mapping never leaves you.

The language model runs in the EU, with zero retention. Requests are not stored after the response and are not used to train models. The providers are named openly — Anthropic, OpenAI or Azure OpenAI, fixed per deployment and written into your contract — and where a jurisdiction requires a specific provider or a fully self-hosted model, PlayerDesk runs that way too. For the regulatory side, see the EU AI Act and GDPR for AI player support.

The full data & security brief, including the redaction detail for your DPO →

Built for EU rules and your licence

An AI that talks to your players has to satisfy two regulators at once: the EU AI Act and the gambling authority that issued your licence. PlayerDesk is designed around both from the first line of code, not retrofitted. A customer-support assistant sits in the AI Act's transparency tier, and the controls below are the ones your compliance team and your regulator will ask about.

Players always know it's an AI

Every chat, email and call opens by saying it is an automated assistant, and "am I talking to a bot?" gets an honest yes in every language. No fake human personas. This is the EU AI Act's Article 50 disclosure, in force since 2 August 2026.

Problem gambling is detected and handed to a person

Responsible-gambling signals are checked on every message, not only at the start of a chat: self-exclusion and limit requests, loss of control, financial distress, chasing losses. The player is moved to a senior human within seconds with a calm holding message. The AI never handles an RG case alone.

Disputed outcomes and KYC go to humans

Withdrawal disputes, refused payments, complaints, fraud and AML cases are routed to your team with the context summarised. On KYC, the AI explains document status and the next step; it never judges a document. Decisions that restrict a player stay with a person, as GDPR Article 22 expects.

The AI never moves money

The model proposes, rule-based validators decide. Bonus eligibility, payment actions and account changes go through validators or human approval, and at night account writes are queued for your team rather than executed.

Every decision is logged

Each account read, action, refused action and escalation is recorded with its reason, together with reasoning traces and API-call receipts. Any conversation can be reconstructed for a regulator, and the audit tables hold no personal data, so they can be kept for years.

No emotion recognition

Distress on a call is read from what the player says, not inferred from their voice. That keeps the voice channel outside the AI Act's high-risk emotion-recognition category, and your agents are never emotion-scored either.

Compliance stays your responsibility as the licensed operator. PlayerDesk gives you the controls that make it achievable and the records that prove it.

What the EU AI Act means for licensed operators →

Proof / blueprint origin

Deployed for a large European iGaming operator running six brands on two PAM platforms (IqSoft and EveryMatrix) — one AI core, two adapter sets, shared knowledge and escalation logic, 100K+ player messages a month. Multi-agent orchestration with tool use, SGR for predictability, real-time QA monitoring. The quality-control layer traces to the SGR-based QA system we shipped inside the same operator in 2024–2025.

What you get

  • Multi-agent orchestration tuned to your operator, across chat, email and voice
  • 20+ languages, your brand voice
  • PAM / payments / KYC API integration (IqSoft, EveryMatrix production adapters; SoftSwiss on request)
  • Helpdesk adapters: LiveChat, Zendesk, Intercom, Freshdesk, or in-house
  • Auto quality control encoded from your existing QA protocol, covering AI and human agents
  • VIP protection rules plus pre-VIP detection feeding your VIP team
  • Real-time QA layer (hallucination, tone, accuracy)
  • Full audit trail and request-level data trace for compliance reviews
  • EU-ready controls: AI disclosure in every channel, responsible-gambling, dispute and KYC handoff to humans, decision log for regulator reviews

Timeline

  • Week 1–2: Discovery — knowledge base, PAM and helpdesk integration, brand voice, and your existing QA protocol.
  • Week 3–4: Core agents deployed; your QA team labels the baseline set that calibrates quality control.
  • Week 5–6: Shadow mode — the AI suggests, humans approve, and both are scored on the same rubric.
  • Week 7–8: Gradual rollout, topic by topic, each released only once it clears your quality threshold.
  • Ongoing: Continuous calibration, drift monitoring, and pre-VIP precision measured against confirmed conversions.

What we need from you

  • API access to PAM, helpdesk and payments
  • FAQ / knowledge corpus (or we help build it)
  • Anonymised historical conversations for evaluation
  • Your existing QA scorecard and a QA lead to calibrate against
  • Brand voice docs
  • Escalation rules, VIP tiers and team structure

Pricing

Design partner pricing on request. First-cohort economics, perpetual usage license.
Buyer's guide

12 questions to ask any support-AI vendor.

Free PDF. Written to work against us too — measurement, economics, data and regulation, operational reality.

Get the guide →

What's your L1 support actually costing you?

30 minutes. We look at your chat volume, your shift structure, your languages, your QA protocol and your VIP rules — and tell you honestly how much PlayerDesk can take off your hands, and how much it can't.

Or write: hello@arctura.eu

Not ready to deploy? Start with a free structure-of-load report →