Three surfaces. One system.
A player who is worried about money, an agent working an eight hour shift, and an operator who opens Relia once a week. The same system, shaped three different ways, with context that moves between them.
Player
Widget in Shadow DOM, Telegram, WhatsApp, email
Chain reader
JSON-RPC, token contracts, nine verdicts
Knowledge
Retrieval and the assistant, scoped per workspace
Ticket resolver
Type workflow, fields, assistant first
Incident engine
Classify, count, compare to baseline
Signed record written for every answer about money
Agent
Inbox, SLA, assignment, case file
Operator
Settings, keys, webhooks, governance
The moment support begins.
One script tag, rendered inside Shadow DOM so the host page cannot restyle it and it cannot leak into the host. It works on a black casino page and a white dashboard, because it corrects the backdrop it sits on rather than inheriting it.
- Home
- Incident banner, greeting, transaction tracker, ticket types, recent conversation, help search
- Messages
- Every conversation this player started, unread markers and a tab badge
- Tickets
- Their tickets with a quotable reference and a live status
- Help
- The knowledge base, searchable, with an article reader
- Pushed screens
- Conversation thread, article, typed ticket form, transaction tracker, confirmation
- Branding
- Accent, uploaded logo, title, greeting, tagline, categories, theme, corner
A working instrument.
Dense on purpose. An agent lives here for a whole shift and moves through dozens of conversations an hour, so information density beats whitespace every time.
Deposits
28 players · started 12m agoAnonymous visitor
Ticket H2A-XGJ · route / web
- Filters
- Inbox, Open, Unassigned, Tickets, Closed tickets, Escalated, AI handled, Resolved
- Actions
- Assign, escalate, resolve and reopen from the thread header, at any window width
- SLA
- Countdown per conversation against the workspace target
- Provenance
- Assistant answers labelled by what they read, never by a confidence number
- Incidents
- A strip across the top with the count, the pattern and the message players see
- Case file
- One link assembling the whole dispute, audited when shared
Control that behaves like infrastructure.
Everything an operator configures is a product surface in its own right, not a settings form. The install screen detects itself. The studio previews live. The chain setup tests on a real hash.
<script src="https://www.relia.gg/widget.js"></script>
<script>
Relia.init({ publishableKey: "pk_live_…" });
</script>- Install
- HTML, React, WordPress and GTM, with live detection and try it here
- Widget studio
- Live preview beside every control
- Ticket types
- Fields, assistant first, resolver, priority
- On-chain answers
- Networks, deposit addresses, tokens, minimums, tested on a real hash
- Knowledge
- Articles, paste to import, and a tester that shows what Relia would answer
- Team, keys, governance
- Roles and invites, publishable and secret keys, audit and delivery logs