Capture the service address, no-cool or no-heat details, and requested timing while your technicians are working. Chleb configures the intake and team handoff around your service area and on-call rules. A request becomes a confirmed visit only after the approved scheduling workflow succeeds.
Chleb AI captures HVAC service requests, caller details and urgency after hours. Review calendar access, dispatch rules and handoffs before launch.
Illustrative fictional scenario: Homeowner calls at 10:42pm. AC out. 96 degrees outside.
I can take an urgent service request for the on-call team. What is the property address?
Illustrative fictional scenario: Homeowner calls at 10:42pm. AC out. 96 degrees outside.
During setup, we review:
Configured per trade
These field-service systems are compatibility candidates, not verified Chleb connectors. Confirm account permissions, service-area rules, calendar or dispatch writes, duplicate handling, failed delivery, and unanswered on-call handoff before promising a connection.
Use fictional caller details and a test account. Run these checks with your team before relying on the workflow. These are setup checks, not results from a customer deployment.
Pass evidence: Use fictional callers inside and outside the service area. For an eligible test booking, inspect the actual dispatch schedule for the correct address and time, then repeat the request and confirm only one record exists. A request with a time in its notes is not a scheduled visit.
If it fails: Do not book the out-of-area request; route it to a human review or callback and do not claim a dispatch slot.
Pass evidence: Run a fictional urgent after-hours call and a routine maintenance call. Inspect who receives the urgent alert and where the routine request lands. If booking is enabled, confirm the appointment in the calendar your team uses.
If it fails: If either rule or slot is unavailable, give the caller a message or human handoff instead of a made-up confirmation.
Pass evidence: In a test environment, make the on-call notification or downstream booking step fail after fictional caller details are given. The failure is visible to the designated team.
If it fails: Do not tell the caller the visit is confirmed; preserve the request for a callback or manual dispatch.
Chleb AI is based in Tampa, Florida, and configures this HVAC call flow for contractors in Tampa and across the United States. The published prices are $297 a month for the CRM, $899 a month for AI Receptionist + Chatbot, and $997 a month for the Front Office Bundle.
Six AI receptionists for HVAC, compared
The AI flags the call as urgent and can send a configured summary to your on-call contact, including any access notes the caller gives, so your team can dispatch the tech.
Yes. It asks a triage question first, then can submit a routine maintenance request for the next available slot or flags a no-cool or no-heat emergency as urgent for your team.
It collects the system's age, tonnage, and fuel type, then can request the estimator on your connected booking calendar during the same call.
Chleb AI is a flat monthly subscription: CRM at $297 a month, AI Receptionist + Chatbot at $899 a month, or the Front Office Bundle at $997 a month. Call minutes and emails are billed separately at carrier cost, not per call.
It can collect the caller’s reported installation date and reason for calling, then route the request to your office. Reading an installation record or confirming warranty eligibility requires a separately verified system connection.
Your team chooses whether the receptionist may state an approved fee or must leave that question for staff. Test the exact wording and the fallback when a fee is unknown; the sample request does not establish a price.
Use a trial call with your business wording to judge the voice and responses. Test a human handoff separately, including what happens when nobody answers and what caller details reach the recipient.
We configure the calendar with your real service area, real on-call schedule, and real availability windows. Test unavailable slots and conflicts on the actual calendar before allowing appointment confirmation. If a caller asks for something out-of-bounds, the AI takes the message and routes it to a human queue.
No. Chleb runs Go High Level under the hood, but the call summary and booking go to your team, and ServiceTitan, Housecall Pro, Jobber, and FieldEdge compatibility is assessed during setup; verify the account before promising a connection if that's where your office and techs already work.
We're US English first today. Bilingual handoff is on the roadmap. If Spanish is critical to your market, talk to us about timeline before signing.