Skip to content
Save 20% on every snapshot, funnel and workflowBrowse the catalogue
Features

GoHighLevel Calendars: Setup, Types and the Settings That Break Bookings

Calendar types, availability rules, buffers, round robin and reminder cadences in GoHighLevel, plus the settings that quietly cause double bookings and no-shows.

Callum RhodesUpdated6 min read
GoHighLevel calendar setup

Key takeaways

  • Set the sub-account time zone before creating any calendar.
  • Connect team calendars with two-way sync or you will get double bookings.
  • Buffers matter more than slot length for businesses that travel between jobs.
  • Three reminders at 72 hours, 24 hours and 2 hours is the reliable cadence.
  • Deposits on high-value appointments cut no-shows more than any reminder.
Contents
  1. The calendar types
  2. Availability that reflects reality
  3. The settings that break bookings
  4. Reminder cadence that cuts no-shows
  5. Taking deposits

Calendars are where most GoHighLevel builds quietly fail. Not dramatically, but through double bookings, slots that do not exist, reminders in the wrong time zone and no-shows nobody tracked. All of it comes from a handful of settings.

The calendar types

TypeUse it for
SimpleOne person taking bookings. Most common.
Round robinDistributing across a team by availability or rotation.
CollectiveMeetings needing several people free at once.
Class bookingGroup sessions with a capacity, such as fitness classes.
ServiceBookable services with durations and, optionally, resources.

Most service businesses need simple or round robin. Reach for the others only when the thing you are booking genuinely has that shape, because the extra configuration surface is a cost.

Availability that reflects reality

A calendar that offers slots the business cannot honour is worse than no online booking, because someone turns up and nobody is there.

  1. Set the sub-account time zone first. Before creating any calendar. Changing it afterwards recalculates availability and can shift existing bookings in confusing ways.
  2. Set real working hours, per day. Not a generic nine to five if Friday finishes at two.
  3. Connect the team's actual calendars with two-way sync, so personal appointments and existing meetings block availability. One-way sync is the cause of most double bookings.
  4. Set a buffer. For anything involving travel this matters more than slot length. Fifteen minutes after each appointment prevents a booking system that assumes teleportation.
  5. Set minimum scheduling notice. Two hours stops someone booking a slot ten minutes from now that nobody will see.
  6. Set a booking window. Thirty days out is usually right. Ninety days invites bookings people forget about entirely.
  7. Cap daily bookings where capacity is genuinely limited, so a good ad day does not produce a schedule nobody can deliver.

The settings that break bookings

SymptomUsual cause
No availability at allWorking hours unset, or minimum notice longer than the visible window
Double bookingsExternal calendar connected one-way, or not connected
Slots at impossible timesSub-account time zone wrong
Reminders at 3amSame, or send windows not configured on the workflow
Back-to-back jobs across townNo buffer configured
Bookings for tomorrow at 6amWorking hours copied from the default template
Round robin always picks one personDistribution set to priority rather than optimised availability

Test by booking a real appointment yourself, on a phone, from a private browser window. Check the confirmation, the calendar entry and every reminder. Almost every calendar problem is visible in that five-minute test and invisible in the settings screen.

Reminder cadence that cuts no-shows

Three touches is the reliable pattern for most businesses:

  • 72 hours before: the details. Date, time, address, what to prepare, what it costs if relevant.
  • 24 hours before: ask for confirmation with a one-word reply. This is the important one, because it converts a passive reminder into an active commitment and surfaces cancellations while the slot can still be refilled.
  • 2 hours before: a short final nudge, or an on-the-way message if someone is travelling to them.

Two refinements worth adding. Route unconfirmed bookings to a task after the 24-hour touch, so a human calls the ones who did not reply. And handle cancellations by releasing the slot and notifying a waitlist, which turns a lost hour into a filled one.

Respect quiet hours on every reminder workflow. A 2am text does more damage than the no-show it was trying to prevent.

Taking deposits

For high-value appointments, requiring payment at booking is the single most effective no-show reduction available, and it is more effective than any number of reminders.

Connect Stripe at sub-account level and enable payment on the calendar. A deposit changes the psychology: a free booking is easy to skip, a paid one is a decision someone has already made.

Apply it selectively. A salon colour appointment or a legal consultation justifies a deposit. A free estimate visit generally does not, and asking for one will cost you more leads than it saves in no-shows.

Calendars configured for the trade

Our snapshots ship with calendars already set up for how that industry books: arrival windows for trades, service durations for salons, and the reminder cadence to match.

Browse snapshots

Frequently asked questions

What calendar types does GoHighLevel have?

Simple calendars for one person, round robin for distributing bookings across a team, collective for meetings requiring several attendees, class booking for group sessions with capacity, and service calendars for bookable services. Most service businesses need simple or round robin.

Why is my GoHighLevel calendar showing no availability?

In order of likelihood: working hours not set, the connected Google or Outlook calendar is full of existing events, minimum scheduling notice is longer than the window you are looking at, or the sub-account time zone is wrong so availability is being calculated for a different part of the day.

How do I stop double bookings?

Connect the team's Google or Outlook calendars with two-way sync so external events block availability, then set a buffer after each appointment. Double bookings almost always trace to a calendar that was connected one-way or not at all.

Can I take payment when someone books?

Yes. Connect Stripe at sub-account level and enable payment on the calendar. This is the single most effective way to reduce no-shows on high-value appointments, because a deposit changes the decision to skip.

How many reminders should I send?

Three works well for most businesses: 72 hours before with the details, 24 hours before asking for confirmation, and two hours before as a final nudge. More than that becomes irritating and people start ignoring all of them.

Sources

  1. HighLevel help centre: calendars

Skip the build. Import a working GoHighLevel account instead.

Industry-ready snapshots with funnels, pipelines, calendars and automations already wired. Delivered within 24 hours, installable on every sub-account you manage.

Mentioned in this article

Keep reading

All articles
Features

AI Agents for Loan Officers in GHL

Loan officers handle multiple client inquiries daily, but responding to every call, qualifying leads, and scheduling appointments can be time-consuming.

March 6, 20255 min read