From kickoff to launch
How to Add AI Chat to Your Website: The Kairos Setup From Kickoff to the First Month of Tuning
Adding AI chat to a website takes about four minutes if you only count pasting the script tag. Everything else, what it may say, what it may book and when it must fetch a human, is where the result gets decided, and it is most of this page.
November 1, 2026 · 9 min read
The short answer
To add AI chat to a website properly, decide what it should answer and book, gather the training material, write the booking and handoff rules, connect the calendar, match the design, test with real customer questions, then launch with one script tag. A Kairos build follows those steps and then tunes the widget through its first month using real conversations.
On this page
- One line of code, and the forty decisions behind it
- Seven steps from kickoff call to a widget that books
- What you hand over, and the one thing we never ask for
- Booking rules to settle before a single slot goes live
- Rehearsal day: trying to break it on purpose
- Launch checklist for an AI booking widget
- The first month: tuning from conversations that actually happened
One line of code, and the forty decisions behind it
Kairos runs on any website through a single script tag, so the installation itself is the same on WordPress, Wix, Squarespace or a hand-built site. On a site DataCram builds with Athena, the widget reads the content directly and stays in step as pages change, which removes the most common way chatbots go wrong: giving last spring's prices to this fall's customers.
The decisions behind the tag are the real build. Every Kairos project starts with a one-time fee from $575 that covers the custom design, training on your site, one booking connection, the Clio dashboard and conversion tracking setup. More connections or unusual booking rules are quoted at kickoff, before work starts. The Kairos overview describes the product; this page is the build itself.
- What the widget may answer, and from which pages
- What it may book, for whom, and how far ahead
- When it must stop and hand the visitor to a person
- What it looks like, where it sits, and what it says first
Seven steps from kickoff call to a widget that books
- 1
Kickoff
A call with the owner and whoever answers the phone today. We list the questions customers ask, the jobs you want booked online, the ones you do not, and where your schedule lives.
- 2
Gather the training material
Your service pages, service area, hours, policies and published prices. Where something is missing, we flag it; the widget cannot answer from a page that does not exist.
- 3
Write the booking and handoff rules
Appointment types, durations, lead times, who can be booked, and the situations that always go to a person: emergencies, complaints, anything about money owed, requests for a human.
- 4
Connect the calendar
A Google Calendar or Microsoft 365 business calendar, or Kairos's own scheduling if you keep no calendar. Booking into ServiceTitan, Housecall Pro, Jobber or FieldEdge is rolling out and not live yet. You grant access inside your own account.
- 5
Design and placement
Colors, type and tone matched to your brand; a chat bubble, a Book now button, or an inline booking panel on service pages, wherever it helps.
- 6
Test with real questions
Your staff and ours throw the actual questions at it, including the awkward ones, until the answers and the handoffs are right.
- 7
Launch, then a month of tuning
The script goes live, Clio starts recording, and we review conversations through the first month, fixing answers and rules as real visitors arrive.
The timeline depends mostly on how quickly material and account access arrive, so we set a launch date at kickoff rather than promise one on a web page. The connection steps for each platform are covered on the integrations page.
What you hand over, and the one thing we never ask for
| Why it matters | Example | |
|---|---|---|
| Services and published prices | The widget answers prices only as your pages state them | Diagnostic visit fee, cleaning packages, consultation rates |
| Service area | It checks addresses before offering times | A list of towns or ZIP codes, and any edge-of-area charge |
| Hours and holiday hours | After-hours routing and booking windows depend on them | Closed Sundays; on-call after 6 p.m. |
| Booking rules | They decide which slots a visitor ever sees | Estimates take 90 minutes; no same-day bookings after 2 p.m. |
| Handoff contacts | A rule can only route to a person who exists | Office email for routine handoffs; on-call number for emergencies |
| Your top questions | They become the first test set | The twenty questions the front desk answers every week |
| Brand files | So it looks like your site, not a vendor's | Logo, colors, fonts, a sentence about your tone |
For the platform connections that are rolling out, the API guides for ServiceTitan, Housecall Pro, Jobber and FieldEdge explain who in your company can approve access and what each platform permits.
Booking rules to settle before a single slot goes live
Most booking problems are rule problems wearing a technology costume. The widget will offer exactly what the rules allow, so a missing buffer becomes a technician scheduled across town with zero travel time. Write these down at kickoff and the calendar behaves.
- Appointment types and lengths. One standard visit, or several booking types with their own durations and rules.
- Lead time and horizon. How soon a visitor can book, and how far ahead the calendar opens.
- Buffers. Travel or prep time between visits, which most calendars do not know about unless told.
- Who is bookable. Which people or crews take online bookings, and whether jobs need office approval first.
- What never books online. Emergencies, large commercial bids, anything you want a person to qualify.
- What happens when the calendar is full. The earliest real opening, or a callback request. Kairos never invents an opening it cannot see.
On the calendar side, availability comes from the provider's own free/busy lookup. Google describes its Calendar API's freeBusy query as returning "free/busy information for a set of calendars." Microsoft's getSchedule documentation lists it for work or school accounts and marks personal Microsoft accounts as not supported, which is worth knowing if your calendar lives in a personal Outlook.com account.
Rehearsal day: trying to break it on purpose
Testing is where a chat widget becomes trustworthy, and the best testers are the people who answer your phone. They know the odd questions, the misspellings, the customer who asks for a discount in the first sentence. We give them a test version and a simple brief: ask what customers ask, then ask what you hope they never do.
The everyday twenty
Hours, area, prices, what a visit includes, how to reschedule. Each answer must match your pages word for word on the facts.
The traps
Requests for discounts, prices you do not publish, a time that is not open. The right answer is honest and offers a person or a booking.
The handoffs
An emergency, a complaint, a billing question, a plain "let me talk to someone." Each must reach the right inbox with the transcript.
The devices
A small phone, a desktop, keyboard only and a screen reader. Usability by keyboard and screen reader is a design commitment we test, not a certification we claim; the W3C's WCAG 2.2 is the reference we test against.
The disclosure
The first message says the visitor is chatting with an AI assistant. That setting is on by default and stays on.
The AI chat page explains how answers are constrained to your material, and the home services page shows the emergency rules a trade business usually adds.
Launch checklist for an AI booking widget
| How to check | Done when | |
|---|---|---|
| AI disclosure | Open the widget fresh on a phone | The first message says it is an AI assistant |
| Booking lands | Make a real test booking for each booking type | It appears in the calendar with full details, then is removed |
| Handoffs route | Trigger each rule: emergency, complaint, billing, ask for a person | Each transcript reaches the named person |
| Contact capture | Submit a bad phone number and a missing address | The server rejects them and the widget asks again |
| Sources recorded | Visit with a tagged link, then book | Clio shows the booking with its page, source, medium and campaign |
| Placement | Check service pages, the home page and the contact page | The bubble, button or panel appears where agreed and covers nothing important |
| Out-of-scope honesty | Ask something the site never mentions | It says it does not know and offers a person or a booking |
If you are tracking ads, the conversion tracking guide adds the checks for click IDs and conversion destinations.
The first month: tuning from conversations that actually happened
Launch is a draft. Real visitors phrase things in ways no rehearsal predicts, and the first weeks of transcripts are the most useful material the project will ever produce. Tuning is included on every plan, and through the first month we go over the conversations with you, not just on our own.
Clio makes the review fast. Its questions report lists what visitors ask most and what the site does not answer, which turns into a short list of pages to write; on an Athena site, the Prometheus agent can draft them for approval. The funnel shows where conversations stall between opening, engaging, leaving contact details and booking. Booking rate, bookings divided by conversations, becomes your baseline. Kairos is new, so there is no industry average from us to compare against, and we will not invent one. The analytics dashboard page explains each measure.
The widget you launch is a guess. The widget you have after a month of transcripts is a fact.
After the first month, plans run month to month: Core at $99, Growth at $199, Pro at $349, details on the Kairos pricing page. If the website itself needs care, hosting and maintenance starts at $55 a month, and new sites from $1,500 are on the web design pricing page. Not sure where to start? A free site audit is the low-commitment first step, and the Kairos and Clio agents are described with the rest of Athena.
Questions owners ask about Kairos
It depends mostly on how fast the material and account access arrive, and on how many booking connections and rules are involved. We set a launch date at the kickoff call once we know both. The installation itself is a single script tag; the work is in the rules, the training and the testing.
Yes. Kairos installs with one script tag, so it works on any website you can add a script to. On a site DataCram builds with Athena, it reads your pages directly and stays current as they change; on other platforms, tell us when your content changes and we update its training as part of tuning.
No. You approve access inside your own Google or Microsoft account using that provider's own approval screen, and later your field-service account when those connections are live, and you can revoke it whenever you like. We never ask for a login, and keys are kept on the server, not in the browser.
A list of your services and any prices you publish, your service area, hours including holidays, the jobs you want booked online and the ones you do not, the people who should receive handoffs, and the questions your front desk answers every week. Missing pages are fine; we flag them during the build.
We go through the real conversations with you, fix answers that miss, adjust booking and handoff rules, and use Clio's questions report to find pages your site should add. Tuning continues after that on every plan, but the first month is when the widget changes most.
On an Athena site, editing your own pages updates what Kairos knows, because it reads them directly. Rule changes, such as a new booking type or a new handoff contact, go through DataCram as part of the tuning included in every plan, so nothing changes without being tested first.
Keep reading
- Booking connectionsChatbot Calendar Integration: Where Kairos Can Book, and How Far Each System Lets ItWhere Kairos books today (Google Calendar, Microsoft 365, its own scheduling), the field-service connections rolling out, and each system's limits.
- 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.
- How Kairos answersAI Chat for Your Website That Answers From Your Own Pages, Then BooksA custom AI chat for small business websites: trained on your pages, never invents a price, says it is an AI, hands off with the transcript, and books.
- 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.
- Chat for the tradesAI Chat for HVAC, Plumbing and Electrical Websites That Knows a Burst Pipe From a Tune-UpA home service chatbot built for the trades: emergency triage, service-area checks, member and financing answers, then a booked visit on your calendar.
- 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.
- Everything in Kairos AI Booking WidgetSee the section
Start your Kairos build with a short kickoff call
Tell us where your schedule lives and what you want booked online. We will list what we need from you, what is included in the build, and anything that would be quoted.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.