By Diger

DigerCompanion

A governed staff/player conversational assistant with record-based context, approvals and human handoff.

The offering

What DigerCompanion does

DigerCompanion is separately marketed for operational queries, shift briefings and first-line player support. Its current description connects authenticated player/account, payment, bonus and game records through controlled interfaces, with staff-role/brand restrictions and audit logs. High-risk changes require two authorised staff confirmations, while sensitive or out-of-scope player conversations reach human support.

Test each allowed intent, permission, proposed action and handoff using representative records. Confirm how failures and approvals are reported to staff and players. The supplier’s advertised calculation/deflection and safer-gambling claims are not adopted as verified outcomes; a sample-data demonstration is not proof of a live autonomous deployment.

Who should explore it?

Operators adding scoped conversational support and controlled operational investigation to an existing stack.

  • Investigate an account/payment issue using permitted records
  • Escalate a player conversation to authorised support

Documented capabilities

  • Record-based operational queries
  • First-line player conversations
  • Role/brand access and dual approval
  • Human handoff and audit logs

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Intent scope
Operational briefings, payment/bonus/account investigation and routine player support.Source
Record context
Authenticated account, verification, payment and bonus records through controlled connectors.Source
Action controls
High-risk changes require dual authorised approval; test tool failures and final state readback.Source
Staff handoff
Sensitive/out-of-scope support and gambling-distress conversations escalate to people with context.Source
Access boundary
Role/brand/market access, private-cloud data and audit records; configure actual retention and eligibility rules.Source

Delivery & commercial details

Delivery & integration
Private-cloud assistant/widget with governed PAM/RGS/payment/CRM interfaces and human support path; test intents, permissions and failures.
Pricing
Request assistant/module, model/channel usage, language scope, connectors, deployment and support terms; no fixed public numerical tariff was established.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Can it change an account without staff control?

The current page places high-risk changes behind two authorised staff approvals and role/brand permissions. Define permitted actions and test confirmation/failure behaviour in the deployment.

Source
What happens when a conversation needs a person?

The product describes human handoff with relevant context, including sensitive or gambling-distress support. Confirm routing, staff availability and retained conversation records.

Source