Blog / Scheduling and estimates
AI appointment scheduling: rules that prevent avoidable booking mistakes
Reliable AI appointment scheduling needs a server-enforced calendar, owner-approved service and pricing rules, and explicit exception handling. The conversation may propose a time; only the scheduling system can confirm it.
Define the smallest useful rule set first
Begin with services offered, areas covered, local business hours, normal job duration, travel buffer, and who is eligible to perform each job. Add holiday closures and minimum booking notice where they apply. A short complete rule set for common jobs is more useful than a long form filled with guesses.
Check timezone explicitly. A caller saying “tomorrow at nine” needs a calendar date and a named local timezone. Store a timezone-aware appointment and read the local date and time back to the caller. Test daylight-saving transitions rather than assuming every local time exists once.
Keep a quote separate from an estimate
For a fixed price, define the included work and exclusions. For a range, explain what changes the final price. For inspection-required jobs, collect the details and request review rather than making up a range. The caller should hear any approved diagnostic, travel, emergency, or after-hours fee before agreeing to the next step.
An illustrative policy might say that a standard job has a fixed approved price, while hidden damage requires a new estimate. Those are examples of rule types, not Zephaux customer prices. Read phone quotes and arrival windows for more detail.
Treat urgent requests as an explicit branch
Urgency does not automatically authorize double booking, a higher price, or dispatch outside the service area. Specify what the assistant can offer, which person can approve an exception, how long to wait, and what to say if nobody responds. An exception should have an identifiable approving owner and a recorded reason.
If no technician has accepted, say that availability is unconfirmed. Do not turn “I have asked the owner” into “someone is on the way.” Immediate threats to safety require emergency services, not a promise from an automated receptionist.
Protect the actual booking transaction
Availability may change while a conversation is in progress. Recheck capacity when committing the booking. Two callers asking for the last slot should not both receive confirmed appointments. A repeated request after a network timeout should use a stable request identifier so the system can return the original result.
Test occupied slots, overlapping durations, required buffers, closed hours, staff eligibility, cancellations, and rescheduling. If rescheduling fails, the original appointment should remain clear to both customer and owner. Explain exactly which booking is confirmed instead of silently replacing it.
Review the same facts the customer heard
After a consented call, the owner should be able to compare the transcript with the calendar outcome and approved rule version. Record whether a price was fixed, estimated, or awaiting inspection. Flag uncertainty rather than hiding it in a summary.
Zephaux has internal scheduling tools and controlled booking implementation, but live phone-to-booking integration is not currently available. See the current scheduling safeguards and status. A successful simulator scenario is not a live booking test.