The receptionist says the appointment is confirmed, but the office calendar is empty. Before changing the greeting or the model, trace which piece of evidence allowed that sentence to be spoken.
A calendar integration should supply confirmation as a verified outcome. The language model should not infer it from collecting a preferred time.
Find where the booking claim became stronger than the evidence
Use one redacted failing call and locate four moments: the caller agreed to a slot, the application submitted a write, the provider returned a result, and the receptionist made its confirmation.
Those events need the same operation reference. Without that connection, an engineer may compare a successful API request with a different failed call.
| Observed evidence | What it establishes |
|---|---|
| Caller selected a time | Preference, not saved availability |
| Tool invocation started | An attempt was made |
| Provider returned an event reference | A remote result exists to inspect |
| Required event fields verified | The saved record matches the agreed booking |
For a fictional repair visit, inspect date, time zone, location, duration, and service type. An event saved on the engineer's personal calendar is not a successful customer booking.
Inspect the response contract, not just the prompt
A response named success can conceal a queued request, draft event, or completed write. Return an explicit state and the supporting reference from the integration layer.
Allow confirmation only for the business-defined confirmed state. Pending work should produce truthful wording and an owned follow-up task. A generic instruction to “never hallucinate” cannot establish whether the provider saved the event.
Google's event-creation guide explains the provider operation. Your application must additionally establish which calendar and record correspond to the customer's intended workflow.
Reproduce the failure without real customers
Use a fictional account and test a rejected write, delayed response, wrong calendar, missing required field, and response lost after the event was created. Inspect both the spoken claim and actual record.
If the result is unknown, do not create another event automatically. The uncertain-timeout guide explains why the first write may already have committed.
Decide when staff should confirm instead
Some visits require approval or manual dispatch. Recording a request can be a valid outcome when the office owns the next step. It is a different service from direct booking, so keep its status and wording distinct.
The saved-record testing article provides an acceptance format for this boundary.
Missing-booking questions
Should we trust the transcript's confirmation?
Check the destination record and supporting operation evidence.
Is a generated event identifier enough?
Verify that it identifies an accepted remote record, not only a local placeholder.
What should we provide for debugging?
Bring one call reference, the expected event, and the actual calendar result to a booking review.