Chatonio

This is taking longer than usual.

Crypto exchange

Support for exchangers that answers from the actual order.

“Where’s my withdrawal? It’s been an hour.” The AI opens the real order and answers in seconds — on your site and in Telegram. Your operators keep the conversations that need a person.

Free to try · no credit card · order lookups on a paid plan

The inbox

What actually fills an exchanger’s inbox.

Three questions, over and over — and every one of them is already answered inside the order.

Swipe — 3 of them

The 3am order nobody answers

At night, silence isn’t read as “support is busy.” It’s read as “I’ve been robbed” — and by morning that’s a review on your BestChange page.

The same three questions, all day

“Where is my payment?” “How long?” “Why is my order in manual?” High volume, low value, and the answer is sitting in the order record.

An operator opened it, then got pulled away

The chat is claimed, so nothing else picks it up. The customer watches a conversation somebody started and nobody finished.

Grounded

Every answer comes from the actual order.

Connect your order endpoint once and the AI looks up the real record — status, direction, amount, rate — before it writes a word.

Your API becomes a tool
Give it your order endpoint once. When a customer types an order number, the AI calls it and answers from what came back.
No API? It reads the page
Point it at the order page instead and it fetches that. Same grounding, same audit, no development work on your side.
Reading is automatic. Changing asks first.
Reading an order happens on its own. For anything that changes one — cancel it, resend a payout — you turn on confirmation, and the AI stops, asks the customer in their own words, and waits for a clear yes before it runs.
Your systems
Your order databaseAPI
Your payment gatewayAPI
Your knowledge baseKB
Your FAQKB
Chatonio AI
EX20487315 · awaiting payment · 0 of 1 confirmations
Read from the order record
SwiftBit support
Web chat · 03:47
I paid 20 minutes ago and nothing has arrived
AII can check that right now — what’s the order number? It starts with EX.
EX20487315
AIFound it. EUR to USDT on TRC20 — 1,000.00 EUR for 1,043.20 USDT, at the rate locked into the order, 1.0432.
Created 03:41, still showing “awaiting payment” — so your transfer hasn’t reached us yet.
can you send me the card number again
AII can’t read payment details out in chat. They’re on the order page itself — open EX20487315 and you’ll see exactly where to send, and how much.
I already sent it. 20 minutes ago
Escalated to an operator · 03:49
AIA payment that’s been sent but hasn’t matched needs a person to check the bank side. An operator has been paged and will pick this up here.
See it

One real order, at 3:47 in the morning.

The order, the status and the rate are data the AI actually looked up. It runs on the SwiftBit demo — type an order number that doesn’t exist and it tells you it can’t find it.

Four things happened there. It asked for the order number instead of guessing at one. It read the real record. It sent the customer to the order page for the payment details rather than reading them out. And it only mentioned an operator after one had actually been paged.

Build one from your own site
Guardrails

What it is told never to say.

Every vendor tells you their AI is accurate. This is the list of things this one is told never to say — and the layer that stops it anyway.

“Never state a specific rate, reserve, limit or AML outcome as fact, and never read out payment details of any kind.”

The exchanger guardrail. Chatonio writes it into your assistant when it reads your site.

Swipe — 4 rules

told never to

It won’t quote you a rate

The rate locked into an order is a fact on the record and it will read it back. What today’s rate is, what your reserve is, whether a limit applies — those move while the conversation is happening, and it is not allowed to state them.

enforced by the platform

It won’t say your money arrived

A payment is confirmed by your data or it isn’t confirmed at all. If nothing you gave the AI backs the claim, the message doesn’t get sent.

told never to

It won’t read out payment details

Not the card, not the wallet, not the recipient name — it is instructed to send people to the order page for those, however the question is phrased.

told never to

It won’t call an AML outcome

A hold is never a bot’s call. Your assistant is instructed to route it to a person rather than say anything about a review. In some jurisdictions, telling a customer their funds are under review is itself an offence.

The first, third and fourth are instructions your assistant follows. The second is enforced by the platform: a status or an amount that nothing in your data supports is blocked before it is sent, whatever the assistant was told.

not sentYour transfer has been sent — it should arrive within 10 minutes.
Blocked — nothing in your data says the payment arrived
Your order EX20487315 is still waiting on network confirmation — I can’t tell you it has landed. I’ve passed this on, and someone will pick it up here.

The first message is the kind of thing an ungrounded assistant sends at 4am. It never reached the customer. The second one did. Every block is written to an audit log, and the conversation is escalated automatically — you find out, not the customer.

It’s checked after it’s written
Every draft is audited against the evidence — this turn’s tool result, the customer’s own messages, your knowledge base — before it’s saved or sent.
When the check fails, it stays silent
If the audit errors or can’t parse the reply, the message is blocked. The failure mode is silence and a paged operator, never a confident guess.
It can’t promise a person it hasn’t paged
The AI is never allowed to tell a customer that an operator is coming unless the system has actually escalated and paged one.

What this doesn’t do

It blocks claims that nothing supports. It can’t tell you your own data is stale — if your order endpoint returns yesterday’s status, the AI will faithfully repeat it. And when it can’t reach your system at all, it says so and pages a person — it does not guess at what the answer would have been.

Around the clock

Nobody has to be awake. Nobody has to stay at the desk.

The AI is the first responder by default, not a fallback for when your staff are away. And a claimed conversation that goes quiet is worse than an unclaimed one — nothing else is going to pick it up.

It answers before anyone is online
A new conversation belongs to the AI from the first message. Nobody has to be on duty for a customer to get a real answer at 4am.
A timer you set
Five minutes by default. If a claimed conversation goes that long without a reply, the assistant comes back in.
Not a holding line
It’s the full assistant — your order lookups, your knowledge base, the same fact-checking. Not “sorry for the wait.”
Cancelled the second they type
An operator who does answer never sees the AI talk over them. And if you’d rather it stayed quiet while someone is online, that’s a setting: always, only when nobody’s online, or never.
The customer asks
“Where is my payment? I sent it 20 minutes ago.”
The AI looks up the order and answersanswers in seconds
Status, direction, amount and the rate locked into the order — read from your own record.
Needs a person?
Your escalation rules, an unmatched payment, or an operator who went quiet — here’s what happens next:
No
Answered from the order, and the conversation closes itself.
Yes
An operator is paged first — and only then is the customer told a person is coming.
Results

Half of this business happens while you’re asleep.

Not half the volume — half the outcome. A customer who sends money at 3am and gets no answer until 9am has already decided what happened to their money. Answering in seconds is the whole difference, and being awake for it costs about a cent a conversation — a conversation that runs several order lookups costs more.

And you can watch your own version

Insights records visits, chat-conversion rate and your own goals — an order-confirmation URL, or an event you fire from your own page — broken down by hour for your web chat, so you can see exactly what the night shift was costing you.

Overview · last 7 daysLive
Unique visitors
1,284
Up 46.3%
Visits
3,061
Up 38.2%
Visit duration
4m 12s
Up 22.9%
Chat conversion
8.4%
Up 52.1%
MonSun
Insights, on your own web chat. The figures shown are illustrative.
SwiftBitCoinLaneno access

SwiftBit · inbox

Dmitri K.
EX20487315 — payment not matched
Escalated
Alina P.
How long does manual review take?
AI
+•• ••• ••• 44 10
Order created, awaiting payment
AI

An operator scoped to SwiftBit cannot list CoinLane at all.

One inbox

Every exchanger you run. One inbox.

Operators in this market rarely run one brand. Chatonio is built for that — and for the fact that not every operator should see every brand.

One login, every project
Your exchangers, and the businesses that have nothing to do with exchange, in a single cross-project inbox.
Operators see one lane
An operator on Exchanger A cannot open, search or even list a conversation from Exchanger B. That’s a database filter, not a hidden tab.
You see all of it
Creating a project makes you its admin, so your cross-project view spans everything you run — and nobody else’s.
Notes the customer never sees
Leave a note your operators see and the client never does. It isn’t sent to the channel, isn’t shown in the portal, and isn’t even given to the AI.
Setup

Point it at your site. It writes the knowledge base.

The first hour is usually why this never gets done. Here it’s a paste and a review.

Swipe — 3 steps

1

Paste your URL

It reads your public pages and writes real knowledge-base articles, real FAQ entries and a first draft of your assistant’s instructions — in your language.

2

Nothing it can’t prove

The articles are your own pages, in your own words. And where it draws a conclusion about your business, it has to point at the exact sentence that supports it — anything it can’t, it drops.

3

Connect your order lookup

Bring your order endpoint and we wire the lookup with you.

Read 14 pages · wrote 31 articles · dropped 6 facts it couldn’t quote

Your script

Paste your ID. That’s the install.

Premium Exchanger has a field for your chat provider — choose Chatonio, paste your channel ID, and the chat is live on every page. No template to edit, no script tag, no HTML. Order lookups run over one endpoint from your script’s own API.

See how integrations work
The chat-provider field in an exchanger script’s admin settings, where the chat ID is pasted.The chat-provider field in an exchanger script’s admin settings, where the chat ID is pasted.

MoneyTop, iEXExchanger, ExchangeBox or your own build — the widget is a single snippet and the lookup route is the same one the live demo runs on.

Channels

Your customers are on Telegram. So is the AI.

Telegram one-to-one and Telegram groups, your website widget, WhatsApp, Viber and email — the same assistant and the same knowledge base behind all of them.

In a partner group, five parallel issues become five tracked threads instead of one unreadable scroll — each with its own status and its own assignee.

Exchanger FAQ

Questions, answered.

Will it quote a wrong rate or a stale reserve?
No. It isn’t allowed to state a rate, a reserve, a limit or an AML outcome as fact — those come from your system or they don’t get said at all. It answers the order question and leaves the pricing question to your page.
Can it look up an order by its number, like EX20487315?
Yes — that is the whole point. You connect your order endpoint once, and when a customer types an order number the AI calls it and answers from what came back: status, direction, amount, the rate locked into the order. If you don’t have an API, it can read the order page instead.
Half my volume comes through a Telegram partner group. Does that work?
One bot serves as many groups as you like, and inside a group the AI sorts each message into the right thread — so five parallel issues become five tracked threads with their own status and assignee, instead of one unreadable scroll. Telegram one-to-one, the web chat and the groups all land in the same inbox.
How long does it take to set up?
The knowledge base builds itself from your site in a few minutes, and reviewing what it wrote is an afternoon. The chat itself is just your channel ID pasted into your exchanger’s settings; the order lookup is wired to your endpoint with us.
I run three exchangers. Do I need three accounts?
No. One login covers every project, with a cross-project inbox that spans all of them. Operators are added per project, so an operator on one exchanger cannot see another’s conversations.
What happens when it can’t answer?
It escalates and pages an operator, and only then tells the customer a person is coming. It is never allowed to promise a human that nobody has actually been paged for.
Will it answer my customers in their own language?
It picks the language up from the first message and answers in it — a short greeting is enough. English, German, Spanish, Russian and Ukrainian ship with a fully translated interface; the assistant and your knowledge base work in 27 languages, and every article can carry its own version per language.
Where does my customer data actually live?
Your integration credentials are encrypted at rest and never returned by any API, attachment links are signed and expire, and every operator account can require two-factor sign-in.

Stop losing the 3am order.

Point it at your exchanger’s site and it writes its own knowledge base — free to try, no credit card.

See pricing