What the system can actually do.
Six capabilities, each of which changes what happens to a support request before a human sees it.
Read the network, not the knowledge base.
Relia queries the chain directly, reads the token contract for symbol and decimals, and returns one of nine verdicts. Public networks are read with no configuration. Deposit addresses turn a report into an operator-specific verdict.
Arrived
Confirmed, with the amount, token, network and destination on the surface
Confirming
Confirmation count, progress and an estimate from the chain's own block time
Wrong network
The single most common way a crypto deposit goes missing
Wrong address
Went through, but not to an address the operator controls
Token not credited
Reached the right address carrying something the operator does not accept
Wrong network
You sent this on BNB Smart Chain, and we do not credit deposits from BNB Smart Chain.
- Amount
- 0.4 BNB
- Network
- BNB Smart Chain
- Confirmations
- 64
- Destination
- 0x1f09…3337
We accept deposits on Ethereum. I am passing this to the team with your hash so they can check whether the funds can be recovered.
Workflows, not form categories.
Each type sets its own fields, decides whether the assistant answers first, and can bind a resolver that settles the request outright. The operator sees fewer tickets, and the ones that arrive carry the facts.
Six defaults
Transaction, verification, bonus, account access, something is broken, something else
Custom fields
Six kinds including a transaction hash field the resolver reads
Escapes intact
A visitor can always open a ticket anyway, in one click
Result: the hash is requested, the chain is read, the answer is given, and no ticket is created.
One event, not forty tickets.
Every inbound message is classified. Distinct people are counted in a rolling hour and compared against the workspace's own baseline. Cross it, and Relia opens one incident and starts telling players what is happening.
Distinct people, not messages
One angry player writing seven times never opens an incident
Per workspace baseline
A busy operator and a quiet one both behave sensibly
Evidence attached
The alert names the pattern, the count and the conversations behind it
Monitoring
Signals recorded, nothing unusual
Anomaly
Distinct reporters climbing against baseline
Incident detected
Threshold crossed, operator alerted with evidence
Active
Players see the operator's message in the widget
Resolved
Cleared by the operator, banner removed
A statement about money should be provable.
Every chain answer is signed with the workspace key and timestamped alongside what the network reported. The player gets a verification link. The operator can recompute the signature without involving Relia.
Open verification
The page needs no account, because a receipt nobody can open is not a receipt
Tamper evident
Editing the record breaks the signature and the page says so
Case file
The whole dispute assembled in order, with commitments surfaced
Your 250 USDT arrived on Ethereum and is fully confirmed, with 101 confirmations.
- Workspace
- Aurelia Casino
- Transaction
- 0xac8846ff2aad4ea1f92c503a179b017dd62b0d2a579c00428911382a2924042d
- Chain state
- Confirmed, 101 confirmations
- Signature
- 91b2f7121c9e3c01f3b4110df2964f9e570fd8ae035b179037885b38f376fbfc
HMAC-SHA256 over the exact bytes of the record. The operator can recompute it without involving Relia. Changing any part of the statement breaks the signature.
Answers you can inspect before a player sees them.
Paste a FAQ, a policy doc or a set of support macros and Relia drafts structured articles from it. A human ticks off which are true. The tester then shows exactly what Relia would answer, with the sources it used.
Import from anything
A FAQ page, support macros, a policy doc, even a chat thread
Duplicate protection
Drafts that repeat an existing article are filtered out
Never in front of a player
Confidence and sources are operator telemetry
Most withdrawals are instant. Larger amounts can take up to 24 hours if we need to verify the account.
Confidence 0.82 · 2 sources · operator view only
Everything that happened, on the record.
Agent actions, webhook deliveries, data exports and deletions. Not a compliance checkbox, an operational record that answers who did what and when the argument starts.
Audit log
Who resolved, who assigned, who opened a document, who shared a case
Delivery log
Signed webhooks with exponential backoff, retries and a stable delivery id
Data rights
Per customer and per workspace export and deletion
Storage health
Relia says out loud when data is not durable rather than failing quietly
my small deposit never showed up
Ticket · resolved · opened 2026-08-22 13:58 UTC
Agent Sara Lind: I will credit this manually within 2 hours.
13:58:04
Message · Player
my deposit is missing and i need it today
13:58:05
Network · Ethereum
below minimum, 0.001 ETH to 0x1111…1111
Verified on chain13:58:05
Receipt · Relia
Signed receipt issued
Verified on chain14:04:11
Action · Sara Lind
conversation assigned
Agent action14:06:39
Message · Agent Sara Lind
I will credit this manually within 2 hours.
Agent action16:02:10
Action · Sara Lind
conversation resolved
Agent action