Chat that does the first conversation
It answers at any hour, asks what the work involves, and hands you the whole exchange.
In short
A chat assistant earns its place when it does two jobs at once. It answers the questions people ask before they get in touch, from your own material rather than from the internet. And it finds out enough about the visitor that your first reply is already informed. The one on this site does both. It reads these pages, answers from them, asks two or three questions, and sends the conversation over with the pages the visitor read and how long they spent on each. That is the difference between an inquiry and a name in a form.
Work it out in a minute
Nine questions across revenue, capacity and control. Shows which of the three is costing you most, and where to start.
What we take on
Built on your material
It answers from your pages, your documents and your own way of describing the work, so what it says matches what your team would say. When it does not know, it says so and hands over to a person.
It asks, then it hands over
Two or three questions that tell you whether this is worth a call. You get the transcript with those answers already in it, and the visitor gets a reply that knows their situation.
The whole visit comes with it
Which pages they read, how long they spent on each, and where they arrived from. Four minutes on one guide is a different call from six pages in ninety seconds.
Your languages, your hours
It replies in the language it is asked in, at three in the morning, on the days your team is closed. Buyers in other time zones get an answer.
What makes one worth having
Most of the value is in the second job rather than the first. Answering questions is useful and it is also the part every chat widget claims. The part that changes a week is arriving at your desk already knowing that the caller runs a distribution business, has forty staff, and is asking about invoicing rather than websites. You reply once, properly, instead of three times to find out.
It has to read your own material. An assistant working from general knowledge will answer confidently and wrongly about your scope, your process and your timelines, and it will do it in your voice. Ours is built on the pages of the site it sits on, so an answer it gives is an answer you have already published.
It also has to know when to stop. The useful behavior is a clean handover: say plainly that a person should answer this, take the details, and pass it on. An assistant that will attempt anything is one you have to supervise, which is the opposite of the point.
The one on this page is the same build. It reads these pages, answers from them, asks what you are working on, and sends the conversation over with the route you took to get here. You can test every claim on this page by opening it.
Questions we get
Is this the same as the chat widget our website builder offers?
Those answer from a list of canned replies or from a general model with no knowledge of your business. Useful for opening hours, thin for anything else.
This is built on your own material and it passes you the conversation with the visitor journey attached. The work is in what it knows and what it sends you, rather than in the bubble in the corner.
What does it do when it does not know something?
It says so, takes the details, and hands over. That behavior is designed in rather than hoped for.
An assistant that answers everything is one somebody has to check. One that knows its edges is one you can leave running.
Can it book a call or take an order?
Yes, and whether it should is worth a conversation first. Booking works well when the next step is genuinely a calendar slot.
Where the next step needs judgment, it is better for it to gather the facts and hand over. Try the automation scorecard on this site for the same question applied to any task.
How long does one take to build?
Weeks rather than months for a first version you can put in front of people, and it improves from real conversations after that.
The build is quick. The part worth spending time on is deciding which two or three questions it should ask, because that is what decides whether the transcript is useful.
What happens to what people type into it?
You decide where it goes and how long it is kept, and that is settled before anything is switched on.
On this site the conversation is emailed and stored, and nothing is passed to a third party for training. Your build gets the same treatment, written down.
Can you put one on a site you did not build?
Yes, and most of them are. It needs a way to read your content and a place to send the conversation.
If the site is somebody else's work, the first pass is finding out what it runs on. That inventory is worth having anyway and you keep it either way.
More in the guides and every answer in one place.
Shaheer Shaikh, C-suite operations lead for a San Francisco AI company working with global pharma on clinical trial data and model benchmarking. Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. More about the firm