I just finished Jordan’s video on Building a Production AI Voice Bot and had 2 clarifying questions: 1. Does the built-in Assistable knowledge base work with phone-based AI assistant conversations, or is it limited to chatbots and web call bots? 2. Why do we need to build a vector database using Supabase with Proship integration for the knowledge base? Would the built-in knowledge base function the same way, or is there a meaningful difference in capability or use case? Thanks in advance for the clarification!

Great to hear about voice V3. Wouldit reliably find/merge an existing GHL contact and reliably book an appointment used the merged contact in a web call (via programmable button or Orb)? We have been experiencing a persistent booking issue with Voice V2 in that scenario - it cannot find existing contact when given a phone num & it cannot book appt.

Has anyone successfully used the Assistable AI Assistant to book appointments with different durations based on appointment type? If so, how are you handling it? The standard book_appointment function doesn’t seem to support variable lengths.

We primarily use Assistable for voice and conversational AI, but have used the chat widget on site a while ago. Is there anyone using the chat widget for clients, seems counter-intuitive to pay GHL for chat widget then Assistable so need to find out widget situation. Thanks!

I created an AI Assistable using the AI Bot Builder, then created both a Chat Widget and a Voice Widget. I noticed that only one active tag was created. Is this expected behavior? Should the Chat Widget and Voice Widget each create their own active tags as well? Could you please clarify? Thanks, Lian