How Kairos answers
AI Chat for Your Website That Answers From Your Own Pages, Then Books
What should a chatbot say when a visitor asks about a trip fee your website never mentions? "I don't know, but I can get you someone who does" is the right answer. Most bots are built to say something else, and that is where the trouble starts.
November 1, 2026 · 10 min read
The short answer
A good AI chat for a website answers only from the business's own pages, services, hours and published prices, says plainly that it is an AI, and books the appointment when the visitor is ready. Kairos, built by DataCram, does exactly that, admits when an answer is not in its material, and hands off to a person with the full transcript.
On this page
- The bot that guessed a price, and the customer who held you to it
- Trained on what your site already says, and nothing it doesn't
- A sample chat from first hello to a booked visit
- Guardrails that hold when a visitor pushes
- When Kairos stops talking and fetches a person
- "I'm an AI assistant" in the first line, and where health care fits
- A front-desk voice, typed
- The list of things Kairos will not do
The bot that guessed a price, and the customer who held you to it
Every owner who has tried a generic chatbot has a version of this story, and our comparison with off-the-shelf chat tools is fair to the good ones. A visitor asks what a water heater replacement costs. The bot, eager to please and trained on half the internet, names a number. The number is wrong, the customer screenshots it, and now the office is negotiating against its own website. The bot was not malicious. It was simply built to answer everything, which is a different job from answering correctly.
Kairos is built the other way around. Its first rule is that it answers from your material or not at all. Its second is that it never invents a price, a discount or an open appointment. Everything else on this page follows from those two. For the product as a whole, start at the Kairos overview; for what it costs, see Kairos pricing.
Trained on what your site already says, and nothing it doesn't
During the build we train Kairos on your own pages: the services you offer, the towns you cover, your hours and holiday closures, your policies on estimates, warranties and cancellations, and the prices you have chosen to publish. That set of material is the whole of what it knows about your business. It does not browse the web for a competitor's rates, and it does not fill a gap with a plausible guess.
Services and service area
What you do, what you do not do, and where. A visitor in a town you skip hears so plainly, along with the nearest place you do serve, if your pages name one.
Hours and policies
Regular hours, weekend coverage, what a diagnostic visit includes, how cancellations work. Quoted the way your site states them.
Published prices only
If your site lists a service-call fee, Kairos can state it. If the site lists nothing, Kairos says the price is set after a technician looks and offers to book that visit.
Booking rules
Which jobs can be booked online, how long each runs, and which need a phone call first. These come from you, not from the pages, and we write them down together.
On a DataCram site built with Athena, where Kairos is one of the Athena agents, it reads the content directly and keeps up as pages change, so a new holiday schedule is in the chat the moment it is on the site. On any other website, we refresh its material when your pages change, as part of the tuning every plan includes. Either way, the fix for a wrong answer is to fix the page, which also helps every visitor who never opens the chat.
A sample chat from first hello to a booked visit
The exchange below is an example written for a made-up plumbing company to show the mechanics. It is not a transcript from a client, and the $89 fee in it is invented for illustration.
| What was said | What Kairos is doing | |
|---|---|---|
| Kairos | Hi, I'm an AI assistant for this plumbing company. I can answer questions about our services or book a visit. | Disclosing that it is an AI in the first line, which is on by default |
| Visitor | Do you come out to Schertz? What does it cost to look at a tankless heater that won't heat? | Two questions in one message, as real visitors write |
| Kairos | Yes, Schertz is in our service area. Our site lists an $89 diagnostic visit to find the problem; the repair is priced once the technician sees it. Want me to find a time? | Answering from the service area page and the published fee, and declining to guess at a repair price nobody published |
| Visitor | Can you do it for $50? | Testing the edges |
| Kairos | I can't change prices or offer discounts. I can book the $89 visit, or have someone from the office call you. | Refusing to invent a discount, then offering two useful paths |
| Visitor | Fine. Tomorrow morning? | Ready to book |
| Kairos | Tomorrow I see 8 to 10 a.m. or 10 a.m. to noon open. Which works? | Offering only openings it can see in the calendar |
| Visitor | 8 to 10. Phone is 210 555 012. | One digit short |
| Kairos | That number looks one digit short. Could you check it? I'll also need your email and the service address. | Server-side validation catching the typo while the visitor is still there |
| Kairos | You're booked for tomorrow between 8 and 10 a.m. The office has your details and your notes about the heater. | Writing the booking and logging it in Clio against the page and source that started the chat |

Guardrails that hold when a visitor pushes
- No invented prices. Kairos states only prices your site publishes, in the same words. Anything else is priced by a person or after a visit.
- No invented discounts. It cannot offer a coupon, a price match or a first-time deal unless your published material contains one.
- No invented availability. It offers only times it can actually see open in your calendar. If nothing fits, it says so and offers a callback.
- Honest ignorance. When a question falls outside its material, it says it does not know and offers a person or a booking, rather than improvising.
- Clean contact details. Name, phone, email, address and job details are validated on the server before anything is saved or sent.
- Rules before eagerness. Your emergency, complaint and billing rules outrank its wish to book, every time.
None of these depend on the visitor being polite. We test each one during the build with the questions real customers ask and the ones a bored teenager would type, and Clio's searchable transcripts let you read any conversation afterward. The Clio dashboard page explains how to spot the chats that went sideways.
When Kairos stops talking and fetches a person
A chat assistant earns trust by knowing when to step aside. Kairos hands the conversation to a person in three situations, and the person receives the full transcript so the customer never retells the story.
- 1
The visitor asks for a human
Any clear request for a person ends the AI's part of the job. It confirms the handoff and says honestly when to expect a reply.
- 2
The question is outside its material
A commercial bid, an unusual install, a warranty dispute: if your pages do not cover it, Kairos does not guess.
- 3
Your rules say so
Emergencies such as a gas smell, sparking or water near a panel, complaints, and anything about money owed go to a person by rule, whatever the visitor says next.
- 4
The transcript travels with it
On every plan the handoff arrives by email with the whole conversation and the contact details. Handoff by text is rolling out to Growth and Pro plans and is not live yet.
At night, an emergency handoff should point the visitor to the on-call number rather than promise a reply in the morning. The after-hours booking guide covers that routing, and Kairos for home services lists the trade-specific rules we usually start with.
"I'm an AI assistant" in the first line, and where health care fits
Kairos tells visitors they are chatting with an AI assistant, and that disclosure is on by default. We think it is simply honest, and in some states it matters legally. Utah's S.B. 226, in effect since May 7, 2025, requires a business using generative AI in a consumer transaction to disclose that it is AI when a person clearly asks, and gives a safe harbor to AI that discloses "clearly and conspicuously" at the outset and throughout that it is generative AI, not human, or an AI assistant (the enrolled bill). Other states may set their own rules.
A front-desk voice, typed
Tone is part of the build. Kairos writes in short, plain sentences, uses the words your business uses (a "service call" or a "diagnostic," a "tech" or a "technician"), and skips the exclamation-heavy cheer that makes a chat window feel like a game show. We set the voice from your own pages and your answers to a few questions about how your best office person talks on the phone, then adjust it in the first weeks of tuning.
It is also built for every visitor. Kairos is designed to be usable by keyboard and with a screen reader, a commitment we design and test against rather than a certification we claim. Our reference point is WCAG 2.2, the W3C Recommendation whose success criterion 2.1.1 asks that all functionality be "operable through a keyboard interface without requiring specific timings."
The list of things Kairos will not do
Kairos will
- Answer from your pages, hours, policies and published prices
- Say it is an AI assistant from the first message
- Book open times it can see, or offer a callback
- Hand off with the transcript when asked or when rules require
Kairos will not
- Quote a price, discount or opening it cannot see
- Diagnose a problem or give medical, legal or financial advice
- Handle an emergency instead of routing it to a person
- Argue a complaint or discuss money owed
We know how to build AI that answers fast because we already run it: LeadBolt, our speed-to-lead software for contractors, and TeamAIOps, our AI employees that answer web chat and email in seconds and book the job. Kairos is a separate product with its own code. Running ServiceTitan? Read our ServiceTitan AI answering guide first, then see what each booking connection allows. Want AI beyond a website chat? That is our AI agent development work. Or start with a free site audit.
Questions owners ask about Kairos
A generic one can, because it answers from whatever it learned anywhere. Kairos answers only from your own pages and states only prices you have published, in your words. If a visitor asks about a price your site does not list, it says the price is set by a person or after a visit and offers to book or hand off. It never invents a discount either.
It says so. Kairos tells the visitor the answer is not in its material and offers a person or a booking. The handoff carries the full transcript by email on every plan, with text handoff rolling out to Growth and Pro. Clio's questions report then lists what it could not answer, so you can add the page that fills the gap.
Rules vary by state. Utah's S.B. 226, effective May 7, 2025, requires disclosure when a person clearly asks, and gives a safe harbor to AI that discloses clearly at the outset and throughout. Kairos discloses that it is an AI assistant in its first message by default. We are not a law firm, so your counsel confirms what applies to you.
For scheduling questions, yes: hours, locations, appointment types and booking an open time. Kairos is not built for protected health information, so it should never collect symptoms, records or insurance details, and we configure it to steer away from them. A practice with stricter needs should have its compliance officer review the setup before launch.
Like your business on a good day. We set the voice from your own pages and from how your best front-desk person talks: short sentences, your terms for services, no forced cheer. The first weeks of tuning adjust it based on real conversations, which you can read in Clio's searchable transcripts.
Yes. Kairos is designed to work by keyboard and with a screen reader, and we test it that way during the build. We treat this as a design commitment measured against WCAG 2.2, the W3C accessibility guideline, not as a certification, because no chat widget earns a certificate on its own.
Keep reading
- The Clio dashboardClio, the Chatbot Analytics Dashboard That Counts Bookings, Not ChatsClio tracks every Kairos chat from widget open to booked job, by page, ad and campaign, and lists the questions your site leaves unanswered. On every plan.
- The night shiftAfter-Hours Booking for Small Businesses: What Your Website Does Between Closing Time and 8 a.m.What happens to a 9 p.m. website visitor today, how a 24/7 online booking chat captures and books the lead, and what should wait for the on-call phone.
- Kairos pricingAI Booking Widget Cost: $575 to Build, Then $99, $199 or $349 a MonthAI chatbot pricing for small business, spelled out: a $575 build, then $99, $199 or $349 a month by conversations. What each plan adds and what is quoted.
- Comparing your optionsCustom AI Chatbot vs Tidio, Intercom, Live Chat and Answering Services: An Honest Buyer's ComparisonChatbot alternatives for small business, compared fairly: Tidio, Intercom Fin, LiveChat, answering services and a custom AI booking widget, priced Nov 2026.
- Attribution for chatHow to Track Chatbot Conversions in Google Ads, GA4 and Meta When the Booking Is the WinCarry UTM tags and the Google click ID through a chat, count the booked appointment as the conversion, and send it to Google Ads, GA4 and Meta correctly.
- From kickoff to launchHow to Add AI Chat to Your Website: The Kairos Setup From Kickoff to the First Month of TuningHow a Kairos AI booking widget gets built: kickoff, training material, booking rules, design, testing with real questions, launch, and a launch checklist.
- Everything in Kairos AI Booking WidgetSee the section
Read the answers before your customers do
Send us the five questions your office hears most. We will show how Kairos would answer each from your own pages, and where it would hand off.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.