Clio, the Chatbot Analytics Dashboard That Counts Bookings, Not Chats

Conversations handled is a number that flatters everyone

Chat vendors love the conversation count because it only goes up. A visitor who asks whether you are open Sunday and leaves is a conversation. So is a bored visitor testing whether the bot will write a poem. Neither paid for anything. An owner who judges a chat widget by conversations handled is grading a front desk by how often the phone rang.

Clio, the dashboard behind every Kairos widget, starts from the other end. The question it answers first is how many appointments the chat booked, and from which pages and which ads. Conversations still appear, because they are the denominator. They are just not the headline. Clio is included on every Kairos plan and is set up during the build; Kairos pricing has the details.

Every number on the Clio screen, defined

Two definitions deserve emphasis. Booking rate uses conversations, not widget opens, as its denominator, so it measures the chat rather than the placement. And a booking is counted only when an appointment is written, not when a visitor says "sounds good." The AI chat page explains what Kairos does in the conversation itself.

A sample week, labeled loudly as a sample

Reading the funnel from the open to the booking

Clio draws the funnel in four steps: opened, engaged, contact captured, booked. Each gap points at a different fix, and the fix is rarely "make the AI smarter."

• Opened to engaged. A wide gap usually means the greeting or the placement, not the answers. Try a panel on the service page instead of a bubble in the corner, or a first line that names a real job; Kairos for home services has trade examples.
• Engaged to contact captured. Visitors who ask and leave often got their answer, which is fine, or hit a question the site does not cover. The questions report below shows which.
• Contact captured to booked. This gap is usually the calendar: no openings soon enough, or a job type that requires a call first. Check the handoffs list for the pattern.
• The whole funnel by page. A page with many opens and few bookings is a page with a mismatch between what it promises and what the chat can book.
• The whole funnel by hour. If the after-hours share is high and the bookings are not, the evening booking rules need another look; our after-hours guide covers them.

Which page, which ad, which campaign started the chat

Every conversation in Clio carries its origin: the page the chat began on, and the visit's source, medium and campaign from its UTM tags, plus the Google Ads click ID when the visitor arrived from an ad. That is how a booking gets traced to the search ad, the Facebook post or the email that brought the visitor, instead of being filed under "website." This attribution is part of Core and works today.

It also settles arguments. When the ad agency says the campaign is working and the office says the phones are quiet, Clio shows whether that campaign's visitors are booking or merely chatting. If the tags on your ads are missing or inconsistent, our conversion tracking setup service fixes them, and the chat booking tracking guide walks through the tagging itself.

Conversion sync to Google Ads, GA4 and Meta, now rolling out

The next step is sending each booked appointment back to the ad platforms as a conversion, so their bidding learns from bookings rather than from chats. That conversion sync is rolling out to Growth and Pro plans and is not live yet. Here is what it will rely on, in each platform's own words, as of November 2026.

• Google Ads. Google assigns a Google Click ID (GCLID) to each ad click; for offline conversions you store the GCLID with the lead and later give it back to Google Ads with the conversion details (Google's help page). Clio already stores it.
• Google's 2026 change. "Starting June 15, 2026, offline conversions import and enhanced conversions for leads uploads will be migrated to the Data Manager API and blocked in the Google Ads API," according to Google's enhanced conversions page. New work is built on the Data Manager API.
• GA4. Google says its Measurement Protocol "allows sending events directly to Google Analytics servers via HTTP requests" and is "intended to supplement, not replace" the site's normal tagging (Measurement Protocol docs).
• Meta. Meta describes its Conversions API as a connection from an advertiser's server, website platform, app or CRM to Meta systems (Meta's developer docs). It applies where the client runs Meta ads.

In every case the conversion is the booking, not the chat. Counting chats as conversions would teach an ad platform to find people who like to chat. If you run ServiceTitan, its own Google Ads conversion tracking is worth reading alongside this.

The questions report, and the rest of the record

The most useful screen in Clio may be the least glamorous. The questions report lists what visitors ask most, and separately the questions your site does not answer. Each unanswered question is a page waiting to be written: a service you offer but never describe, a town you cover but never name, a policy you explain on the phone every day. On an Athena site, the Prometheus agent can draft those pages for your approval.

1. 1

   Search the transcripts

   Every conversation is saved and searchable, so you can find every chat that mentioned a tankless heater or a competitor's name.

2. 2

   Export what you need

   Metrics and conversations export to CSV for your bookkeeper, your agency or your own spreadsheet.

3. 3

   Read the weekly summary

   A weekly summary email recaps the week's numbers for owners who will never log in to a dashboard.

4. 4

   Ask for a custom report later

   Custom reports are rolling out to the Pro plan and are not live yet. Until then, the CSV export covers most one-off questions.

We have built this kind of dashboard before: for HomeService WebApp we built dashboards on top of field-service data. If your reporting gap is bigger than the chat, our ServiceTitan dashboards guide covers job and revenue reporting, and the booking connections page shows where Clio's bookings come from. A free site audit is the simplest first step.