TryVox

ElevenLabs guide

Connect an ElevenLabs Conversational AI agent to a TryVox phone number.

ElevenLabs guide

End-to-end setup for ElevenLabs Conversational AI + TryVox numbers. Same shape as the Vapi guide with ElevenLabs-specific knobs.

Prerequisites

  • TryVox account with at least one Active phone number.
  • ElevenLabs account with the Conversational AI product enabled and at least one published agent.
  • An ElevenLabs API key with convai_* scopes (Dashboard → profile icon → API Keys).

1. Connect ElevenLabs

  1. TryVox dashboard → AI AgentsConnect provider.
  2. Provider: ElevenLabs.
  3. Display name: e.g. Conversational AI - support.
  4. API key: paste your ElevenLabs key.
  5. Connect.

The integration validates the key by listing your Conversational AI agents. If your workspace isn't on the default org, paste the workspace ID into Settings → workspace_id after connecting.

2. Bind a number for inbound

  1. Open the integration.
  2. Connect number.
  3. Pick a TryVox number.
  4. Pick an agent (we list your live Conversational AI agents).
  5. Connect.

When you bind, TryVox calls ElevenLabs' POST /v1/convai/phone-numbers with our termination URI and digest creds (using the v2 nested inbound_trunk_config + outbound_trunk_config shape), then PATCHes the new phone-number record with your agent_id. Inbound calls arrive at sip:<E.164>@sip.rtc.elevenlabs.io; ElevenLabs maps number → agent.

3. Outbound — 🚧 in progress

The same POST /v1/convai/phone-numbers call from step 2 registers our trunk for outbound on ElevenLabs' side, so the resource exists — but the egress path from your agent back through TryVox to the PSTN is being polished and is not GA in v1. Don't rely on agent-originated outbound for production yet; coordinate with support if you need it.

You'll see the entry under Conversational AI → Phone Numbers in your ElevenLabs dashboard (labelled TryVox <E.164>). Don't delete it manually from there — disconnect from TryVox and we'll clean up the ElevenLabs side for you.

Troubleshooting

SymptomFix
Key invalidMake sure the key has Conversational AI scope. Regenerate in ElevenLabs if unsure — TryVox validates both /v1/user (alive) and /v1/convai/agents (scope) on connect.
Empty agent listThe key is right but the workspace ID is wrong — set workspace_id in the integration's Settings.
Connect-number fails with "elevenlabs: …phone-numbers returned 409"A phone-number with this E.164 already exists on your ElevenLabs account from an earlier setup. Delete the stale entry in their dashboard, then retry.
Audio quality issuesElevenLabs prefers PCM/Opus; let the codec negotiation fall through.

On this page