Support infrastructure for products where support is about money.
Traditional support software searches text. When a player asks where their deposit went, the answer is not in an article. It is in the transaction. Relia reads it.
Relia agent inbox, incident active
Where is my deposit?
It is the most common question a crypto operator receives, and the one every support tool answers worst. The player is not asking about policy. They are asking about their own money, right now.
- 01Search the knowledge base
- 02No article covers this transaction
- 03Escalate to a human
- 04The player waits
- 01Identify the transaction
- 02Read the network
- 03Return a verdict
- 04Open a ticket only if needed
The answer is on chain.
A hash pasted into the chat or the tracker is enough. Relia queries the network, reads the token contract for its symbol and decimals, and returns what actually happened. It works before an operator configures anything.
Relia never claims money reached the operator when it cannot know that. Without a configured deposit address it reports the network facts and says so plainly.
Arrived
Your 250 USDT arrived on Ethereum and is fully confirmed, with 101 confirmations.
- Amount
- 250 USDT
- Network
- Ethereum
- Confirmations
- 101
- Destination
- 0x1f09…3337
Balances update within a few minutes of the final confirmation.
- Verdicts
- 9
- arrived through to not found
- Networks
- 7
- Ethereum, BSC, Polygon and more
- Setup required
- None
- public networks read by default
- Token metadata
- On chain
- symbol and decimals from the contract
The best ticket is the one that never existed.
A ticket type in Relia is a workflow, not a label. It decides which fields to ask for, whether the assistant answers first, and whether the chain can settle it outright.
Player picks Transaction
The form asks for a hash and what happened
Relia reads the network
Amount, token, confirmations, destination
Verdict returned
Your 250 USDT arrived 12 minutes ago
No ticket created
The workflow ends without an agent
Forty reports are one incident.
Every support tool counts conversations. Relia classifies them, counts distinct people in a rolling hour and compares that against the workspace baseline. When the pattern crosses, it opens one incident.
Baseline for this workspace / 1 per hour
The widget stops asking how it can help and starts telling them what is happening.
Support volume peaks exactly when the product is broken. This is the moment every other tool drowns, and the moment Relia becomes more useful rather than less.
Prove what was said.
A statement about someone else's money should not rest on a chat log the operator controls. Every answer Relia gives about a transaction is signed and timestamped together with what the network reported at that moment.
The player can check it
A verification link that does not require an account
The operator can prove it
Recomputed from the workspace key, without involving Relia
Tampering shows
Editing the record breaks the signature
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.
One dispute. One record.
Messages, chain facts, signed receipts and agent actions assembled in order, with the commitments pulled to the top. One read only link, audited when shared, and it expires.
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
Install it without a project.
One script tag. Relia tells you the moment it sees itself running on your site, and you can try the widget from the settings screen before touching production.
The widget renders inside Shadow DOM, so the host page cannot restyle it and it cannot leak into the host. Only the publishable key ever reaches the browser.
<script src="https://www.relia.gg/widget.js"></script>
<script>
Relia.init({ publishableKey: "pk_live_…" });
</script>Make it yours.
Accent, logo, greeting, ticket categories, theme and corner, all per workspace with a live preview beside every control. Relia should read as the operator's support experience, not as a tool they rented.
Most of them are on a phone, and worried.
This is not a picture. It is the production widget running at a phone width, on this page. Open it, switch tabs, paste a transaction hash and watch it read the network.
Try a real hash
0xac8846ff2aad4ea1f92c503a179b017dd62b0d2a579c00428911382a2924042d
Or ask a question
how long do withdrawals take?
The same script, the same Shadow DOM, the same answers your players would get. Nothing on this page is a rendering of the product.
The part nobody demos, and everybody needs.
Publishable keys client side. Secret keys never reach the browser.
Signed deliveries with exponential backoff, retries and a delivery log.
Every agent action recorded: who read a document, who resolved what.
Per customer and per workspace export and deletion, built in.
Relia says out loud when data is not durable instead of failing quietly.
Every query scoped to a workspace. One inbox can never see another.