AI-generated Answer for rohith_27334
Short answer: ElevenLabs doesn’t document a built‑in “blocklist”/call‑blocking toggle. The documented way to stop unwanted calls is to detect the caller ID in the agent and immediately terminate the call with the End Call system tool.
How to implement with Telnyx SIP
- Connect Telnyx to ElevenLabs
- Follow the Telnyx SIP trunking guide to route your Telnyx numbers to an ElevenLabs agent. (elevenlabs.io)
- Read the caller ID in your agent
- The caller’s number is exposed to the agent as the system dynamic variable system__caller_id. You can reference this in prompts/tools to decide what to do. (elevenlabs.io)
- End the call when the number is blocked
- Enable the End Call system tool on your agent (it’s on by default for dashboard‑created agents). In your agent’s instructions, add a rule like: “If system__caller_id matches a denylist, play a short message and call end_call.” The tool supports an optional message and a required reason. (elevenlabs.io)
Optional: centralize the blocklist check
- Create a server tool (webhook) that takes system__caller_id, checks your blocklist, and returns a flag (e.g., blocked=true). In your agent prompt, instruct the LLM to call the server tool first and, if blocked, immediately use end_call. (elevenlabs.io)
Notes and limitations
- The SIP trunking docs confirm caller/call metadata is available to the agent; they do not document a pre‑answer SIP rejection feature. Practically, this approach ends the call right after the agent greets (or with a single short message) using end_call. (elevenlabs.io)
References
- Telnyx SIP trunking with ElevenLabs: Connect Telnyx SIP trunks with Conversational AI. (elevenlabs.io)
- SIP trunking overview and metadata availability to agents. (elevenlabs.io)
- System dynamic variables (system__caller_id). (elevenlabs.io)
- End Call system tool. (elevenlabs.io)
chrome terrace
fierce birch