Yesterday we wrapped up another insightful Amplify Voice Build Hours session, and I'm thrilled about the collaborative problem-solving we accomplished today. For those who couldn't join, here's a quick recap: - Time Formatting Troubles Solved! @Matt Cohn and the group dove into formatting date and time in Make, especially focusing on time zones. We explored the 'format date' function and how to set the correct time zone for Europe/London. Big thanks to Peter for suggesting the use of 'set date' and 'set time' functions for long-term time zone handling. - Outbound Agent Scenarios Simplified: @Guy Robertson brought up an interesting challenge about building an outbound agent for support calls with four possible call scenarios: no answer, disconnected number, voicemail, and engagement. We discussed strategies on building separate scenarios for testing and then combining them using routers. Also touched on the divert call feature in Vapi and its cost implications. Exciting stuff! - Tackling Twilio A2P Registration: @Harry Goldsmith shared his journey with Twilio A2P compliance registration. We discussed the variable timeframes for approval and how it can impact your projects. We guided Harry on checking his registration status and troubleshooting potential issues. Remember, patience is key here! - Vapi Integration Hurdles: @Harry Goldsmith also encountered some issues with Vapi integration and sending booking links. We suspected A2P compliance might be the culprit. We delved into checking Twilio's error logs to pinpoint the problem. It's all about those little details! - Introducing Vapify!: @Peter Kakoma gave us an exclusive look at Vapify, his platform for white-labeling Vapi voice assistants. He walked us through the user journey, dashboard features, and how you can customize branding, subdomains, and email settings. It's an impressive tool that could be a game-changer for agencies looking to offer branded voice solutions. - Vapify Pricing Feedback: We had an open discussion about Vapify's pricing tiers. Peter presented the Starter, Business, Pro, and Enterprise plans. Participants provided candid feedback on the pricing structure, suggesting a shift towards per-client or per-sub-account pricing. It's always great when the community comes together to help refine a product! - Rethinking the Pricing Model: The conversation evolved into exploring potential pivots in Vapify's target market and use cases. The feedback was invaluable, and Peter appreciated the insights for improving the platform. Collaboration at its finest!

Hey everyone, so stoked to be part of this community I am a Senior Software Developer so highly skilled in Tech, Automations, System Integrations, and now Voice AI If anyone is very skilled in Sales, Branding and Marketing and would like a Tech Fulfilment partner, DM Me. I have seen VoiceAI sell itself. Just have a nice website with a demo button and buy button - Lets crush it everyone

Hi all. I wonder how you manage multiple clients on Vapi. Do you create one Vapi account for each client? Do you keep all the AI agents in one account? Or maybe you create multiple organizations for clients under one single account? I appreciate any help you can provide.

I just watched an Alejo video in which he shared how to book an appointment by sending a Celandly link through SMS. So I have a question Can we send a Google Calendar link instead of a Celandly link to book an appointment?

Hello all - new to delivery of solutions to clients :) I have a client who I'll be building a Make automation for. How do we go about 'sharing' the Make scenario with the client when we are testing and then afterwards to deliver the project? I have the same question for customGPT. Thank you.