This is a design choice, not something HighLevel requires. Plenty of accounts run well on one calendar. Split them when your rules for the AI differ from your rules for people: fewer days, fewer kinds of appointment, or exceptions only a person should agree to.
When one calendar stops being enough
One calendar works while the AI and your team follow the same rules. Trouble starts when they don't. Say the AI should only book standard consultations at set times, while a person handles rush requests, unusual cases and anything that needs judgment. On a single calendar, every open slot is open to both.
Our pattern for a consultation pipeline that needs this is two calendars. One is for AI self-booking, open only at the times you're happy for the bot to fill. The other is for manual and exception bookings, and it belongs to the person who handles escalations.
- Your team keeps moving or cancelling appointments the AI booked
- Some appointments should never be booked without a person agreeing to them
- The AI should offer fewer times than your team actually works
How the bot picks a calendar
Conversation AI can run on a single booking calendar, and a prompt-based bot can use several. With more than one, it reads each calendar's description and keywords to work out which fits what the person asked for.
Anything it can't match goes to the fallback calendar you set. That detail catches people out, and it has its own section below.
Descriptions help the bot choose, but they don't tell the customer anything. HighLevel's guidance is that whatever the bot should say about each service still belongs in its prompt.
Set up the split
Write the rule down before you build. One or two sentences: which appointments the AI may book, when, and what counts as an exception for a person.
- Create the AI calendar and set its availability to only the times the bot may fill. Use date-specific exceptions for holidays and days off.
- Create the manual calendar and make the escalation owner its team member.
- Open AI Agents → Conversation AI → Bot Goals and edit Appointment Booking.
- Under Calendar Selection, choose the AI calendar. If you use Multiple Calendars, tick only the calendars meant for AI booking.
- Set the fallback to an AI calendar, never the manual one.
- Give each AI calendar a clear description and keywords, and put the service explanations in the bot's prompt as well.
- In each calendar's notes, write what books there, what goes to the other calendar, and who owns it.
The fallback is an AI calendar too
When the bot can't match a request to a calendar, it books on the fallback. So whichever calendar you set as fallback is, in practice, an AI calendar. Put the manual calendar there and the bot books on it every time it's unsure, which is exactly the traffic you wanted a person to see.
Don't read the split as a permission setting either. What keeps the bot off the manual calendar is that it isn't in the bot's calendar list and isn't the fallback. Check both whenever anyone edits the bot goal.
Whatever you pick as the fallback, the AI can book. Keep the manual calendar out of it.
Rather have it set up for you?
We'll build the AI calendar, the manual calendar and the bot goal so exceptions always reach a person. First step: a 30-minute 1:1 with Rob.
Keeping the two calendars straight
Later on, nobody remembers why there are two consultation calendars. That's why we write the routing into the notes of both, in plain words. The manual one names its owner. The AI one says which bot goal books it.
If your team assigns leads to people, a Round Robin calendar can tell the AI to book with the contact's assigned user. That keeps continuity on the AI side without merging the two calendars. After any change to the bot or the calendars, run through this:
- The bot goal lists only AI calendars
- The fallback is an AI calendar
- The manual calendar still belongs to the person who handles exceptions
- A test chat with an unusual request books on the fallback, not the manual calendar