NewInteractive Agents Live

Betsson France: Production AI for Regulated iGaming Support

How Betsson France made ~75% of customer support autonomous, eliminated 30+% of tickets at root cause, and enforced compliance on every interaction.

Betsson France logo

Industry

Region

  • Europe
InteractiveAI12 min read

Listen to this case study

0:00 / 0:00

75%

Customer Issues Resolved End-to-End

3.3 min

Average Resolution Time

40-50%

Cost Reduction

Verified production results

Executive Summary

Support that runs under regulation, at scale.

Betsson France operates one of the most demanding customer support environments in European iGaming: high-volume, French-licensed, governed by strict KYC, AML, and responsible gaming requirements, with sharp seasonality tied to the sporting calendar. Before InteractiveAI, support agents resolved tickets by manually navigating five siloed systems, and institutional knowledge lived in static documentation and individual managers' heads.

InteractiveAI deployed production-grade Interactive Agents into Betsson France's customer support operation, integrated end-to-end with PAM, Zendesk, Sumsub, Jira, and the promotion engine. The AI agents now run across Email, Live Chat, and KYC as a cross-functional layer interacting with Customer Support, Compliance, Fraud, and Operations.

~75% of customer issues are resolved by AI end-to-end. This combines 65-80% direct autonomous resolution on tickets that enter the queue with the 30+% of would-be tickets the AI eliminates proactively at root cause. KYC issues that used to take days now resolve in minutes. Every AI decision links back to a specific policy.

With InteractiveAI, we didn't deploy a chatbot. We built a governed AI system embedded in our operational stack. Roughly 75% of our customer issues are now resolved by AI end-to-end, plus 30+% of would-be tickets that never reach the queue at all, resolved proactively at root cause before a customer has to ask for help.

Mehdi Aounallah

Head of Customer Support, Betsson France

The Challenge

Five systems, one ticket, no room for error.

Betsson France ran a high-volume, high-regulation operation under structural friction. Within a single ticket, CS agents manually navigated five disconnected systems for player data, KYC verification, escalations, and bonus eligibility.

The cost per ticket was high. During peak sporting events, response times lengthened. Quality varied across shifts and agents. They needed an AI infrastructure layer that could take action under regulatory enforcement, at any hour, at any volume.

Betsson France evaluated standard helpdesk AI add-ons, in-house agent frameworks, and direct frontier model deployments before selecting InteractiveAI. The decision criterion that mattered: production AI they could trust under strict regulatory constraints, operate themselves, and extend across the rest of the business.

Business Impact

The numbers that landed in production.

Autonomy & Outcomes

Autonomous Customer Support Resolution
~70-75%
Proactive ticket elimination at root cause
30+% of would-be ticket volume
KYC Autonomy
80-90% (L1: 85%; L2: ~100%)
Promotions & Offers Autonomy
85-90%
Player Login Autonomy
~90%
Player Information Updates
80-90%

Performance

Cost per Ticket (with AI)
€0.50-0.80
Estimated Cost per Ticket (fully loaded baseline)(The estimated fully loaded Cost per Ticket accounts for InteractiveAI platform costs combined with human agents' gross salaries, employment taxes, benefits, and related operational overhead.)
~€4.00+
Cost Reduction
40-50%
Human Hours Saved per Month
1,100
Average Resolution Time
3.3 minutes
Acceptance Rate
>90%
False Positive Rate
<1%

Operational Scale (last 30 days)

Tickets handled across Chat, Email, and KYC
~8,000
Additional tickets eliminated at root cause through proactive resolution in Sumsub, before reaching the support queue
~3,000
Ticket-equivalent workload addressed, handled by computing power, not headcount
~11,000
What surprised me most is how much of the AI we now run ourselves. When something needs adjusting, a new rule, a tone change for a sensitive topic, a tightening of a bonus eligibility check, I do it directly. I write the policy, test it, deploy it. No engineering ticket, no waiting cycle.

Mehdi Aounallah

Head of Customer Support, Betsson France

Beyond the Cost Line

The win isn't cheaper support. It's better support.

What scales here is not chatbot deflection or FAQ retrieval but production support operations executed by agents that can be trusted to enforce policy precisely on every interaction. The business impact is structural: handling thousands of tickets a month now requires computing power, not extra headcount. When big sporting events cause sudden spikes in traffic, the AI absorbs the extra work instantly without the need to overstaff or slow down.

But beyond saving money and reducing workloads, this is a major upgrade in customer service. Faster response times and 24/7 availability directly improve the player's experience. Faster identity checks mean quicker first bets, faster withdrawals keep players loyal, and round-the-clock support means players get help instantly instead of waiting in a queue.

And beyond the numbers, the quality of service has changed: KYC issues that used to take days resolve in minutes, 24/7. The results exceeded every expectation we had.

Mehdi Aounallah

Head of Customer Support, Betsson France

Proactive Resolution

The best ticket is the one that never opens.

Most AI deployments measure success by deflection. Interactive Agents go further: they eliminate the conditions that produce tickets in the first place. The KYC agent operates directly on top of Sumsub, catching name-matching failures, document-quality issues, and verification edge cases that would previously surface as customer support tickets. The customer often never sees the failure state. The agent re-runs the check, completes the verification, and the player advances without writing in.

Conservative measured impact: 30+% of would-be tickets eliminated before reaching support. What used to be ~11,000 monthly tickets is now ~8,000, and the ~3,000 difference never enters the queue at all. This is the single highest-leverage outcome of the deployment: not just handling tickets faster, but reducing the volume of work the operation needs to handle.

Quality of Service

KYC resolution time
Days to minutes
Availability
24/7, no degradation during sporting peaks
Customer experience
Proactive feedback on document issues; no queue waits
Thank you so much, I did not expect you to be able to resolve this issue so quickly and efficiently at this time of night.
Betsson France player (On a KYC verification completed overnight (anonymized, shared by Betsson France operations team))

What the AI Handles

Domain by domain. Measured autonomy. Deliberate human boundaries.

  • Promotions & Offers

    85-90% autonomous

    The largest domain. The agent resolves bonus eligibility, wagering questions, and welcome-offer disputes by reading the player's transaction history and account flags directly. Routine cases close in a single turn. Complex eligibility decisions, where commercial discretion is required, route to the bonus team with full context attached.

  • KYC & Document Processing

    80-90% autonomous

    Identity verification is the most regulated workflow in iGaming and the highest-stakes test of any AI deployment. The agent reconciles verification data with the player profile, applies the verification policy at every level (basic ID, proof of address, IBAN), and replies in seconds with a full audit trail. Level 1 (ID): 85% autonomous, the agent performs fuzzy name matching and modifies Sumsub records to resolve mismatches, mimicking human reviewer behavior. Level 2 (POA): approaching 100% autonomous. During implementation, InteractiveAI also closed a long-standing gap: the previous system rejected French names with accents and minor address variations, generating unnecessary KYC failures the agent now resolves correctly.

  • General Inquiries

    High

    Open-ended account questions and conversational support. This is where Interactive Agents differ from a traditional chatbot: the same agent that runs a deterministic compliance routine can hold a fluid conversation, and switch back the moment a regulated topic surfaces.

  • Withdrawals & Payments

    By design

    Withdrawal status questions and payment-pending diagnostics. The agent pulls withdrawal and ticket history, checks compliance flags, and either resolves directly or hands off to the payments team with a complete brief. Bank-account changes (where financial-fraud risk is highest) are routed to human review by design, not because the AI cannot handle them.

  • Player Information Updates

    80-90% autonomous

    Personal-data, limit, and preference changes. The agent applies the right identity-verification gate, collects supporting documents, and either completes the update directly (low-risk changes like email) or hands off to operations with a complete brief (higher-risk changes like banking details).

  • Login & Account Access

    ~90% autonomous

    A complex routine that touches multiple tools and teams, yet the agent resolves nearly all cases without escalation, a demonstration that autonomy on intricate workflows is achievable end-to-end.

  • Betting History and Deposits

    High

    Sportsbook history questions and deposit troubleshooting. Each follows the same pattern: account-state diagnosis, history retrieval, and structured escalation where human judgment is required.

Compliance & Governance

Governed every turn. Not after the fact.

Compliance & Governance

Compliance Policy Enforcement
100% on every triggered interaction
Decision Traceability
Every action traced to the policy that produced it
Cross-Departmental Escalation Quality
Zero variability in context completeness
Hallucination Prevention
Structurally enforced at response generation
Every decision is traceable, testable, explainable, and auditable.

Mehdi Aounallah

Head of Customer Support, Betsson France

How It Works

Built by the people who run the operation.

Interactive Agents are composed from eight components that domain experts and engineers build together. Dynamic Context Engineering then retrieves only the policies that match the current customer interaction, so per-turn cost stays flat whether the policy library has 50 rules or 5,000.

Models are a commodity. Business impact comes from how context, data, and tools are managed across the entire AI lifecycle, from build through governance to continuous improvement. The agent that ships on day one is the weakest version of the agent that will ever run.

The Components

Eight components. Authored together.

  • Prompts

    Persistent identity and guardrails.

  • Policies

    Condition-action rules in natural language.

  • Routines

    Multi-step procedures.

  • Glossary

    Domain vocabulary.

  • Macros

    Reusable compositions of routines and policies.

  • Variables

    Player state and account flags.

  • Tools

    Gated connectors: PAM, Sumsub, Zendesk, Jira, IBAN/RIB, and InteractiveAI OCR.

  • Knowledge Base

    The documented policy the agent grounds its answers in.

Managers write the rules. Engineering wires the systems. Both work in the same artifacts.

The Platform

One platform for the entire lifecycle.

  • Trace-level observability

    Every decision captured with cost-per-run, latency, and compliance reports on demand.

  • Natural-language policy authoring

    Compliance edits policies and redeploys instantly, no engineering.

  • Sovereign deployment

    Agents, data, and 200+ models on cloud, private cloud, or on-premise, with regional residency and zero retention.

  • Compounding traces

    Every interaction becomes better future performance, validated in sandboxed experiments before production.

Platform Integrations

One orchestration layer across the operator stack.

  • Player Account Management (PAM)

    Source of truth for player data: account status, balances, personal details, limits, history. Read and write access enables the agent to retrieve player state and execute updates directly.

  • Zendesk

    Email and Live Chat. The agent reads inbound tickets, classifies intent, executes workflows, writes responses, and manages full ticket lifecycle programmatically.

  • Sumsub

    Identity verification: status, document review outcomes, KYC process triggers and follow-up.

  • IBAN/RIB validation service

    Bank account validation for withdrawal eligibility checks.

  • InteractiveAI OCR Model

    Proprietary OCR for document-heavy workflows like bank account verification.

  • Promotion engine

    Bonus eligibility, offer state, and wagering data sourced for the Promotions & Offers routine.

  • Jira

    Internal escalation routing for payment processing issues, compliance edge cases, fraud flags.

Representative tools in production

  • Authentication & player stateauthenticate_customer, get_applicant_data, get_filtered_action_log
  • KYC & document processingocr_document, approve_applicant, reject_applicant, get_fraud_network, add_note_to_applicant
  • Account updatesupdate_customer_email, update_player_information
  • Conversation lifecycleclose_conversation, emit_output (for trace transparency)
  • Knowledge retrievalInternal knowledge base lookup, the most frequently called tool, invoked whenever the agent needs to ground a response in documented policy
  • Cross-team handoffStructured Jira ticket creation with full context payload

What Scales Next

Customer support was the first agent. Not the last.

Customer support was the first deployment. It is not the last. The AI infrastructure investment is one-time, not per-use-case: every additional Interactive Agent runs on the same platform, with policy-authoring skill, governance practice, and the datasets compounding from support traffic transferring to whatever comes next. The foundation is production-proven. What scales next is the business.

Take the Next Step

Three concrete paths forward.

  • See the agents in production

    Book a 30-minute live demo where the InteractiveAI team walks through actual policies, routines, and traces from a working iGaming deployment.

  • Talk to the team that built this

    InteractiveAI can introduce you directly to the Betsson France operations team.

  • Run a scoped pilot

    A 6-week implementation on one or two of your highest-volume support domains, with measurable success criteria defined upfront.