AI Chatbots
A support assistant that answers from your own docs
A chat assistant trained on your actual docs, pricing, and policies - answering the repeat questions so your team handles the ones that need a person.
It reads your content, and nothing else
Answers sourced from your docs, FAQ, and policies - not a generic model guessing.
- Help centre articleshelp.yoursite.comHow-to, shipping, returnsRe-read when an article is published
- PoliciesReturns, warranty and privacy pagesWhat is allowed, word for wordRe-read when a policy changes
- Product catalogueYour store or product databaseSizes, care, price, stockRead live, so a price is never stale
- Order statusYour order system, read-onlyWhere is my order, and nothing moreLooked up per question
- Replies your team approvedSaved answers in your helpdeskTone, and the edge cases docs missAdded as your team saves them
Not the open web, and not a guess. If none of the above has the answer, it says so.
It knows when to stop and fetch a person
A clear path to a real person the moment a question needs one. The rules are written with your support lead, before launch.
| When the customer | The assistant | Goes to |
|---|---|---|
| Asks where an order is, or how to return something | Answers, and shows the article it used | Stays with the assistant |
| Asks for a refund, a discount or an exception | Explains the policy, then hands over | Support, a person |
| Asks for a person, in any words | Hands over at once - no "are you sure?" | Support, a person |
| Asks something your content doesn't cover | Says it doesn't know, and offers a person | Support, a person |
| Is still stuck after two answers | Stops trying, and hands over with a summary | Support, a person |
| Asks about a bulk or custom order | Takes the details, and books a call | Sales, a person |
An example set - your rules are your own.
Placed where your users are
Embedded on your site, in-app, or wherever the conversation already happens. One set of sources and rules behind all of them.
On your website or in your app
A launcher in the corner of every page, opened on the page the customer is already reading.
On WhatsApp
The same answers in the thread your customers already use, on your business number.
In the support inbox
Replies to the easy emails, and drafts the rest for a person to check and send.
Worth building, or not yet
Worth building if
- You get repeat questions your team answers the same way every time
- You have docs, FAQs, or policies worth grounding answers in
Not yet, if
- You need the bot to make account-specific decisions with no human check
- Your product changes faster than documentation can track it
Questions we get asked
Does it make things up?
It answers from the sources listed on this page - your help centre, policies, catalogue and approved replies. If the answer isn't there, it says so and offers a person instead of guessing.
What happens when it hands over?
The conversation goes to a person on your team with a short summary attached, so the customer doesn't have to repeat themselves.
Can it issue a refund or change an account on its own?
No. It can read an order's status, but decisions about a customer's account go to a person. If you need those made with no human check, it isn't a fit yet.
Where can it run?
On your website, inside your app, on WhatsApp and in the support inbox - wherever the conversation already happens.
Who decides the handoff rules?
You do. We write them with your support lead, and they can be changed as you learn which questions need a person.
How is it priced?
Tell us where your questions come in and what content you have, and we come back with scope, a timeline and a price.
Answering the same questions every day?
Send us your help centre and the questions that come in most - we come back with what it would answer, and where it would hand over.