This is one of those updates that looks small in the UI, but actually changes how you should structure complex voice agents. After building 25+ voice agents that have handled 25,000+ calls, the biggest issue I kept seeing was this: Single-prompt agents are fast to build, but once the prompt gets close to 10,000 tokens with tools, booking rules, edge cases and support logic, the agent becomes harder to control. Workflows solve part of that, but they can become too rigid when the conversation needs to stay flexible. Procedures sit in the middle. They let you turn specific tasks like updating a booking, handling refunds, checking eligibility, or using a tool into triggered step-by-step playbooks that only load when needed. In the video I cover: - Why giant prompts start breaking down - When to use single prompts, workflows, or Procedures - What goes inside a Procedure: name, trigger and content - How to write triggers so the agent actually knows when to use them - How Procedures reference tools, knowledge bases and other Procedures inside ElevenLabs The simple rule: Use a single prompt for simple agents.Use workflows for fixed call paths.Use Procedures for complex tasks that still need flexible conversation. https://youtu.be/bCeErhzbds4