AI chatbot with human handoff for your website
The bot answers. You take the rest. Then it learns.
Nothing to integrate. A few choices to make. The chatbot, the support queue and the bubble already share one script tag. What turns them into a loop is a handful of settings: what the bot does when it does not know, what a handover carries, and what you do with your answer afterwards. This is the whole loop, stop by stop, and what a month of it costs.
Answer only from what you wrote.
And let people ask for a person.
The chatbot is the first line of reply. Give it your own words (a pasted policy, a page it can read, a question you answer every week) and it answers from those and nothing else. When your knowledge does not cover a question it does not guess: it sends your fallback message. And a small link under the box, Talk to a person instead, is there from the first message on.
- Knowledge
- Paste text, give it a URL, or write a Q&A for the question you get every week. Everything is split into short passages you can edit one at a time.
- Guardrail
- A question no source covers gets your fallback message instead of a guess, and that question costs nothing.
- Voice
- Pick a tone and an answer length. Answers stream in as they are written, and the chat always says it is an AI.
Not a dead end.
A flag, a ticket and an email.
The small link under the box, Talk to a person instead, opens one question: how can the team reach you? An email address or a phone number, either will do. Then three things happen without anyone lifting a finger. The conversation is flagged, an email lands with you, and if there is an email address it also opens as a support ticket with the conversation inside it.
- Your list
- Needs a human is a filter of its own in the chatbot, with a count at the top: how many are waiting on you.
- The ticket
- Subject Chat: and their last question, status Open, priority Medium, and the last twelve messages in the body.
- The email
- It names the visitor, quotes their last question, says how to reach them, gives the ticket number and links to the whole conversation.
- No email?
- A phone number on its own still reaches you, in the email. It just does not open a ticket.
A handover is a ticket you can work.
With the conversation already in it.
You never start from a blank page: the ticket already holds what the visitor asked and what the bot said, so you answer the real question. Tickets move through four statuses, carry a priority and keep a proper thread, and the visitor can look their ticket up later with their email and reference, so “any update?” does not become another message to answer.
- The queue
- Open, In progress, Resolved or Closed, with the counts on screen. A handover starts as Open.
- Priority
- Low, medium or high. A handover starts at medium; raise it when it cannot wait.
- The reply
- Replies are kept in order against the ticket. The visitor gets a reference they can quote back.
The bot’s own handover ends in a ticket and an email. Live Chat and Callbacks are separate blocks in the same bubble, for visitors who would rather go straight to a person. They are not part of the handover; add them when you can answer in time.
For the visitor who is still on the page and wants an answer now. Replies arrive in real time, each conversation shows the visitor’s name and email if they gave one, and a returning visitor lands back in the same thread.
Live Chat →For the visitor who would rather talk than type. One field and a tap, their timezone shown next to the request, and a queue you work first asked, first called. The block feeds the lead list you pick.
Callbacks →| When | Use | Because |
|---|---|---|
| The visitor asks the bot for a person | Support Tickets, automatically | A ticket with the conversation attached, and an email to you. |
| They are on the page and you are at your desk | Live Chat | Replies land in real time, and the thread can be picked up again later. |
| They would rather talk than type | Callbacks | Their timezone shows beside the request, and you ring back in order. |
| It has to happen at a fixed time | Bookings | Callbacks asks for “when you can”. Bookings is the sibling block for a fixed slot. |
Every gap you fill
is a question you never answer twice.
This is the step that makes it a loop. Once you have answered the visitor, the answer should not live only in a transcript. Under any assistant reply, Teach a better answer opens a small form: the question, and the correct answer you want given back. Add it to knowledge and the next visitor who asks gets your version.
- One action
- From the conversation: Teach a better answer, write the Question and the Correct answer, then Add to knowledge.
- Or the source
- If a passage is out of date, rewrite that paragraph. It retrains on the spot, is marked as edited, and the rest of the page is left as it was.
- The next one
- Visitors can rate every answer, and the unhelpful ones are counted for you. With Needs a human, that is your reading list for the week.
Ask it something it can’t answer.
Then teach it.
A toy assistant that knows two things, so you can watch the loop turn: a question it can answer, one it cannot, the handover, and your answer coming back the second time. As in the real widget, the link to a person sits under the box from the first message on. The real chatbot searches passages of your own pages; the shape of the loop is the same.
- Asked
- 0
- Answered
- 0
- Taught
- 0
Pick a question on the left.
Nothing is waiting on you.
Ask the same question again: it is answered now, and nobody has to.
Two stations have a rate.
The bot is billed at cost.
A new live chat is 1 credit and a ticket a visitor opens from the bubble is 1. The chatbot is different: each answer is billed at what it actually cost, every conversation carries its own running total, and a question no source covers gets your fallback message and costs nothing. Three settings put a ceiling on it. Every account gets 250 free credits a month, and packs start at $9.
Each new conversation started with you.
Each ticket a visitor opens.
- Live chats 1 credit per new chat 60
- Support tickets 1 credit per ticket opened from the bubble 25
It fits inside the free credits, with 165 to spare, before the chatbot’s answers.
Over by 0 credits, before the chatbot’s answers. One Starter pack (1,000 credits, $9) covers that for about 0 months at this size. Purchased credits never expire.
- Chatbot answers are billed at what each one cost, and every conversation carries its own running total. Three settings under Model & cost put a ceiling on it: Max answer length, Conversation memory and Answers per day, after which visitors are asked to leave their email instead.
- A question no source covers gets your fallback message and costs nothing.
- Callbacks have no separate rate on the rate card.
Six ways the loop stalls,
and the setting behind each.
- Cause
- A ticket only opens when the conversation has an email address. If the visitor left only a phone number, the handover reaches you by email but does not become a ticket.
- Fix
- Turn on Ask for an email before starting, so every conversation has one. For a phone number alone, the email to you says how to reach them.
- Cause
- The question is not covered by a source, or the passage that covers it is out of date. The bot answers only from your knowledge.
- Fix
- Add the page by URL or paste the text, then check the passages. Rewrite the stale paragraph: it retrains on the spot.
- Cause
- Either the credits ran out, or the Answers per day ceiling was reached. Both send a message instead of an answer.
- Fix
- Top up with a pack, or raise Answers per day under Model & cost, and open Usage history to see where the credits went.
- Cause
- The email is easy to miss and the queue is easy to forget.
- Fix
- Use the Needs a human filter on a schedule and answer from the ticket queue, where status and priority keep the list honest.
- Cause
- The reply went somewhere they did not look, or they never had a reference to quote.
- Fix
- Reply from the ticket so it is on the record, and tell them their reference: with it and their email they can look the ticket up themselves.
- Cause
- Offer to hand over to a human is switched off.
- Fix
- Turn it on in the chatbot’s guardrails. It is on by default, so check whether someone changed it.
Chatbot handoff, before you ask.
It is a chatbot that answers from your own content and lets the visitor ask for a person. In Builderify a small link under the chat box, Talk to a person instead, asks how the team can reach them. The conversation is marked Needs a human, you get an email, and if they left an email address it also opens as a support ticket with the conversation attached.
No, the visitor chooses. When your knowledge does not cover a question the assistant sends your own fallback message instead of guessing, and the Talk to a person instead link is there from the first message on. It is on by default, and the setting Offer to hand over to a human switches it off.
It is flagged Needs a human in the chatbot, and an email goes to you with the visitor's last question, how to reach them and a link to the whole conversation. If the visitor left an email address it also opens as an Open support ticket at medium priority, with the last twelve messages in the body. A phone number on its own reaches you by email but does not open a ticket.
Open the conversation, choose Teach a better answer under the reply that fell short, write the question and the correct answer, and choose Add to knowledge. The next visitor who asks gets your version. If a passage is simply out of date, rewrite that paragraph instead and it retrains on the spot.
You can, but they are separate blocks in the same bubble rather than part of the handover. The chatbot hands over to a ticket and an email. Live Chat suits visitors who want an answer now while you are at your desk, and Callbacks suits visitors who would rather be phoned.
A new live chat is 1 credit and a ticket a visitor opens from the bubble is 1 credit. Chatbot answers are billed at what each one cost, every conversation carries its own running total, and a question no source covers gets your fallback message and costs nothing. Three settings cap the spend: Max answer length, Conversation memory and Answers per day. Every account gets 250 free credits a month, packs start at $9 and purchased credits never expire.
4 modules, in the order a visitor meets them.
- 01 · AI chatbot trained on your website AI Chatbot Answers from your knowledge, hands over what it cannot, and takes in what you teach it.
- 02 · Support ticket widget Support Tickets Receives each handover as an open ticket, with the conversation attached.
- 03 · Free live chat for your website Live Chat The real-time door beside the bot, for visitors who want a person now.
- 04 · Request a callback widget Callbacks The phone door: one tap, their timezone, a queue you work in order.
Same script tag. A different job.
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.