AI SUPPORT FOR GAMING OPERATIONS

Let AI handle the routine work.
You choose what needs approval.

AI answers from your approved knowledge and rules. A new question may need your team once: review the answer, save it and test the same question or its approved wording variants. You control which replies need approval.

Try it with sample data. Live channels and account connections need setup and testing.

An incoming deposit question
Your policy and available evidence
QUESTION → CHECK → ANSWER01

“I sent the transfer. Why hasn’t my balance updated?”

Matching sample recordMatched

Sample record matched. AI answers the status question.

Your rules control approval
Illustrative workflow

Same question. Less work for your team.

Manual process
AI demo process
Manual processFind the account → open the record → check the status
AI demo processAI checks the matching sample record and answers the status question.
Manual processFind the policy → read it → type the same answer again
AI demo processAI replies from approved knowledge. Review a new answer once, then test it for reuse.
Manual processSolve the same unusual question again on the next shift
AI demo processSave the reviewed answer. AI can reuse it when the question and your rules match.

What to compare in your pilot: staff minutes per case, first-reply time and the share answered by AI.

Explore pricing and plan your scope

Planning estimate · Your assumptions, not measured client results

Estimate the staff time you could save.

Change the three assumptions to compare the same daily chat volume.

Before: staff handle every chat

13.3 hours / day

After: staff handle the remaining chats

6.7 hours / day

Estimated staff time saved

6.7 hours / day

50% Less routine handling time

Calculation: chats × staff minutes ÷ 60. After = before × (1 − AI share). Assumes the remaining chats take the same time.

Excludes setup, monitoring and exception follow-up time. An estimate, not guaranteed savings; measure the result in your pilot.

YANDEE SUPPORT, EXPLAINED

See how Yandee takes work off your team.

See AI answer routine questions, follow your approval rules and reuse a new answer after review, testing and publication. Illustrations and local demo screens use sample data.

Download the service explainer

Service explainer · Local demo and illustrated workflows

In the film, “Approval” means DRAFT review or a rule requiring a person. The actual modes are AUTO, DRAFT and OFF.

Music: “Effervescence” by Scott Buckley · Edited excerpt · Scott Buckley · CC BY 4.0

Read the narration

Another late-night queue. The same questions. Answers spread across tabs. Then the next shift starts all over again. Meet Yandee: AI that answers routine questions and checks records, following the rules you set. When the answer is already approved, AI replies. Your team does not need to type the same answer again. You choose the controls: answer automatically, prepare a draft, or ask for approval. Some sensitive cases always need a person. A new question? Your team answers once. Review, test and publish that answer. AI can then handle matching questions next time. Manage each brand in its own workspace, with its own team and knowledge. Start with your policies, review the answers, and plan a Telegram-first pilot. Test delivery before going live. Show us where your support gets stuck. Let’s map your first Yandee pilot.

View the original screen walkthrough (silent)

Try approved AI replies, reviewed knowledge reuse and AUTO/DRAFT/OFF rules with sample data. Live hosting, Telegram, backend access and action-specific approval flows are configured and tested before launch.

SEE IT FOR YOURSELF

AI handles the repeat. You approve what is new.

Try an approved answer or a sample status check. Then review a new question, save the answer as knowledge and test the next repeat. Your rules decide when AI replies and when approval is needed.

Stop searching for the same answer.

Keep approved answers in one library so AI can use the right policy for a routine question.

Let AI finish the routine reply.

Open the interactive demo to see AI answer eligible questions. Staff review mode remains available when your policy requires it.

Approve only the cases that need you.

When review is required, the question and checks stay together. A new routine answer can then be reviewed, saved and tested for reuse.

Yandee interactive demo · Sample data

LOOK INSIDE YANDEE

Your whole shift. A clearer workspace.

Actual screenshots from the interactive Yandee demo. A clear queue, a focused conversation and customer context beside it. Explore the same screens yourself with sample data.

yandee.supportYandee interactive demo · Sample data
01

Know what needs attention before the queue grows.

See waiting conversations, AI activity and the next case to pick up. Open the detailed report when you need it.

yandee.supportYandee interactive demo · Sample data
02

Read the conversation. See the context. Reply.

The customer stays at the centre. Queue on the left, customer details on the right, a reviewable draft below. Extra tools open when you need them.

  1. 01

    Find the case that needs you.

    Find the conversation, its assignment and its current state in the left panel.

  2. 02

    Review a draft instead of starting over.

    Read the customer’s question and inspect the private reply before anyone sends it.

  3. 03

    Know what supports the answer.

    Check customer context and the latest read-only record on the right. Open investigation details in the conversation.

03

Finish setup one step at a time.

Explore the setup checklist in the same workspace. The demo keeps live channel and backend activation separate from completed sample steps.

04

Choose automatic replies or approval first.

Inspect AI modes and channel settings in one place. These controls simulate the policy you would configure for a verified pilot.

The interactive demo has English, Thai and Chinese controls. Screenshots below show sample data; detailed scenario and audit text may use another language.

LESS SEARCHING BETWEEN REPLIES

Handle a new question once. Reuse the approved answer.

Before: staff search and type the same answers every shift. With Yandee: AI handles eligible routine questions. New cases feed a reviewed knowledge process, so a repeat does not always need another handover.

01INTEGRATION DEPENDENT

Customer asks about a deposit. AI checks and answers.

MANUAL PROCESS

The customer has sent a slip. Your team still has to find the account, check the transaction and explain what is known.

In the matched-record demo, AI checks the sample account, amount and reference, then tells the customer the recorded status. Staff only investigate when the record is missing or does not match.

  • AI reads the permitted record; it does not add money.
  • The matching record stays beside the answer.
  • No match? Staff receive the case and the reason.

Sample records in this demo. Your real backend needs a tested read-only connection.

SOURCE AVAILABLE

The record is right beside the reply.

Request
Deposit status
Permitted record
Matched · credited
Confirmed completion
As recorded in the sample
EVIDENCE MISSING

Missing evidence? Keep the case with a person.

No current matching record. Keep the case open and ask the team to check.

Workflow illustration · Sample data

02AI DEMO PROCESS

Same question again? AI sends the approved answer.

MANUAL PROCESS

Support hours, account access and operating rules keep coming back. Searching old chats for each answer takes attention away from unresolved cases.

AI uses the approved guide to answer routine questions. If a question is new, your team checks the answer and saves it for review and testing. Once published, AI can use that answer for eligible repeats under your rules.

  • Approve the answer and the questions it applies to.
  • Test a repeat question before relying on it.
  • Use AUTO for eligible replies; DRAFT when approval is required.

Try a routine answer in the local demo. Live sending is tested during setup.

Knowledge assistant

Approved policy → AI answer

Demo available

Read-only lookup

Permitted record → visible context

Integration required

Handover assistant

Case reason → the right person

Demo available

Onboarding assistant

Requirements → setup checklist

Demo available

Workflow illustration · Sample data

03AI DEMO PROCESS

Run multiple brands without mixing their rules.

MANUAL PROCESS

One team may cover several brands. A reply copied from the wrong workspace can carry the wrong rules.

Organize each brand’s knowledge, channel and team access in its own workspace. A visible brand context helps reviewers check the answer against the correct policy.

  • Separate knowledge and operating rules for each brand.
  • Explicit roles and scoped access for your people.
  • A visible brand context before every decision.

Separate workspaces. Combined cross-brand inbox is planned.

CURRENT WORKSPACE

A
Brand A

Team + knowledge + channel

B
Brand B

Team + knowledge + channel

C
Brand C

Team + knowledge + channel

Separate context. A clear identity.

Workflow illustration · Sample data

04AI DEMO PROCESS

Give withdrawal updates your team can stand behind.

MANUAL PROCESS

“Any update?” comes in again. A guessed arrival time may calm the chat briefly, then leave the next shift explaining a promise nobody verified.

In the demo, a verified sample record says the withdrawal is queued for review. AI explains that reason without inventing an arrival time. If the record is missing or unclear, staff take over.

  • No balance edits or withdrawal approvals.
  • No confirmed transaction based only on a customer message.
  • No invented completion times when the record has none.

Read-only status answers in the demo. AI does not approve withdrawals or change balances.

“My withdrawal is still pending. When will it arrive?”
What does the available evidence confirm?
Evidence availableAnswer from the verified record
Missing or uncertainAsk the team to check
AI answers verified status questions; staff handle uncertain cases

Workflow illustration · Sample data

05AI DEMO PROCESS

Change shifts without making customers start over.

MANUAL PROCESS

The customer has explained the problem. The next person still needs to know what was checked, why it was handed over and who owns the next action.

Keep the conversation, available evidence and handover activity together. A person takes ownership, while account closure and sensitive concerns stay with trained staff.

  • Account closure and responsible-gambling concerns go to staff.
  • No promotion or pressure to continue in a sensitive case.
  • Make ownership and the next action explicit.

Assistance supports trained staff; it does not replace their judgment.

A PERSON SHOULD TAKE THIS
“I want to close my account. Please help me.”
Reason
Sensitive account request
Next step
Pass the request and context to trained support staff.
Y
Human handover

Account closure requires a staff decision. AI does not close the account.

Workflow illustration · Sample data

06REVIEWED IMPROVEMENT PATH

Teach a new answer once. Test it for the next repeat.

MANUAL PROCESS

A new question reaches your team. If the answer stays buried in that chat, the next shift has to solve it again.

Save the team’s answer as a knowledge draft. Review and publish the right version, then test the same question and its approved wording variants. AI can reuse that answer for those matching questions when your rules allow it.

  • Keep the question, answer and source together.
  • Review, publish and test before reuse.
  • Change or revoke answers when your policy changes.

Reviewed knowledge reuse is available in the demo. Automatic learning and publication from every chat are not enabled.

y.

Ready for the next repeat

Approved knowledge + your rules

  1. 01Save answer
  2. 02Review
  3. 03Publish
  4. 04Test reuse

Workflow illustration · Sample data

A CLEAR VIEW OF THE PRODUCT

See what is ready for your first pilot.

Demo available

Try AI answers and human handover.

Run a routine question or sample status lookup, then compare it with a case that needs staff.

Demo available

Set up in English or Thai.

English and Thai flows for account review, workspace setup and a clear next step.

Demo available

Try the billing journey with sample data.

A simulated offer, invoice and setup journey. No money is collected in the demo.

Integration required

Plan the connections your operation needs.

Telegram, backend access, hosting and payment providers are scoped and verified for your pilot.

THE SCREENS BEHIND THE SERVICE

Keep the whole shift in view.

Open work, human ownership and setup status give the next shift a practical starting point.

yandee.supportYandee interactive demo · Sample data

See which conversations need your team.

Waiting conversations and sample activity are separated from detailed reporting controls. All figures come from this synthetic demo, not customer performance results.

Check the workspace from your phone.

The same responsive demo, with navigation and customer context available when needed. No native app installation is required.

Desktop and mobile screenshots use synthetic records. The demo is a responsive website, not a native mobile app.

FOLLOW THE SUPPORT WORK

See AI answer, or pause for review.

Choose a sample case, inspect its evidence, then see the exact reply or handover.

yandee.supportPPilot workspaceInteractive illustration · Sample records · No live actions

Choose a sample deposit outcome

Sample customerTelegram · Demo data
Handed to staff · Deposit not confirmed
Incoming message

I sent the transfer, but my balance has not updated. Can you check?

Illustrative scenarios with sample data. This page is not connected to a customer account or live backend.

Yandee knowledge workspace · Sample data

Your knowledge, made useful

Answer it once. Save it for the next time.

When a new question needs your team, save the checked answer with its source. Review and publish it, then test the repeat question. AI can reuse approved knowledge when the question, brand and rules match.

  • Save a new answer as a draft, with its source.
  • Review, approve and publish the right version.
  • Test reuse; update or revoke it when the rules change.
See how onboarding works

OWNERSHIP YOU CAN SEE

Keep approval where your rules require it.

A case that needs approval keeps its question, source and next step together. Your team handles that decision; approved routine answers can stay with AI.

  • An explicit person responsible for the conversation
  • A clear distinction between waiting, AI and staff handling
  • Case details stay within reach while the agent replies

Captured from a synthetic conversation after staff takeover. No message was sent to a real customer.

Yandee manual handover · Sample data

CONTROL IS PART OF THE WORKFLOW

You decide what AI sends and what needs approval.

AUTO sends eligible replies. DRAFT prepares them for approval. OFF stops AI. The demo has workspace, channel and case controls; action-specific approval rules for live use are agreed and tested during setup.

A HOME FOR EACH BRAND

One brand’s knowledge stays with that brand.

Organize each brand’s team, channel and approved knowledge in its own workspace. Define the access and deployment needs for your pilot.

Read account context beside the case.

Scope permitted backend lookups with read-only access. No balance changes or withdrawal approvals.

READ-ONLY BY DESIGN

Set the cases that need approval.

Choose draft review where a person must approve the reply. Keep human handling on knowledge or cases that require it, and use AUTO for eligible routine answers.

YOUR APPROVAL RULES

See what the previous shift checked.

See the sources, reviewer decisions and activity trail. Give the next shift a clear starting point.

Responsible-gambling concerns, account risk and uncertain payment cases belong with trained staff. The pilot is built around that handover.

THE COMPLETE WORKSPACE PICTURE

Choose the workflows that take work off your team.

Open a category to see the workflow and its current scope. We agree on the exact capabilities for your pilot before rollout.

AAI assistanceDemo available

Use AUTO for eligible approved answers, DRAFT when a reply needs approval and OFF to stop AI. Workspace, channel and case settings control the local demo. Live action-specific approval rules require scoping and testing.

BKnowledge libraryDemo available

Save new answers and corrections as drafts. Review, publish and test them so AI can reuse the approved version for eligible matching questions. Update or revoke knowledge when the rules change.

CCase lifecycleDemo available

A case keeps its context, owner and next action. Human handover and support-ticket closure are distinct from payment confirmation.

DOperating noticesPlanned

Time-bounded maintenance and incident notices are a future extension. Your pilot starts with reviewed operating policies and staff handling of exceptions.

EVoice and attachmentsPlanned

Voice transcription and bank-slip verification are planned capabilities, not ready-to-buy add-ons. Each needs separate scoping and validation before live use. We do not infer a completed transaction from an attachment.

FStaff toolsDemo available

Inspect the answer and source, take over exceptions and follow the activity record. Choose staff review for workflows that require it.

GCustomer contextIntegration required

Use the records and fields permitted for the case. Confirm identity and access before bringing account-specific information into a reply.

HSpecialist workflowsIntegration required

Knowledge assistance, read-only lookup, human handover and commercial onboarding have separate responsibilities. Backend lookups require a tested connector.

IChat channelsIntegration required

Telegram first. Website chat and other inbox channels are assessed per pilot. A channel is ready only after delivery and handover tests pass.

JTeam and permissionsDemo available

Scoped roles, explicit approvals and separate author/reviewer responsibilities in commercial onboarding. Access is checked for the action and workspace.

KQuality and improvementPlanned

Test a new answer against repeat questions and review the result before relying on it. This is supervised knowledge reuse. Automated evaluation and self-publishing from chats remain unimplemented.

LMobile accessDemo available

Responsive web screens adapt to phones. Native iOS/Android apps, biometric unlock and mobile push are not part of the current pilot.

MMultiple brandsDemo available

A workspace for each brand, with its own knowledge and permitted team access. A combined cross-brand customer inbox is a later capability.

NPrivacy and controlLive setup required

Use authorized content, minimize personal data and keep credentials out of chat. Live hosting, retention and production identity requirements are agreed during setup.

“Demo” means an inspectable sample flow, not a connected production service.

FROM YOUR POLICIES TO YOUR FIRST PILOT

Start with Telegram. Build around your operation.

Bring the policies your team uses, choose the first cases and review the replies together. Test delivery and handover before the pilot reaches real customers.

Plan my support pilot

Scope and pricing are agreed around your requirements.

  1. 01

    Pick your biggest support bottleneck.

    Choose the first support questions, team owner, brand and backend to assess.

  2. 02

    Bring in your first Telegram channel.

    Plan one Telegram connection. Test inbound messages, staff replies and handover before activation.

  3. 03

    Approve answers and set your rules.

    Choose which routine questions AI may answer, which replies need approval and which actions are outside its scope. Save reviewed answers as the starting knowledge.

  4. 04

    Test which cases AI can finish.

    Try approved replies, first-time questions and approval-required cases. Review a new answer, publish it and test the repeat before enabling eligible automatic replies.

  5. 05

    Measure the workload. Expand what works.

    Review actual cases together. Add a validated backend lookup or another workflow when the first one is ready.

FROM ENQUIRY TO OPERATION

  1. 01Enquiry
  2. 02Account review
  3. 03Agreed scope
  4. 04Subscription setup
  5. 05Workspace readiness

BEFORE WE START

Know what it takes to get started.

Can we start using this today?

You can try the local demo now with sample data. To serve real customers, we first set up your channel, approved answers, account permissions and handover route, then test the complete workflow.

Does it work with Telegram and our website?

Telegram is the first channel in the pilot plan. For website support, we assess whether an inbox integration fits your setup. We confirm the connection and test real delivery before enabling your channel.

Can it read our backend?

We first review the APIs and permissions your platform provides. Supported lookups can use a scoped, read-only connection. We do not promise compatibility with every backend, and the pilot does not change balances or approve withdrawals.

Can we use our website and old chats as knowledge?

Yes. Authorized site content, policy documents and selected chat history, with personal data minimized, can enter the review process. Your team approves the material before publication. We do not treat every past answer as correct, and conversations do not become knowledge without review.

Can AI answer on its own and reuse what we teach it?

Yes, the local demo has AUTO for eligible replies, DRAFT for approval before sending and OFF. A new answer can be saved as a knowledge draft, reviewed, published and tested for future matching questions. This is reviewed knowledge reuse; chats do not automatically approve or publish themselves. Live connections and action-specific approval rules still need setup and testing.

How are multiple brands and pricing handled?

We scope a workspace for each brand’s team, channel and knowledge, then confirm deployment and access requirements. Pricing is quoted for the agreed pilot, integrations and operating needs. No fixed savings or performance outcome is promised.

Explore pricing and plan your scope

LESS REPETITIVE WORK STARTS HERE

Get more from the support team you already have.
Start your Yandee pilot.

Show us your repeat questions, busiest shifts and support costs. We’ll scope a pilot around the work you want to reduce, then measure what changes with your team.

Plan my Yandee pilothello@yandee.ai
A GOOD FIRST CONVERSATION STARTS WITH
  • 01Your nightly chat volume
  • 02Your team size and brands
  • 03Your channels and backend
  • 04The work that takes the most time

Please don’t email passwords, access tokens or customer records. We’ll agree on a secure setup process.

yandee.support

Yandee interactive demo · Sample data