Smarter appointment load balancing: exclude calendars and split by calendar

Two new options give you finer control over how AI booking rules balance appointments across your team.
Exclude a calendar from load balancing
Not every calendar should influence who gets the next lead. Service calls, internal meetings, and follow-up visits can now be left out of the appointment counts your routing rules use.
Open any calendar's settings and check Exclude from load balancing
 (just below User Selection Strategy). That calendar's appointments immediately stop counting toward team members' rolling 30-day totals for every set of booking routing rules in your account,
 with no changes to your existing rules. The calendar stays fully bookable and selectable; only the load-balancing math changes.
Per-calendar appointment counts in routing rules
Rules can now look at appointment counts for specific calendars instead of just the whole account. This unlocks calendar-scoped balancing and percentage splits, for example:
"80% of the appointments in the the North Calendar should go to John; the rest can go to any other available user."
"70% of the appointments in Calendars A and B go to Jake, Sally, or Tom."
Just describe the rule in plain language when setting up AI Calendar Selection and the new User Appointment Counts by Calendar
 variable is used automatically. It's also available in the variable picker, the Distribution Quick Guide, and the saved-script tester, where you can generate sample per-calendar counts to see which branch a rule takes.
Good to know
Percentage rules are measured over the rolling 30-day window of appointments in the named calendar(s).
Excluding a calendar removes it from the global and by-ZIP counts, but per-calendar counts still include it, so a rule that explicitly references that calendar keeps working.
In Atlas, you can ask to "stop counting the Service calendar toward rep load" and it will update the calendar setting for you. Ava Code Mode understands the request too but will point you to the checkbox rather than writing a rule around it, since excluding a calendar is a calendar setting, not a routing rule. Ava can still build the percentage-split and calendar-scoped rules directly.