Voice AI

This would be great for 2 reasons. 1) When one of your contacts is calling using the AI phone number they would be recognized " Hi John" Thanks for calling, how can I help you? 2) When doing voicemail drops to sell AI voice the caller could call back, be recognized and have a demo of what their missing on their call back.

With companies like Nedzo that have ultra realistic voices, I think the HL voice ai has a long way to go. Would be good if the voices could sound less robotic.

We already have a caller on the line, why does the bot need to transfer them to another phone number so another bot can take over?

I have a client who would like his inbound AI employee to use his own voice so that his customer interactions are more personable. I would like to be able to upload an AI voice file that I've trained with external software, or be able to train the custom AI voice within GHL. Thank you for all you do for us! ie. https://elevenlabs.io/voice-cloning

The AI Voice Agent could experience spam phone calls. Could there be a way to block incoming numbers - I see this as being a problem with my GHL (business number). This could disrupt Automation and Workflow with bad information and fake contacts.

Currently, Voice AI uses structured prompts and logic to handle live phone conversations and guide callers through different questions and scenarios. My recommendation is to extend that same conversational framework into website forms, allowing a form itself to function as a chat window rather than a static set of input fields. ⸻ Conversational Form Window The idea is to embed a chat-style interface directly inside a form, using the same prompts, training, and agent goals that power Voice AI or Conversation AI. • Instead of a floating chat widget, users could interact with the AI directly within the form section of the page. • The AI would guide visitors through questions in a natural, message-based format, collecting the same information as a phone call — but through text. This would make forms feel interactive and human while maintaining the same conversational flow and data capture logic that already exists within the Voice AI system. ⸻ Benefits • Seamless user experience: Visitors stay on the page and interact within the form without pop-ups or distractions. • Professional appearance: The chat interface becomes part of the page design, matching brand aesthetics rather than relying on a floating icon. • Consistent data collection: The same prompts and workflows used in Voice AI can be mirrored here, ensuring uniform lead qualification across phone and web. • Higher engagement: Visitors who don’t want to speak on the phone can still complete a guided, conversational intake through the website. ⸻ This would give GoHighLevel users a way to create conversational, AI-powered forms that feel personalized and dynamic — not just another chatbot floating on the screen. It also keeps the logic unified across Voice AI, Conversation AI, and now interactive web forms. Thank you for considering this — it could be a major step forward in how businesses collect leads and communicate through AI on their websites.

As we work towards offering AI receptionists to clients, it would be super helpful if the AI could train based on previous call transcripts. For example if we have someone call in and ask to speak with Patty, the AI may not realize they're asking for Patricia. Or maybe industry jargon is used on calls, it would be helpful if the AI can learn what all those terms are so it can respond properly. Some of this stuff only turns up in client calls, and in an ideal scenario, after the call the AI would ask the sub account owner or admin to clarify or add context to what was discussed on the call.

The more you invest in building a sophisticated Voice AI agent, the harder the platform makes it to maintain one. Once your agent prompt grows past the 16,000 character retrieval limit, you can no longer view your own agent in full — making it nearly impossible to audit, edit, or improve it with confidence. ________________________________________ The Problem: As Voice AI agents mature — adding qualification flows, lead scoring logic, branching paths, and behavioral guardrails — their prompts grow naturally in length and complexity. Once that prompt crosses the 16,000 character API retrieval cap, the response is cut off. The full prompt simply cannot be returned in a single pull. This means agency builders are left working blind — unable to see the complete instructions their agent is running on, and unable to make precise edits without risking unintended changes to the parts they can't see. The Impact: For agencies building and reselling Voice AI, this is a direct liability. A prompt you can't fully read is a prompt you can't fully trust. Performance issues in front of paying clients become harder to diagnose, and the quality of the agent — and the agency's reputation — suffers for it. The Ask: Raise the Voice AI agent prompt retrieval limit well beyond the current 16,000 character cap — or introduce chunked, paginated, or exportable prompt access — so that agency builders always have complete visibility into the agents they're selling.

You built the perfect Voice AI agent — then had to start cutting pieces of it. That's the reality for agencies hitting the 15 in-call action cap. Every feature removed to stay under that limit is a compromise your client will notice — and a reason they'll question the product you sold them. ________________________________________ The Problem: The current 15 in-call action limit forces Voice AI builders to make compromises that directly degrade the end-user experience. When an agent is fully built out — with qualification questions, lead scoring, field captures, and call routing — the ceiling of 15 actions is hit before the agent reaches its full potential. This means critical features must either be removed, substituted with lower-quality alternatives, or left out entirely. The result is a less capable, less accurate agent being delivered to end customers. The Impact: For agencies reselling Voice AI to clients, this isn't just a technical limitation — it's a business problem. Clients expect a polished, fully-featured agent. When compromises caused by a 15-action ceiling are visible in performance, it reflects poorly on the agency and erodes customer confidence in the product. The Ask: Raise — or remove — the 15 in-call action cap so that builders can deliver the full experience their clients deserve without having to choose between features.

Generate a message to welcome our newly registered customers