> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Diagnose an appointment that did not book

> Compare the assistant assignment, tool result, and destination calendar before retrying.

Start with one failed test and keep its contact, requested time, timezone, and conversation or call ID. This makes it possible to distinguish a missing tool from a provider rejection or an unresolved booking.

## Check the saved assignment

Open the assistant's **Calendars** picker and let it load. Confirm the selected calendar belongs to the intended account. An assistant has one active calendar; selecting a different one replaces it. Clicking the selected calendar removes it.

If a GHL calendar is missing, run the account's [connection check](/v3/guides/troubleshooting/ghl-connection). If the calendar exists but the picker cannot load the assignment, resolve that error before changing it.

## Compare each booking step

| What happened | What to check next |
| - | - |
| The assistant offered times without checking availability | Attach `get_availability`; ask the prompt to offer only returned slots |
| Times were returned, but no booking action ran | Attach `book_appointment`; make the booking condition explicit in the prompt |
| The tool cannot identify the contact | Have the assistant collect the required identity and use `update_user_details` before retrying |
| The tool says the slot is unavailable | Check the same date and timezone, then request fresh availability |
| The tool reports an unconfirmed booking | Inspect existing appointments before retrying or choosing another time |
| An appointment exists, but no message arrived | Investigate confirmation delivery separately from appointment creation |

The booking operation checks current availability before creating a GHL appointment. An availability result from an earlier moment does not reserve that slot.

## Prove the correction

Use a new controlled test. In the destination calendar, verify the contact, selected calendar, appointment date, timezone, and that only one event exists. If the assistant says a booking succeeded but no event is present, keep the tool response and call/conversation ID for support; do not repeatedly submit the same booking.

See [calendar setup](/v3/guides/workflows/book-appointments) and [platform tools](/v3/platform-tools).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.