Why your booking page shows no available times, and how to fix it

When your booking page shows no available times, one of its rules is almost always blocking the dates you're looking at. Usually the meeting type is switched off, the hours or time zone are wrong, or a calendar shows you busy. Buffers, notice and date overrides can also leave no room. Work through the checklist below to find the one rule causing it.

Don't start by turning off conflict checks. Times will appear, but people can then book you when you're actually busy.

Quick checklist for a booking page with no times

• Open the right public link and check the meeting type is turned on and bookable.
• Check the date you're viewing, the time zone shown, how far ahead people can book, and the minimum notice.
• Review your weekly hours and any date override that closes or shortens a day.
• Make sure the right host accounts are connected and their calendars can be checked.
• Compare the free gaps with the full meeting length plus buffers.
• Check daily booking limits and whether every required host is free.

First, work out whether there are truly no valid slots or the page simply failed to load. An empty-looking calendar can mean either. Note what the visitor actually sees before you change any settings.

Write down what you see before you fix anything

Note the booking link, the date you expected to offer, the time zone shown and the exact message. Note the time you checked too, because minimum notice depends on the current time. If the page is also embedded on your website, test both the direct link and the embed.

If the direct link works but the embed is blank, the problem is likely on your website, so leave your calendar rules alone for now. If both show no times, start with the meeting type's settings.

Test as an ordinary visitor, not only in your admin preview. Being able to open the editor doesn't prove a customer can book. Ask a colleague to try the link without using your account.

Check the meeting type, dates and time zone

Make sure the link points to the right active meeting type, rather than an archived one, an old template or another host's page. Check whether an end date or limited booking window has passed. Don't create a second booking page as your first fix, because the old link will keep circulating with the same problem.

Then look at the visitor's time zone. Your Monday evening may be their Tuesday morning, so the slot you expected can show up on the next day. Google's time zone help explains how calendars show events in each person's local time. Our guide on how to schedule meetings across time zones covers the common mix-ups.^[1]

Next, check minimum notice against the current time. For example, with 2 hours' notice, a visitor checking at 13:20 can't book a 15:00 start. The earliest allowed moment is 15:20, and with slots every 30 minutes the first one shown would be 15:30.

Check your working hours and date overrides

Look at the hours this meeting type actually uses, rather than your account's default working hours. It might follow a shared schedule, its own hours or a team setup. A change to your default may not reach meeting types that already exist, so check the meeting type itself.

A date override can close a day that normally has hours, on purpose. A partial-day override might leave only a short opening. Before you remove one, find out who added it and why, because reopening a colleague's leave day by accident fixes nothing. This guide to holiday availability and date overrides explains how they work.

Caletus has date overrides, minimum notice, buffers and daily booking limits. Use the labels and values in your own account to work out which rule is closing the day.^[2]

Look for calendar availability problems

Check the connected account and each calendar that's checked for conflicts. A shared calendar selected by mistake can fill your page with other people's meetings. A connection that has lost access needs reconnecting, so don't just remove it from conflict checks.

Google reports calendar errors separately from busy times. A calendar that failed to load is a different thing from one that loaded and showed no conflicts. An unknown calendar state shouldn't be treated as free.^[3]

Look for all-day events, duplicate test bookings and recurring events. Check each event's busy status before you edit it. In Google Calendar, an event marked available doesn't block time, and that's separate from whether the event is private or public.^[4]

If a calendar was disconnected, reconnect it and repeat your original test. Reconnecting may not catch up on missed updates or remove duplicates, so check any bookings made while it was down.

Check that the whole meeting fits

A 45-minute interview can't fit in a 30-minute gap, even if the gap looks roomy in a compact calendar view. Use the real start and end times. Then add buffers, start-time intervals and any rule that buffers must fit inside working hours.

For example, 12:00–12:30 is too short for a 45-minute call before you even add prep time. A 12:00–13:00 window fits the call, but 10-minute buffers on each side might not, depending on how your tool handles the edges. Test that boundary instead of guessing, and see the guide to meeting buffer time for sensible settings.

Daily limits are a separate check. A host can have an empty afternoon and still be full because they've hit their booking cap for the day. Raising the cap is a business decision, so get approval before you change it.

Check every host the meeting needs

A collective meeting needs a time when all required hosts are free. A round robin meeting only needs one eligible host from the pool. Caletus's team features cover both collective scheduling and round robin pools, so confirm which one your meeting type uses.^[5]

For a panel interview, check each interviewer's schedule. One person's leave or short day can explain the missing slot. Removing them to open up times changes the meeting, so agree on it with the recruiting team first.

For a round robin pool, check who's in it, who's eligible, who's free and who has room left. Five names in the pool doesn't mean any of them can take that slot. Read what happens when a round robin host is unavailable before you count on a fallback.

Booking page troubleshooting by symptom

These are likely causes, not certain ones. Note the original value before you change anything. Change one setting, repeat the same test, and put back anything that didn't help. That way you learn the real cause instead of piling up changes that happened to make the page look fuller.

How to test your Caletus booking page step by step

1. 1Pick a test meeting type. Note its host, time zone, length, hours, notice, buffers and the calendars it checks.
2. 2Find a future time that meets all those rules, with every required host connected and free.
3. 3Open the public link as a test invitee and check you can pick that date and local time.
4. 4Add a temporary busy event to one checked calendar. Confirm the overlapping slot disappears.
5. 5Delete that event, check the slot comes back, then book it.
6. 6Check the booking record, the calendar event, the confirmation email, and that the slot is no longer offered.
7. 7Cancel the test booking and check the records and emails before you send real traffic to the page.

Don't make a real host wide open just for this test. Use a test meeting type with realistic rules and a known free time. If you can't find any free time that fits, the page may be telling the truth: the team is fully booked.

When to contact support

Contact support when the page contradicts a test you can repeat or a calendar connection keeps failing. Do the same if a booking goes through despite a proven conflict. Include the meeting type, your test's time and time zone, what you expected, what you saw, the calendar provider, and screenshots with private details hidden.

Never send passwords, access tokens or unrelated calendar details. Mention recent changes and whether the direct link and the embed behave differently. One clear example with a single meeting type is easier to investigate than a screenshot of your whole calendar.

Afterward, undo any temporary changes you made while troubleshooting. Write down the real cause, whether it was a holiday override, a permissions problem or a product bug, so the next admin doesn't start from scratch. You're aiming for correct availability, even if that means fewer open slots.

• booking page troubleshooting
• no available appointment slots
• calendar availability problems
• scheduling configuration checklist