Capability · Booking & scheduling
Make Booking Work Across Locations, Teams, and Services
Multiple locations, staff, services, territories and booking rules — calendars are where they all collide. Structure decides whether the right person shows up at the right place.
- 01
Visitor
- 02
Service
- 03
Location / territory
- 04
Eligible staff
- 05
Availability
- 06
Appointment
- 07
Confirmation + follow-up
Calendar model
Every calendar is defined by the same eight fields.
When each location's calendars are described the same way, adding a service, a staff member or a new location is a fill-in exercise.
- Location
- Austin North
- Service
- Consultation
- Calendar type
- Round robin
- Team
- 4 users
- Hours
- 8:00–18:00
- Buffer
- 15 min
- Routing
- Availability
- Status
- Active
One generic calendar
- — Wrong locations booked
- — Staff conflicts
- — Bad reporting
- — Unclear ownership
Structured calendar system
Bookings land on the right location, team and service — and report correctly.
What should be standardized?
Rules are global. Availability is local.
Rescheduling, cancellation, reminders and no-show handling follow one policy. Each location only controls who is available and when.
Standardize
Naming
Appointment statuses
Reminder logic
Cancellation rules
Reporting definitions
Configure locally
Staff
Working hours
Local holidays
Service availability
Booking routing depends on the same territory logic as GoHighLevel lead routing. New staff and new locations get calendars as part of location onboarding.
Questions
Calendar questions.
Coming from Calendly, Acuity or another CRM? Future appointments and booking links need their own cutover plan — see GoHighLevel calendar migration.
Next step
Design your booking structure.
Tell us how many locations, services and staff book appointments today, and where bookings go wrong.