Service Calendar (v2) support natively in Voice AI Appointment Booking action
C
Christopher Hegyesi
The native "Appointment Booking" action in Voice AI Agent Goals reads only from the legacy Calendars list (Personal / Round-Robin / Class / Collective). Service Calendars — both v1 and the new top-level Services system — do not appear in the Calendar dropdown, so the Voice AI agent cannot book a Service Booking with the correct per-service duration.
The Conversation AI side of this is already shipping: there is a Lab feature "Service Calendar Support in Conversation AI" that is currently Live. Voice AI has no counterpart Lab toggle — confirmed by inspecting the Calendar dropdown in a sub-account and by searching Labs for "service" and "voice."
Asking for parity: a Voice AI Lab feature equivalent to the existing Conversation AI one — "Service Calendar Support in Voice AI Prompt-Based Bots" — that exposes the new Services system to the Appointment Booking action's Calendar picker, and inherits each booking's duration from the selected service rather than the calendar's default slot length.
Use case: A salon with 20 services ranging 60–180 min uses the GHL Services engine for the website booking widget. The Voice AI agent answers the phone, but is forced to use a Personal Calendar with a fixed 30-min slot length, so every Voice AI booking lands as a 30-min Calendar Appointment instead of a real Service Booking. The website widget and the phone agent end up writing to two different scheduling primitives. Without Service Calendar support in Voice AI, every salon/spa/service business client has to either (a) build a custom n8n bridge with five Custom Actions or (b) maintain 20 parallel Personal Calendars per service — both lossy compared to native parity.
Related ideas that should be considered together:
"Multiple Calendar Booking for Voice AI & Conversational AI" (marked Complete, but the Voice AI half isn't actually shipped — confirmed by Alexander Jais Dec 11 2025)
"Service Calendar v2 - CALENDAR IDs"
Paul Leong's Nov 12 comment on the multi-calendar idea: "need the ability to book appts of different durations based on call intent."
The platform-level signal: Service Calendar 2.0 was a documented migration that all Service businesses were nudged into. Voice AI was simultaneously released. The two products do not yet talk to each other for the booking primitive Service businesses actually use. This is the gap.
Log In
M
Mark Marquez
I need this, I’ve been told for months it’s coming.
C
Christopher Hegyesi
Mark Marquez I sent you a text and email !
C
Christopher Hegyesi
Just hit this today (May 1, 2026) in a live sub-account. The Calendar dropdown in the Voice AI Appointment Booking action shows exactly one selectable node the only Personal Calendar in the location. The new Services tab has 14 services with proper per-service durations (60–180 min), all assigned to a staff member, all bookable via the Services public API and the website widget. None of them are reachable from the Voice AI picker.
To bridge the gap I had to build five Voice AI Custom Actions (lookup, availability, book, reschedule, cancel) all dispatching to a single n8n webhook that calls services.leadconnectorhq.com/calendars/services/bookings with a Private Integration Token. It works, but it's roughly 3–4 hours of build per client and an n8n maintenance surface that wouldn't exist if the native action just supported Service Calendars.
The lowest-friction path here would be a Voice AI Lab toggle that mirrors the existing "Service Calendar Support in Conversation AI" toggle (currently Live in Labs). Same scope, same affordance, opt-in only no commitment to GA. Service businesses are already on Service Calendar 2.0 because GHL migrated them. They just can't use Voice AI with it yet.