It answers your customers at 23:00.
It reads your product sheets, manuals and past tickets, replies in the language it was asked in, and names the page the answer came from.
Every answer
has a source.
It answers your customers out of your product sheets, manuals, terms and past tickets. Every reply names the page it came from, so nobody has to take its word for it.
Book the callThe same field, on your website, is the reason your inbox stops repeating itself.
Product sheets, manuals, terms, past tickets. Only what you have cleared for the public, never your internal folders.
Every answer names the file and the page. The customer can check it, and so can the colleague who picks up the escalation.
Anything the shelf does not cover goes to a person, with the question and the thread already attached.
The same mechanism, on a catalogue we invented.
Below is a working shop with 193,620 products and an assistant reading the same data the page does. It checks whether a bulb fits a socket, whether a lamp belongs in a bathroom, and assembles bills of materials. Yours would read your catalogue instead.
Loading the demo …
Phone screens are the wrong shape for a shop and a chat panel at once. The demo opens full-screen instead.
Open the demoThe shop, brands, products and prices are invented and the catalogue is synthetic — it contains no customer data. To prevent abuse, the number of questions per visitor is limited.
Your customers ask at every hour. Somebody should answer.
Most of what lands in a support inbox has been answered before: in a manual, in the terms, or in a ticket from March. Those questions do not need a person. They need the paragraph, quickly, and in the language they were asked in.
A question that would otherwise have waited until Monday, answered in two seconds, and a lead that arrives with the article numbers already on it.
Three tickets that never reached a person, and one that did, arriving with the diagnosis already written.
Every document behind these three answers is in German. Nothing was translated in advance, and no page of your site had to change.
It reads the shelf you clear for it.
No new system to fill and no re-writing the handbook. We point it at documents you have cleared for the public, and nothing outside that shelf is ever within reach.
Four steps, and you can check every one.
One real customer question followed the whole way through. This is the part that decides whether you are willing to put it in front of people who can buy from you.
The question arrives
On the product page, in the helpdesk widget, or in WhatsApp. Wherever your customers already are, without an account to make first.
It finds the passages
Not a web search. It ranks paragraphs out of the shelf you cleared and keeps the exact location of each one it used.
It answers in your words
Short, in the language of the question, quoting the passage rather than summarising it into something softer.
It stops when it should
Where the shelf does not reach, it says so and hands the thread to a named person instead of inventing the rest.
What it refuses to do.
Where it runs, and what it can reach.
Four weeks from the call to live.
Thirty minutes with both founders. We read a week of your support inbox and count how much of it a document already answers. If that number is small, we tell you, and there is nothing to build.
We agree exactly which documents the public may hear from. That list is the entire security model, and settling it takes an afternoon rather than a project.
We run it against the real questions out of your inbox. Your team marks what comes back wrong. That correction loop is most of the work, and it is why we need a few hours of your time.
The Front Desk starts on the product pages rather than the whole site, with numbers attached: answered, handed over, and correctly refused.
The rest of the site, more languages, or the helpdesk. Or a workshop so your own people can extend it without us in the room.
What we need from you
- A week of your support inbox, so we can count what repeats before anything gets built.
- The documents you are willing to let the public hear from. Read access, nothing more.
- One person who can say yes to wording. Roughly two hours a week.
That is the whole ask. If that week of inbox turns out to be genuinely unrepeatable questions, we will say so on the call rather than build something that deflects nothing.
Send us a week of your support inbox.
Thirty minutes with both founders. We will count how much of it a document already answers, and tell you plainly if the number is too small to be worth building.
Book the call