Skip to main content

AI Assistant

The AI Assistant is a full-page conversational agent for the backoffice, built on Artificial Intelligence (AI). The Content Management System (CMS) is the backoffice area for managing player-facing content. Describe what you want in plain English and the assistant uses the platform's tools to help you find information and make changes — across players, transactions, bonuses, campaigns, the CMS, tournaments, loyalty, analytics, workflows, and segments.

Overview​

The assistant is a general backoffice copilot, not a workflow/segment-only helper. It has its own page and keeps a persistent conversation history. Mutating actions are surfaced as a plan you explicitly approve before anything is changed.

Accessing the AI Assistant​

You can reach the assistant in two ways:

  1. AI Assistant in the sidebar (/assistant) - the full standalone chat with conversation history, available to operators with permission to view the assistant.
  2. In-editor panels - a scoped assistant panel inside several editors, including the Workflow builder and Segment editor (plus banner, notification-template, and tournament editors).

Using the Assistant​

Starting a Conversation​

Use the assistant instead of navigating multiple screens when you want a quick answer or a ready-to-review change.

  1. Click the AI Assistant icon
  2. A chat panel opens
  3. Describe what you want to create

Example Prompts​

For Segments:

  • "Create a segment of players who deposited more than €500 in the last month"
  • "Find inactive players who haven't logged in for 30 days"
  • "Group all UK players who play slots"

For Workflows:

  • "Send a welcome email when a new player registers"
  • "Grant a 50% bonus when a player makes their first deposit over €100"
  • "Notify the VIP team when a high roller requests a withdrawal"

Review and Approve​

The assistant works in planning mode, so nothing changes on your platform until you've reviewed and approved it:

  1. Describe your request
  2. Review the proposed configuration
  3. Approve to apply changes
  4. Refine if adjustments needed
tip

Always review the assistant's proposal before approving. Make sure the logic matches your intent.

Conversation Tips​

Be Specific​

❌ "Create a segment for good players" ✅ "Create a segment for players who deposited over €1000 and logged in within the last 7 days"

Include Details​

❌ "Send an email after deposit" ✅ "Send the 'Thank You for Depositing' email template when a player deposits €50 or more"

Ask for Explanations​

You can ask the assistant to explain:

  • "Why did you add this condition?"
  • "What does this action do?"
  • "Can you simplify this workflow?"

Capabilities​

The AI Assistant works across many domains of the backoffice, including:

  • Players & transactions - search and view players, look up transactions, review pending withdrawals
  • Bonuses & campaigns - create and manage bonus templates and campaigns
  • Tournaments & loyalty - manage tournaments and loyalty programs, tiers, rewards, and rules
  • CMS - pages, sections, banners, carousels, and menus
  • Notifications - notification templates (with AI translation)
  • AI image generation - generate images (for banners and content)
  • Analytics - run analytics queries and reports
  • Workflows & segments - create, edit, and manage lifecycle

It can delegate to specialist agents for focused tasks, and it plans mutating work as a series of steps, each tagged with an impact level: safe, requires approval, or dangerous.

Permissions and Safety​

The assistant always acts under your own permissions and brand scope:

  • It can only use platform tools you are permitted to use — for example, an operator without permission to view player records can't ask the assistant to look up player details.
  • It is restricted to your authorized brands; cross-tenant and other-brand data are blocked.
  • Safe reads (looking things up) run directly, while mutating steps are surfaced as a plan you must approve before they run.
  • It does not guarantee perfect accuracy — always review a plan before approving it.

Conversation Management​

The standalone assistant keeps a history sidebar where you can:

  • Rename, pin, and delete conversations
  • Search across conversations and within the current conversation
  • Export a conversation to Markdown
  • Use keyboard shortcuts (for example, in-conversation search)

Plan Approval​

When the assistant needs to change something, it presents a plan of steps. You can:

  • Approve or reject the plan, and resume after approval
  • Retry an individual tool call that failed
  • Answer structured question cards when the assistant needs more input

Each step shows its impact level (safe / requires approval / dangerous) so you know what will happen before you approve.

Usage Analytics (superadmin)​

Superadmins can open a Usage Analytics dashboard from the assistant (analytics icon) to review AI usage over a date range, broken down by user, by model, and by agent, plus tool analytics, cache performance, and quality metrics — useful for cost governance.

MCP Tokens​

From your account menu, you can generate personal access tokens to connect external AI tools to the platform's assistant tools. Tokens can be generated, listed, and revoked, up to a limit of 25 tokens per user. A token acts under the issuing operator's own permissions and brand scope, the same as using the assistant directly in the backoffice.

Example Session​

You: "I want to create a segment for VIP players"

Assistant: "I'll help you create a VIP segment. To define 'VIP' players, what criteria should we use?

  • Minimum deposit amount?
  • Total wagering?
  • Account age?
  • Specific VIP tier?"

You: "Players who deposited more than €5000 total"

Assistant: "I'll create a segment with this rule:

Segment: VIP Players

  • Event: SUM of deposit.completed amount (all-time) > 5000

The preview estimates about 342 matching players. I've prepared a plan to create it — please review and approve."

You: (reviews the plan and clicks Approve)

Assistant: "Done! The 'VIP Players' segment has been created. You can now use it in workflows."

note

The matching-players count shown before you approve is an estimate, and any change the assistant makes runs through the plan-approval flow described above — nothing is applied until you approve it.

Settings​

Provider, model, and Application Programming Interface (API) key settings live under the AI Provider tab: superadmins set the system-wide default in System Settings, and operators with permission to view or change assistant configuration can override it for their own operator in Operator settings. Supported providers are Claude, OpenAI, and a self-hosted custom endpoint. Response style (tone: professional, friendly, or concise) and suggestions are separate configuration options.

Troubleshooting​

Assistant Not Responding​

  • Check your internet connection
  • Confirm a provider and API key are configured in the AI Provider settings (requires permission to view assistant configuration, or superadmin access)
  • Try refreshing the page

Incorrect Suggestions​

  • Provide more specific details
  • Break complex requests into smaller parts
  • Manually adjust after initial generation

Missing Features​

  • Some advanced configurations may need manual setup
  • The assistant works best for common patterns