The operational decision
Preserve truthful request status when the provider does not confirm the booking. A calendar integration should be evaluated as a sequence of actual operations, not as a connected badge. Availability, booking, changes and failure handling each need their own expected result.
Prepare the workflow
Simulate an authorization or availability error and check the screen, spoken reply and staff record; none should claim success prematurely.
Example wording for approval
“The example booking was not confirmed. I can follow the approved request fallback, but I cannot say the appointment is reserved.”
Worked example
The fictional calendar lets the assistant read availability but denies permission to create an event. A visitor selects a slot, and the write fails. The assistant should say the appointment was not confirmed and use the approved request fallback. The staff record should preserve the failure category without exposing credentials. Check that no email, result card or calendar attachment claims a successful booking. Availability access and booking access are separate capabilities that must each be verified.
Handoff record
Record these task-specific fields: attempt identifier, provider error category, pending state, owner.
Acceptance check
Return a failed write after an apparent slot selection. The assistant should explain the unconfirmed state and avoid sending a fabricated calendar confirmation.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗