Popular: Create Your First Booking Link Set Your Availability
About This Resource

A Booking Link Is Not Working

Use this checklist when a public booking link does not open, shows an error, or cannot complete a booking. First identify whether the failure is the URL, link state, configuration, plan access, or the booking form itself.

Check the link and URL

  1. Copy the URL again from the link’s Share page.
  2. Open it in a private browser window.
  3. Confirm the link is active and not a draft.
  4. Check whether the link is private or otherwise restricted.
  5. Compare the URL slug with the one being shared.

If the page is not found, the URL may be incomplete, the slug may have changed, or the link may not be published.

Check booking-link configuration

Open the link’s settings and confirm it has:

  • A valid title and duration.
  • A location such as Google Meet, phone, or in-person.
  • An assigned schedule with weekly hours or date overrides.
  • Required booking questions that can be completed.
  • Valid redirect settings when Redirect on Booking is enabled.

If the page opens but shows no times, use No Available Times Are Showing.

Check plan-controlled features

Some capabilities require Pro, including advanced booking controls, private links, redirects, paid bookings, custom questions, and other gated workflows. If an action shows an upgrade prompt, the link may still work with the feature disabled; it cannot save or publish the gated configuration until the plan requirement is met.

For paid bookings, confirm the required payment provider is connected and configured.

Test the exact failure

Test the link in a private window and, if possible, another browser or device. Record the step where it stops: opening the page, selecting a time, submitting details, redirecting, or receiving confirmation.

Gather the public URL, exact error message, browser, date and time, displayed time zone, and affected step. Remove personal information from screenshots.

Do not send passwords, payment details, session cookies, API keys, or integration tokens to support.

Did this answer your question?