input-branching

Route voice inputs by using tag-based content prefixes like [voice-instruction], [transcript], and [HANDLED]/[REPLY] to direct realtime agent events to the correct processing path for tool calls or memory updates.

Handle voice transcripts without instructions by processing the delegated input as-is. The fallback path processes plain inputs directly when no explicit voice instruction tags are detected.

Realtime voice agents manage chit-chat by respecting [HANDLED]/[REPLY] tags to update context memory and generate responses without issuing new commands or triggering downstream tool calls.

Yes, you can use tag-based prefixes like [voice-instruction] and [transcript] to guide voice instruction routing, explicitly driving tool calls, memory updates, and response generation based on content.

The voice input routing system supports delegated agent handoffs using tag-based formats including [voice-instruction] with summarized transcripts, plain delegated inputs, and [HANDLED]/[REPLY] interactions.

Voice agent transcripts may fail to trigger tool calls if required content prefixes like [voice-instruction] or [transcript] are missing, causing inputs to fall into the plain delegated processing path.