It does not book it. Jobs you want a person to schedule, such as insurance claim help or a large estimate, are marked that way when the call flow is set up. When a caller asks for one, the receptionist says so, keeps the caller's details and passes the request to your team. In the sample call below, a roof inspection is booked and the insurance claim the caller asks about next goes to a person.
Not every job should go straight onto the calendar. An insurance claim, a large replacement quote or a visit that needs a particular person often needs someone to talk it through first. When a call flow is set up, each service is marked either as one the receptionist may book or as one a person schedules.
The sample business lists four services. The receptionist may book a roof inspection, a roof leak repair or a replacement estimate, and insurance claim help is marked for a person. The job list beside the demo shows those settings.
In the sample call, the caller books a roof inspection for 2 PM the same day, then asks the receptionist to get his insurance claim started. The receptionist does not book it and does not attempt the claim. It says insurance claim help is something the team schedules personally, and that his message has gone to the team with his number.
The team receives the request in his own words, with the name, number and address the receptionist already collected for the inspection. The inspection stays on the calendar. Because the booking came first, the receptionist had his number before it passed the claim on.
Where the line sits depends on the business. Common choices are jobs that need a quote in person, jobs that involve an insurer or a contract, and anything outside the services you list. Chleb's FAQ describes calls outside the configured playbook being routed to your team with the full transcript, and Chleb's HVAC page describes out-of-bounds requests being taken as a message and routed to a human queue.
Some businesses are better off without an AI receptionist at all. Chleb's own FAQ names three: complex multi-step legal-style intake, markets that need bilingual coverage it does not yet serve, and call volume under roughly 30 calls a week.
It shows the rule at work: a bookable job is booked, a job marked for a person is not, and the request reaches the team with the caller's details. Brindlecroft Roofing and the caller are fictional.
It does not show a real message being delivered, how quickly your team calls back, or the production receptionist, which uses a language model following the rules in your call flow. The voices in the video come from Kokoro text-to-speech, not the production voice.
When a caller names a job marked for a person before giving a name or number, the simulation now asks for a name and a callback number first: it says the job is something the team schedules personally, collects both, and only then passes the request on, so the handoff never claims a number it does not have. The sample call still books the inspection first, so you can watch a bookable job go on the calendar and a job marked for a person get handed off in the same call. Test the person-scheduled jobs on a test call before launch, including one where the caller opens with that job, and check that the live receptionist takes a name and number before it promises a call back.
To hear the live receptionist, call (813) 694-8671.
Simulated call, voiced by text-to-speech. The live receptionist is at (813) 694-8671.
Narrator: Simulated call, voiced by text-to-speech. The live receptionist is at (813) 694-8671.
Receptionist: Thanks for calling Brindlecroft Roofing, this is the virtual receptionist. How can I help you today?
Caller: Roof inspection, please.
Receptionist: I can help with roof inspection. What's your name, please?
Caller: Luis Ortega.
Receptionist: What's the best number to reach you?
Caller: 813 555 0176.
Receptionist: Thanks, I have 8 1 3, 5 5 5, 0 1 7 6.
Receptionist: What's the address for the visit?
Caller: 5610 Cypress Bend Court.
Receptionist: The earliest I can offer is today at 2 PM or today at 4 PM. Which works better?
Caller: The first one.
Receptionist: Let me read that back: Luis Ortega, at 8 1 3, 5 5 5, 0 1 7 6, for roof inspection, at 5610 Cypress Bend Court, today at 2 PM. Is that all correct?
Caller: Yes.
Receptionist: You're booked for today at 2 PM. The team will see it on their calendar right away. Is there anything else I can help with?
Caller: Can you also get my insurance claim started?
Receptionist: Insurance claim help is something the team schedules personally. I've passed your message to the team with your number, and someone will call you back today. Is there anything else?
Caller: No, that's all.
Receptionist: Thanks for calling Brindlecroft Roofing. Have a good day!
You do, when the call flow is set up. Each service is marked as bookable or as one a person schedules, and Chleb's founders build and test the call flow from your services before your number goes live.
A plain statement that the team schedules that job personally, and that the request has gone to the team. In the sample call the receptionist already has the caller's name and number from the inspection it booked, so they go with the request, and he is told someone will call back today. In the simulation, a caller who asks for that job before giving any details is now asked for a name and a callback number first, so the handoff always carries them.
Yes. In the sample call, the inspection is booked before the claim request, and it stays on the calendar after the claim goes to a person.