I think at the moment, AI beginners (including those of us who've been in this from the start) are focusing too much on the Voice AI hype, and not using AI to really what its supposed to be used as.....building AI systems. The use of make, zapier, n8n, is simply just glorified static automations. However, building true AI systems where the LLM actually makes decisions based on the given/applicable data is where we should be driving to. Most companies are not taking advantage of AI's full potential (because of us AAA's). Everyone is launching chat interfaces on top of their existing products - chats for everything. Chat is just a UX paradigm shift. What used to be a GUI is now a Chat, and you can talk to it. But at the end of the day, you are still accomplishing the same thing with software. Sure you can get to information faster. But if all we’ve done is move the user interface to a chat interface, we are not making the most of AI's capabilities. So what’s next? Instead of talking to AI to get information back... imagine if you talked to AI so it does something for us, completely entirely what we are trying to accomplish. That's where it's at, and the innovation is happening with AI Agents that will lead to full automation of entire jobs with agentic solutions. 𝗦𝗼𝗿𝗿𝘆 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝘀𝗽𝗶𝗲𝗹.....the point being is that Stack AI specializes in creating AI-powered workflows and custom assistants, emphasizing generative AI capabilities. It is designed for organizations that require advanced AI functionalities integrated into their operations, particularly in regulated industries needing enterprise-grade security. I deal a lot with the UK's NHS (actually, GP's are my main target audience) and US Law Firms. Hence why it was mandatory for me to switch out from using n8n. n8n just functions as a flexible, fair-code platform primarily focused on workflow automation without extensive coding. It excels in connecting various applications through a visual builder but lacks built-in AI capabilities and autonomous agents.

@Alejo and Paige Pijuan Great video (as always)! Can you do a buildout on VAPI (or, whatever no-code platform is the best fit) for a Call Center? Or, even better, can you do a deepdive into Deepgram's deployment methods, including their self-hosted offer? My target audience at the moment is the UK's NHS with the major obstacle being security and privacy (local servers are a priority for the NHS). It seems that Deepgram is noticing this gap in the market and is trying to be a one-stop-shop.....no need for AWS or G-Cloud for optimal server processes when dealing with Enterprise clients (like the NHS).