A connected calendar can be technically online and still be operationally unready. Before an AI receptionist offers an appointment, the business must define which calendar, slots, callers, and failure paths are allowed.
Choose the source of truth
Identify the exact Google Calendar controlling availability and who may change it. Document how holds, travel, time off, and existing jobs affect bookable time. Google's API separates reading free-busy information from creating events, so test both permissions.
Define each appointment type
Set duration, lead time, buffers, service area, eligible hours, and required caller information. An open hour is not automatically right for every job.
Make time zones and dates explicit
Confirm the business time zone, caller-facing language, daylight-saving behavior, and how events appear on staff devices. Test month boundaries, holidays, and daylight-saving changes.
Verify the created event
Check the correct calendar, title, contact details, service context, location, duration, and internal notes. Confirm real notifications and do not promise messages outside the approved system.
Design the failure path
If availability cannot be read or an event cannot be created, Nova should not guess. Use an approved callback record, transfer, or voicemail fallback. AfterTone uses live scheduling only after customer-specific selection, configuration, and testing.