GoHighLevel calendar setup starts with choosing the calendar type that matches how you take bookings: Service, Round Robin (spreads appointments across team members by availability or equally), Class Booking (one host, many attendees, limited by seats) or Collective Booking (booking with several people at once). Then you set availability, buffers, the team members, the booking form and the notifications, and connect Google Calendar if your team uses it. The settings that cause most problems are time zones, buffers and double booking against an external calendar. HighLevel's help articles were read October 18, 2026; one calendar type (Collective) had little dedicated documentation in our search, so test it before promising it.
Which GoHighLevel calendar type should you use?
Use a Service calendar for one provider, a Round Robin calendar to share bookings across a team, and a Class Booking calendar when one host has many attendees.
| Type | What it does | Use it for |
|---|---|---|
| Service calendar | One service or provider with its own availability | A single consultant, a treatment room, a standard appointment |
| Round Robin | Distributes bookings among assigned team members, by availability or equal distribution (no priority for particular staff) | A sales or intake team where any rep can take the call |
| Class Booking | One host, many attendees; seat limits drive availability; each booking removes one seat | Classes, workshops, group sessions |
| Collective Booking | Books people together for one slot | Appointments that need two people present |
Sources: HighLevel's calendar types overview, round robin setup guide and class booking guide.
| Service | Round Robin | Class Booking | Collective | |
|---|---|---|---|---|
| Several team members share bookings | ✕ | ✓ | ✕ | ◐ |
| Seat limits for groups | ✕ | ✕ | ✓ | ✕ |
| Distribution by availability or equally | – | ✓ | – | – |
| Needs the Neo widget for staff or seat display | ✕ | ✓ | ✓ | ✕ |
Source: HighLevel calendar help articles, read October 18, 2026. Collective Booking had little documentation; test it
How to set up a calendar in GoHighLevel: the settings that matter
- Pick the type from the table above, and name it for the appointment (for example "Initial consultation, 30 minutes").
- Add team members and, for round robin, choose availability-based or equal distribution.
- Set availability. Weekly hours, date overrides and holidays. For classes, set the recurring schedule and the seat limit.
- Set the duration and buffers. Pre- and post-buffer time pads each appointment so back-to-back bookings do not collide.
- Choose the widget style. Round Robin staff selection and Class Booking seat display need the Neo widget style, per HighLevel.
- Build the booking form with only the fields you need. Every extra field loses bookings.
- Set notifications and the reminder workflow; see appointment reminders.
- Connect Google Calendar if staff use it, and test two-way sync. See calendar not syncing.
- Test. Book as a stranger from a phone, in a different time zone, and cancel and reschedule.
Common GoHighLevel calendar problems and fixes
| Problem | Cause | Fix |
|---|---|---|
| Double bookings | External calendar not connected or sync off | Connect and test two-way sync; add a conflict calendar |
| Wrong times shown to customers | Calendar and user time zones differ | Set the calendar time zone and check each user's |
| Back-to-back crunch | No buffer | Add pre- and post-buffer time |
| Round robin gives one rep everything | Availability-based distribution with uneven schedules | Use equal distribution or align availability |
| Staff selection missing in the widget | Widget style is not Neo | Switch the calendar widget style |
| Leads book but nothing follows | No workflow on booking | Start the reminder workflow from Customer Booked Appointment |
Frequently asked questions about GoHighLevel calendar setup
What calendar types does GoHighLevel have?
Service, Round Robin, Class Booking and Collective Booking, per HighLevel's help center.
How does a round robin calendar choose who gets the booking?
A round robin calendar in GoHighLevel chooses who gets the booking by availability or by equal distribution. HighLevel says it does not support priority for particular staff.
How do I stop double bookings?
Connect the external calendar, test two-way sync, and add buffers. Treat a missed sync as a fault to fix, not a rare event.
Can I limit how many people book a class?
Yes, a Class Booking calendar uses seat limits; each confirmed booking reduces the seats by one.
What is a buffer in a GoHighLevel calendar?
Padding before and after an appointment so adjacent bookings do not overlap.
Why does the calendar show the wrong time?
A time-zone mismatch between the calendar, the user and the visitor. Set each explicitly and test from another zone.
Can you set up my calendars and booking flow?
Yes, as part of our CRM implementation; the audit is free.