Practical operating guide
Why your calendar shows availability that customers cannot book
By ByTomorrow · Published
Your calendar has an empty space, but a customer says the booking page has no appointments. Both screens can be showing exactly what they were configured to show.
The office view may show unused time while the booking page applies staff, resource and scheduling rules. The missing slot matters more than whether either screen looks empty.
Diagnosis
An empty calendar is not a bookable slot
Different views answer different questions
The staff view shows scheduled events. A customer needs a slot that satisfies the booking rules for the specific service, assigned person and date. Write down the exact booking link before changing settings.
The diagnostic view has limits
HighLevel documents calendar-specific diagnostics, including conflict and notice codes. Its troubleshooting view uses the logged-in user's time zone and does not diagnose workflow logic. Keep those limits beside your test notes.
Working worksheet
A diagnostic map for the missing slot
Record the failure
Copy this row: booking link ___; service ___; requested local date and time ___; customer time zone ___; staff time zone ___; customer sees ___; staff sees ___. Use a test identity and keep personal details out of shared screenshots.
No slots appear for the day
Check whether the intended calendar has an assigned person with working hours on that date. Record the current assignment and hours before editing. If the service needs a resource, check that resource separately.
A particular slot is unavailable
In HighLevel, inspect the unavailable slot in the calendar troubleshooting tool. CONFLICT points to an external calendar event; NOTICE points to scheduling lead time; BUFFER or DURATION points to how the appointment fits. Record the code and the specific setting it identifies.
The time exists but the customer cannot finish
If selection works and submission fails, capture the visible error and test the form separately. Do not remove availability rules to fix a submission problem. The appointment creation step and its permissions may need investigation.
Worked example
Illustrative case: a staff member sees an open afternoon, while the customer is trying to book inside the configured notice period. The worksheet records NOTICE. The owner then decides whether that notice period is intentional. Changing staff hours would not answer that question.
Use the worksheet
Put it into practice
Reproduce the customer view
Open the exact public booking link in a fresh browser session. Select the same service, date and time zone. Record whether the failure occurs before or after selecting a slot.
Inspect one blocking rule
Match the missing slot to the diagnostic reason or a specific configuration check. Change only the setting the owner intends to change, and retain its prior value.
Retest both sides
Check an allowed appointment and an appointment that should remain unavailable. Remove any test booking afterward. Record the result so an apparent fix does not silently weaken a needed restriction.
Questions
Straight answers.
Only if the business deliberately stops treating that calendar as a conflict source. First identify which event blocks the slot. Removing conflict checks to expose one opening can make genuinely occupied time bookable.
No. Availability diagnostics and post-booking messages are separate checks. Verify the actual appointment record before investigating any confirmation workflow.
Sources and further reading
- HighLevel calendar troubleshooting
Supports calendar diagnostic codes, staff availability checks, the logged-in user time-zone limitation and exclusion of workflow errors.
Checked .
Bring one reproducible booking failure
A booking link, the requested time and the observed error give a workflow discussion a concrete starting point.
Discuss your workflow