What a confirmed booking requires
The integration must read eligible availability, apply job duration and technician or territory rules, write the appointment once, and return a reliable confirmation. It also needs correct time-zone handling, permissions, duplicate protection, retries, and an outage path.
When to use an appointment request
If the scheduling platform lacks reliable availability or write-back access, collect the caller’s preferred windows and send a structured request to staff. Tell the caller clearly that the office will confirm. This is less automated but more accurate than pretending a slot is reserved.
Tests to complete before direct booking
- Two callers request the final available slot.
- The calendar changes between availability check and write.
- A retry occurs after an uncertain response.
- Daylight-saving or time-zone boundaries affect the requested time.
- The integration loses permission or the provider is unavailable.
- The job type requires a different duration, technician, or territory.
- A cancellation or reschedule must reach both systems.
Language matters
Use “You’re booked” only after confirmation. Use “I’ve recorded your preferred time” or “The office will confirm” for a request. The summary sent to staff should label the status just as clearly.
Straight answers
Frequently asked questions
Can every HVAC calendar support direct AI booking?
No. Access and capabilities vary by product, account, configuration, and API.
Is an appointment request still useful?
Yes. It can capture a qualified lead and all scheduling details without creating a false confirmation.
What prevents double booking?
Atomic or idempotent writes, confirmation identifiers, conflict checks, and tested retry behavior in the actual production integration.
Who controls appointment rules?
The HVAC company approves job types, durations, availability, service territory, technician constraints, and exceptions.