# 100x More Reliable Voice Agents

## Executive summary

Unmute is introduced as an open, declarative standard for building voice agents, designed to solve the critical problem of vendor lock-in and architectural fragility in the current voice AI landscape. Current agents are often embedded within specific platforms (e.g., ElevenLabs, VAPI, LiveKit), making them non-portable. Unmute shifts the paradigm by declaring the agent's behavior, tool calls, data flows, and failure handling in a single, compiled package, making the LLM an optional resource rather than the sole decision-making spine. This approach ensures structural guarantees and portability across different cloud runtimes.

## Key takeaways

- Declarative Execution and Portability: Unmute allows the agent's behavior to be defined in a single, portable package that compiles to various runtimes (e.g., PipeChat Cloud, LiveKit Cloud, or Slang's architecture). This means the agent's core logic remains version-controlled IP, regardless of the underlying infrastructure or cloud region.
- Addressing LLM Over-Reliance: Traditional agents assume the LLM is the decision-making spine, leading to unpredictable, expensive, and difficult-to-govern behavior. Unmute enforces execution through declared steps, making the LLM an optional resource that must 'earn its place' in the call.
- Structural Guarantees over Instructions: The standard moves beyond the false choice between rigid IVR and complex single-prompt agents. By splitting the work into discrete, context-limited steps, the system achieves determinism—allowing specific rules (like a regulated disclosure) to be locked down while other parts remain generative, all within the same call.

## Technical details

- Agent Architecture: The standard mandates that tool calls, data flows, step transitions, and failure handling must be declared and enforced by the compiled package, rather than being left solely to the LLM runtime. This structural approach significantly reduces token usage and latency compared to single-prompt methods.
- Resource Management: The system treats resources (like a frontier model, cached audio, or compliance disclosure) as composable elements that the agent composes around the caller and use case, rather than relying on a single sequential pipeline.
- Compilation Workflow: The process involves compiling the agent definition (e.g., `agent.yaml`) into running code. This compilation step validates the agent's structure and wires up the necessary tools before deployment, ensuring the entire system is valid before execution.

## Practical implications

- Reduces vendor lock-in by decoupling agent logic from specific platform implementations.
- Improves reliability and governance by replacing monolithic prompts with discrete, verifiable steps.
- Optimizes operational costs by reducing token usage and latency, as only the necessary context is passed to the model at any given turn.

## Topics

Voice AI, Agent Orchestration, Declarative Programming, MLOps, Software Architecture, Unmute, PipeChat, LiveKit, ElevenLabs, VAPI, Langfuse

Source: https://www.youtube.com/watch?v=1v9m-RUfaEY