Allow Voice AI to Book Appointments as Unconfirmed Instead of Forcing Confirmed Status
C
Customer Service
Body:
Currently, Go High Level’s Voice AI automatically books all appointments as Confirmed when setting a calendar event. This creates limitations for teams like ours that rely on manual confirmation workflows.
In our organization, we intentionally want appointments to be created as Unconfirmed first. This allows us to:
Review the lead and verify details before confirming
Follow up via call/SMS to ensure the lead will actually show
Automate based on status (e.g., Unconfirmed → Confirmed → Show/No Show)
Unfortunately, the Voice AI doesn’t allow us to control this behavior—it skips the “Unconfirmed” step and triggers downstream automations prematurely. This disrupts our workflow and inflates our “confirmed” metrics inaccurately.
👉 Can you allow a setting or toggle for Voice AI to book appointments as Unconfirmed instead of Confirmed?
👉 Or let us define the status the AI uses when scheduling?
This would greatly improve workflow flexibility for teams that want to vet or manually confirm appointments before treating them as official.
Let me know if you'd like a shorter version or if you're also submitting this to the Go High Level support team.
Ask ChatGPT
Log In
A
Adam Baxter
It is insane that appointments appear are automatically confirmed when booked by an AI agent. No one trusts an AI agent to get everything right the first time 100% of the time and it looks unprofessional on a business if they are sending emails confirming appointments that are then changed shortly thereafter. This needs to be able to be changed ASAP
A
Andre De Souza
I share the same opinion and reinforce this request. This feature is ideal for 3 of my subaccounts/clients. The current setting to always confirm a new appointment when booked by the AI Voice Agent is so disturbing for my clients operations. And extremely confusing to us since the Conversation AI and Calendar settings bookings are “new/unconfirmed”, as it should. So in my opinion there is a lack of standards making it confusing for my internal team and clients to understand this functionality