An open slot is not always an appointment, and an unavailable calendar is not an invitation to guess. The receptionist needs a useful answer even when it cannot safely confirm a time.
Decide what a confirmed booking means
Define the selected calendar, appointment type, time zone, service duration, travel or preparation buffer, and any required approval. Google Calendar's free/busy interface reports occupied intervals; it does not by itself decide whether a service visit is valid.
Use a different phrase for a request
If live availability cannot be retrieved or the requested time violates an agreed rule, ask for preferred windows and a callback number. Tell the caller that the team will review the request; do not say “you're booked” or place an invented hold.
Keep escalation available when timing matters
For a time-sensitive request, apply the customer's approved transfer rule where appropriate. If the human destination cannot be reached, use the agreed voicemail or safe fallback and leave a workspace record with the caller's preferred dates and time zone.
Test failure modes before enabling booking
With the customer, test calendar access revoked, overlapping events, closed hours, ambiguous time zones, and a caller who changes their mind. Verify the caller-facing words and whether the workspace distinguishes a request from a confirmed event. No one should discover the fallback during a real customer call.
Expand only after the path works
AfterTone configures Nova's Google Calendar availability and scheduling only when the customer selects it, connects the calendar, approves the rules, and completes testing. A narrower capture-and-callback flow may be the right first release while calendar access or service constraints are being sorted out.