Customer support & assistants
Customer support run by AI: on your website and in your inbox.
One assistant answers visitors 24/7 on your website. A second drafts the replies in the support inbox — your agents review and send.
Support inbox · drafts ready
“Is this model compatible with 2019?”
DraftReply drafted from the datasheet, source cited. Waiting for you to send.
“What's the lead time to Namur?”
DraftStandard lead time given. One click to correct, one to send.
“I'm disputing my invoice.”
Handed overOut of scope: no draft, passed to the right team.
18 drafts · 0 sent without you
- 24/7
- The chat answers at night, at weekends and during peaks.
- 90%
- Of your customers' questions covered by the two channels.
- Zero hallucination
- No answer? It says so and hands over to the right person.
Two ways to automate your customer support
On your website
The chat answers the visitor, right away.
- 24/7, evenings and weekends included
- Answers from your own product data, documents and procedures
- Can read an external source: stock, catalogue, order tracking
- Hands over to a human as soon as it leaves its scope
In your inbox
The draft waits for you to send.
- A reply drafted for every incoming email
- The same knowledge base as the chat
- Never sent on its own: your agents review and correct
- Nothing drafted on a sensitive case — it goes to a human
Why your support answers too late
Nobody waits an hour for an answer any more. A question left hanging means an unhappy customer or a prospect buying elsewhere — and in the evening or at the weekend, there's nobody to answer.
A reply that takes two hours: the customer has already moved on.
A simple answer going out two days after the request.
Nothing in the evening or at the weekend, while traffic carries on.
The information exists, but between a PDF, the website and a colleague's head.
Scripted chatbot, or AI assistant?
Understanding the question
A scripted chatbotKeywords spotted in a sentence. Rephrase it and it loses the thread.
An assistant connected to your dataThe real meaning of the request: what the customer is after, their context, what they didn't spell out.
What it knows
A scripted chatbotThe answers written in advance.
An assistant connected to your dataEverything your documents contain.
An unexpected question
A scripted chatbot“I didn't understand.” Then the menu, again.
An assistant connected to your dataA constructed answer, or an honest hand-over.
Updates
A scripted chatbotRewriting the scripts on every change.
An assistant connected to your dataYou edit the document, it follows.
Trust
A scripted chatbotNo way to tell where the answer came from.
An assistant connected to your dataEvery answer cites its source.
What changes for your customers and your teams
- Up to 90%
- Of your customers' questions absorbed by the two channels — your agents only handle what needs judgement.
- Zero hallucination
- Without the information, the assistant doesn't answer: it hands over to the right person.
- Everything logged
- Questions, answers, hand-overs: you see what's missing and the base improves continuously.
It plugs into the tools you already use.
Our agents work inside your software, not next to it: email, CRM, ERP, documents, calendar. When a business tool has no connector, we plug into its API.
Outlook
Gmail
SharePoint
Notion
HubSpot
ZohoWhich industries it fits
Your data stays in Europe, and it stays yours.
All our guaranteesHow we work
- Fixed price, not time and materials
- The price is set upfront and doesn't move. We iterate until it runs, at no extra cost — scope drift is our problem, not yours.
- Quote within 24 hours
- A 30-minute conversation, then a costed quote within 24 hours. Go-live takes one week to one month depending on complexity.
- You can own it
- On request, the solution is deployed on your environment and the code is yours. Otherwise we host and maintain it — it's an option, not a requirement.
