Luca Moretti
09:13I was charged twice for the same invoice.
One inbox for every channel, with an AI agent that resolves the routine and hands the rest to your team.
Resolved today 1,284
I was charged twice for the same invoice.
Can I move my delivery to Thursday?
Done. Your order now arrives Thursday between 9 and 12.
I want to cancel and I'm quite upset.
Third contact this week, asks to cancel. Tone: frustrated.
Jonas is replying
Trusted by more than 400 support teams
Half a minute, start to finish. No sound needed.
Your customers write from wherever they already are. Your team answers from one place, with the full history in front of them.
One queue
Luca Moretti
I was charged twice for the same invoice.
Hannah Bergström
Where do I download last month's receipt?
Kofi Mensah
Do you ship to Ghana?
02:47
A customer writes at 02:47. The agent replies within seconds, in the language the customer wrote in.
02:48
Account details are only read when the customer's identity has been verified by your own system. Otherwise the agent answers in general terms.
02:51
Refunds, cancellations, anything it is unsure about: the agent stops, writes a short note, and opens the conversation for a person.
08:30
The morning shift finds the conversation waiting with the note attached. Nobody asks the customer to repeat themselves.
I was charged twice for the same invoice.
Hi Luca, sorry about that. Let me take a look.
Identity verified by your system
I can see two charges of €184 on 12 September.
Note for the team: two charges of €184 on 12 Sept. Refund needs a person.
Maya
Refunded, Luca. It will reach your card in 2 to 3 days.Resolved at 08:34
These are not settings. They are how the agent is built.
Every reply is attempted exactly once. If the outcome is unclear, the agent does not retry. It asks a person to look.
Your systems are only queried for a customer whose identity is cryptographically verified. The agent cannot choose whose data it sees.
Ownership is checked again in the instant before sending. If a teammate has taken the conversation, the agent's draft is dropped.
Every event is signature-checked against the raw bytes and rejected if it is more than five minutes old.
Logs record what happened, not what was said. Conversation memory is bounded and expires on its own.
Everything a team needs to run support day to day is already here.
Publish articles by category and language. Your team links to them mid-conversation.
refund
Label, assign, and prioritise on arrival. Macros turn a five-step routine into one click.
Route by inbox, team, or round robin. Everyone sees who owns what.
Volume, first response, and resolution time by agent, team, inbox, and label.
One tap for the customer. A trend line for you.
How did we do?
The agent replies in the language it was written to. The dashboard ships in more than thirty.
REST endpoints and signed webhooks for every conversation event.
{
"event": "conversation_status_changed",
"id": 4822,
"status": "open",
"assignee": "maya@haldenfreight.com"
}Paste the widget snippet, forward your support address, and link WhatsApp, Instagram, and the rest.
Optional. Point the agent at one signed endpoint in your product so it can see orders, plans, or bookings for verified customers.
Pick the inboxes the agent covers. Your team watches it work and can take any conversation at any moment.
Last month, 412 teams handled 2.1 million conversations on Satisfy Chat. 68% never needed a person. The rest reached one in 41 seconds.

“We used to open to 140 tickets at 8am. Now it is eleven, and each one has a note saying exactly what is needed.”
Ingrid SolbergHead of Support, Halden Freight
92%fewer tickets waiting at 8am
Run Satisfy Chat in our cloud or on your own servers. It is the same product either way, built on an open-source core you can read.
We host, patch, and scale it.
You run it on your own infrastructure.
On the roadmapSLA timersAudit trailSingle sign-onReply suggestions for agents
It says so, writes a short note for your team, and opens the conversation for a person. It does not guess, and it does not keep the customer in a loop.
Yes, at any moment. The agent checks who owns the conversation in the instant before it sends. If a person has taken over, its draft is discarded.
Claude, from Anthropic. On a self-hosted deployment you bring your own key, so usage and data terms are between you and Anthropic.
Only through one endpoint that you build and sign, and only for customers your system has verified. You decide what that endpoint returns. The agent never touches your database.
No. Satisfy Chat is a complete support desk on its own. Turn the agent on for one inbox, watch it for a week, and widen it when you trust it.
Most teams connect their channels in an afternoon. A customer context connection usually takes a developer two or three days.
A 30 minute walkthrough on your own channels, with a person from our team.