#I want to dynamically set built_in_tools.voicemail_detection in code with a dynamic voicemail_messa
1 messages · Page 1 of 1 (latest)
Short answer: No. The public docs don’t show support for overriding built_in_tools (including voicemail_detection) via conversation_config_override. Overrides are documented only for first_message, system prompt, language (and commonly voice), not for system tools. (elevenlabs.io)
What is supported:
- Add/configure voicemail detection as a system tool on the agent itself; it supports an optional custom “voicemail message.” (elevenlabs.io)
- If you need per-call personalization, use Dynamic Variables and reference them in text you control (docs note variables can be used in prompts, first messages, and tool parameters). This is the recommended way to inject runtime values. (elevenlabs.io)
Important migration note:
- The legacy inline tools array is deprecated and removed as of July 23, 2025. System tools must be specified via prompt.built_in_tools (by name), and client/server tools via prompt.tool_ids. Don’t send legacy tool objects in overrides or agent configs. (elevenlabs.io)
So the snippet you proposed (embedding a system tool object with params under built_in_tools inside conversation_config_override) isn’t a pattern the docs endorse. Configure voicemail_detection on the agent, and use Dynamic Variables to personalize any message content at runtime. (elevenlabs.io)
Sources:
Overrides | ElevenLabs Documentation
Voicemail detection | ElevenLabs Documentation
Dynamic variables | ElevenLabs Documentation
Agent tools deprecation | ElevenLabs Documentation
Voicemail detection | ElevenLabs Documentation
what about over a websocket?
Short answer: use dynamic variables in the WebSocket initiation; you can’t override built-in tool settings (like voicemail_detection parameters) via WebSocket overrides per current docs.
- What WebSocket supports at start: send a conversation_initiation_client_data message that can include conversation_config_override (prompt, first_message, language, tts.voice_id) and dynamic_variables. Example fields are shown in the Agent WebSockets reference. (elevenlabs.io)
- What overrides cover: overrides are limited to system prompt, first message, language, and voice ID (plus conversation.text_only in some SDK guides). Tool configuration is not listed as overridable. (elevenlabs.io)
- Recommended pattern for voicemail message: configure the Voicemail Detection system tool once, and set its “Voicemail Message” to a dynamic variable placeholder (e.g., {{voicemail_message}}). Then pass the actual value at runtime in the WebSocket initiation via dynamic_variables. The Voicemail Detection page documents the configurable voicemail message option, and the Dynamic Variables guide states they can be used in tool parameters. (elevenlabs.io)
Minimal WS init example:
{ "type": "conversation_initiation_client_data", "dynamic_variables": { "voicemail_message": "Sorry we missed you—call us back at 555‑0100." } }
If you’re receiving phone calls via Twilio, you can also return dynamic_variables (and any allowed overrides) from the inbound webhook the platform calls before the session starts. (elevenlabs.io)
References:
- Agent WebSockets API (conversation_initiation_client_data, dynamic_variables, conversation_config_override). (elevenlabs.io)
- Overrides scope and usage. (elevenlabs.io)
- Dynamic Variables in tools. (elevenlabs.io)
- Voicemail Detection tool and its configurable voicemail message. (elevenlabs.io)
Sources:
Agent WebSockets | ElevenLabs Documentation
Overrides | ElevenLabs Documentation
Voicemail detection | ElevenLabs Documentation
Twilio personalization | ElevenLabs Documentation
Agent WebSockets | ElevenLabs Documentation
Overrides | ElevenLabs Documentation
Dynamic variables | ElevenLabs Documentation
Voicemail detection | ElevenLabs Documentation
how do you make feature request? Not supporting dynamic variables in voicemail messages is terrible
Here’s how to submit a feature request to ElevenLabs:
- Use the Help Center form: open “Submit a request,” pick Customer Support, set Type to “Feature request,” and include your details and attachments. (help.elevenlabs.io)
- You can also follow the Help Center guidance to contact support directly and provide as much information as possible (screenshots/audio help). (help.elevenlabs.io)
- The Help Center link above is the official channel for feedback/bugs/feature suggestions. (help.elevenlabs.io)
- Optional: share the idea in the official Discord community to gather visibility/feedback from the team and users. (help.elevenlabs.io)
- ElevenLabs’ site confirms the Help Center/support chat are the correct routes for technical requests (not legal contact). (elevenlabs.io)
If you want, paste the exact JSON/payload you’re using for voicemail detection and I’ll help format a clear feature request description for the ticket.
Sources:
Submit a request – ElevenLabs
How can I contact support? – ElevenLabs
How can I submit feedback, suggestions or a bug report? – ElevenLabs
Is there a community for ElevenLabs? – ElevenLabs
ElevenLabs — Contact legal | ElevenLabs
can you open a ticket for me?