Appointment could not be booked

Appointment could not be booked

When an appointment could not be booked even though the conversation intended it, the cause is usually the booking configuration or the availability of suitable time slots. This article helps you narrow down the cause.

Check the booking status first

Look at the booking status of the affected conversation. The possible statuses and what they mean are described in understanding booking status. A conversation can, for example, have the status offered, requested, booked or failed.

Common causes

• No available time slots: No suitable slots were available within the booking window.
• Incomplete booking settings: The appointment type, duration or booking window is not fully configured.
• Required fields not met: Required result fields were not captured when they serve as a prerequisite for a booking.
• Callback instead of appointment: Some campaigns provide for a callback instead of a directly booked appointment.

A detailed description is available in failed bookings.

What you can check

1. Check whether the campaign's booking settings are complete.
2. Check whether available time slots exist within the booking window.
3. Check whether required result fields were captured as a prerequisite.
4. Check whether a callback is provided for the campaign instead of an appointment.

Hinweis: Whether and how an appointment is offered depends on the booking configuration. Nexcal does not promise an appointment without the corresponding configuration.

If the booking still fails

If the booking remains unsuccessful despite a complete configuration, contact support. Include the workspace, the campaign, the affected conversation and the visible booking status.

Related topics

• Failed bookings
• Understanding booking status
• Callbacks instead of appointments