Voice AI

In voice ai agent, when a caller mentions a phrase I want to transfer the call to a cell phone. If that caller doesn’t pickup, I want to transfer it to a different cell phone. I know the primary transfer can be done within the agent with an action, but the secondary transfer is not currently possible.

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.

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.

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.

We can currently send an email transcript after the call is completed, but it would be nice to actually send the recording and summary with it too

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.

An ability to test or demonstrate the Voice AI by just clicking a widget or a button in a funnel/website.

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.

AI Studio already has the ability to build blogs, but today I don’t feel comfortable using it for production websites because the content layer isn’t dependable enough. I’ve personally experienced blog articles being modified or completely disappearing after prompting AI Studio to make changes that had nothing to do with the blog itself. That makes it difficult to trust AI Studio for SEO-focused websites where articles represent months or years of work. Feature Request Please separate content from page generation by introducing a dedicated CMS layer inside AI Studio. Instead of storing blog articles as part of the AI-generated page structure, store them in a protected content database that AI prompts cannot accidentally overwrite. The CMS should include: * Blog Posts * Categories * Tags * Authors * Media Library * Draft / Published states * Scheduled publishing * Revision history * Autosave * Restore previous versions * Backups * Dynamic routing (/blog/[slug]) * Search * RSS Feed * Sitemap generation * SEO fields (Title, Description, Open Graph, Canonical) Most Important Requirement AI prompts should never modify or delete CMS content unless the user explicitly asks to edit that specific article. For example: If I prompt AI Studio: “Redesign the homepage.” or “Improve the Services page.” or “Change the color palette.” My existing blog articles should remain completely untouched. Likewise, if I ask AI Studio to generate a new page or redesign another section of the website, it should never rewrite, regenerate, move, or delete existing blog content unless I explicitly instruct it to do so. Why this matters Many agencies and businesses rely on blogs for long-term SEO. Articles often represent dozens or hundreds of hours of work and become valuable business assets over time. Right now, AI Studio is an amazing website builder, but because blog content can be unintentionally affected by unrelated prompts, it’s difficult to trust it as the primary platform for content-driven websites. A protected CMS architecture would make AI Studio a true replacement for WordPress, Webflow CMS, and other content management systems while giving users confidence that their content is safe.