Skip to main content
Voice agents are standard agents configured with a voiceConfig and used inside call flows via the CONNECT_AGENT node. This document covers the voice pipeline configuration, the CONNECT_AGENT node schema, and audio/provider details needed for frontend integration (call flow builder UI). Related: End Call Tool & Exit Modes | Agents API | Call Flow API

Types


CONNECT_AGENT Node Schema (Call Flow Builder)

This is the full node schema used in the call flow JSON:

Configuration Defaults & Limits


Voice Pipeline (v0 — Fixed Providers)

In v0, the STT and TTS providers are hardcoded. There is no runtime provider selection.

Platform Defaults

What Can Be Overridden

Only these fields are configurable at the agent level: Note: Node-level voiceConfig overrides are accepted by the schema but not yet applied in v0. The agent’s own voiceConfig is always used. Important: ElevenLabs TTS output format is always forced to pcm_8000 (raw PCM, 8kHz, 16-bit signed mono) to match the AudioSocket format. MP3 output is not supported and will throw an error.

Audio Format

All audio in the voice pipeline uses PCM 16-bit mono at 8kHz (Asterisk AudioSocket native format):

Output Path Routing

When the conversation ends, the node routes to the next node based on the exit reason: Note: For error exit reason, the fallback is the default output, not onComplete. This prevents error loops.

Conversation Flow Diagram


Latency Budget (Typical Turn)


Validation Rules (Call Flow Builder)

These constraints are enforced during flow validation (before execution):

Error Types

These error types may be reported in conversation analytics or flow execution logs: Retry Strategy: Recoverable errors use exponential backoff: delay = min(1000ms * 2^retryCount, 5000ms). Max 3 retries.

Session Limits