Workflow design for a voice agent project
Hey Azim! I saw your video about the Solacium app’s voice agent. Very cool! I’m building a voice agent for my appliance repair business to handle after-hours appointment requests, but I’ve been running into some challenges with how to structure it. After seeing the scale of your workflow, I realized I probably need to think a bit bigger. I was hoping you might have some pointers on how to approach designing the logic. Should I rely more on an AI agent to infer next steps dynamically, or should I use switch nodes and define explicit paths as much as possible? Here’s what I’m working with: when customers call in, they can be either new or returning, and they might have several intents, things like requesting pricing, following up on an appointment, filing a complaint, ordering a part, or booking a first appointment. Eventually, we want the voice agent to handle all of those and more, but for now, the goal is booking new customers and for all other intents the voice agent can just to take a message so our office staff can call back the customer. The part I’m focusing on right now is booking a first appointment. - We only serve certain postal codes, so if the customer is outside our service area, we need to decline service. We just ask the customer what their postal code is. - For valid areas, the agent should provide a quote based on the appliance, brand, and service type which can have various combinations. - If the customer accepts the quote, the agent offers appointment slots: morning (9 am–1 pm) or afternoon (12 pm–5 pm), excluding same-day, next-morning, weekends, and statutory holidays. This booking would be sent by email to the office and they would enter it in the calendar. I’m using ElevenLabs, Twilio, and n8n, but I’ve hit a wall getting the logic to work cleanly. I’ve tried the switch node method, and then i was leaning more toward an AI brain + multiple tools setup, but i see you have multiple switches and multiple brains so maybe I'm not thinking about this quite right. And note that the idea is to add the other tasks over time so a scalable structure is what I'm hoping to start with. Any insight you could share would be super helpful! I’ve attached a few screenshots for reference of what I've been attempting to do.