Autocloz + Telnyx
Telnyx is the most complete voice carrier in Autocloz. You paste a Telnyx API v2 key, a Call Control connection ID and a from-number into Settings → Integrations, and reps can dial leads from the browser, receive inbound calls on their Telnyx numbers, and get call records and recordings on the lead timeline. It is also the only carrier that runs the parallel dialer, outbound IVR menus and AI voice-agent calls. You pay Telnyx directly for minutes and numbers.
What you can do with Telnyx
Telnyx plugs into the Call stack — bring your own carrier account, scoped to your workspace.
In-browser calling over WebRTC
Add the SIP username and password of a Telnyx Credential Connection and the dialer rings and carries audio inside the tab. Without them Telnyx still dials, but server-side, with no audio in your browser.
Every dialer mode
Telnyx supports call control, answering-machine detection and leg bridging, so preview, power and parallel modes all run on it. Parallel dialing is not available on any other carrier in Autocloz.
Recordings and inbound routing
Recording links arrive on the call.hangup webhook and attach to the call. Inbound calls ring the rep assigned to the dialled number, or the default receiver you set on the card.
How to connect Telnyx
Bring your own carrier account — you keep control of the account, the spend and the data boundary.
- 1
Create an API v2 key
In Telnyx Mission Control go to Account → Keys & Credentials → API Keys and create a key. It starts with KEY. Do not paste the Public Key here.
- 2
Create a Call Control connection
Under Voice → Programmable Voice create a Call Control or TeXML connection, copy its Connection ID, and point its webhook at https://<your-autocloz-domain>/api/voice/webhooks/telnyx.
- 3
Add credentials for browser audio
Create a Credential Connection (authentication = Credentials) and paste its SIP username and password into the WebRTC fields on the Telnyx card in Settings → Integrations.
- 4
Add your numbers and test both directions
Enter a number you own in E.164 as the default from-number, add numbers under Voice → Numbers, save, then place a test call and call your number from a phone.
What syncs between Telnyx and Autocloz
Outbound, Autocloz calls POST /v2/calls on your account with the connection ID and the lead's number. Inbound, Telnyx posts call events to the webhook URL above. Autocloz verifies the Ed25519 signature on each event with the Telnyx public key a super-admin stores once in the admin console, drops duplicates by event ID, and writes a call record with duration, hangup cause and the MP3 recording link.
Those records feed the lead timeline, the voice reports and the dialer's next-lead logic. Telnyx recording links are usually long-lived, and Autocloz re-requests a fresh link when a stored one has expired at playback time.
Why Telnyx is the default for dialer campaigns
Autocloz keeps a capability list per carrier and refuses a dialer mode the carrier cannot run, instead of quietly falling back. Telnyx is the only carrier marked for server-side dispatch, bridging and parallel legs, so a supervisor can start a campaign and have calls originate without a rep's browser placing each one. The same programmable answer webhook lets Autocloz walk an operator-built IVR tree on outbound calls.
AI voice-agent calls use Sarvam for speech and language, but the audio still travels over a Telnyx media stream. A Sarvam agent on any other carrier is refused with a message saying so. See AI agents for what those calls can and cannot do today.
What Telnyx does not do in Autocloz
- It does not buy or port numbers for you. Numbers are bring-your-own: buy them in Telnyx, then add them in Autocloz.
- Telnyx SMS is a separate setup (a Messaging Profile) and is covered on the Telnyx SMS page.
- It does not resell minutes. Your Telnyx balance pays for every call.
Troubleshooting Telnyx
- Calls connect but you hear no ringback in the browser.
- The WebRTC SIP username and password are empty or belong to a Call Control connection. They must come from a Credential Connection.
- Inbound events are rejected with a signature error.
- The Telnyx public key is missing or wrong in the super-admin console. Paste the Public Key from Keys & Credentials there, not the API key.
- Inbound calls ring nobody.
- Assign the number to a rep under Voice → Numbers, or set a default inbound receiver on the Telnyx card.
Part of the Call stack
Telnyx is one of several carriers you can run behind the Call channel. They share the same dialer, CDR logging, recordings UI and compliance gates.
Explore the Call featureRelated integrations
In-browser Voice SDK calling + low international SIP rates; CDR poll for retroactive ingest.
View integrationIndia-native voice with per-agent OAuth, presence sync + recording import.
View integrationProgrammable Voice — bring your own account for outbound calls.
View integrationFrequently asked
Do I need both a Call Control connection and a Credential Connection?
For browser audio, yes. The Call Control connection carries API-placed calls and webhooks; the Credential Connection is the SIP login the browser uses to place and hear the call.
Can one SIP login serve my whole team?
Yes. One Credential Connection is enough for everyone in the workspace. The caller ID for each call is picked from your numbers by your routing rules.
Which dialer modes work on Telnyx?
Preview, power and parallel. Parallel needs answering-machine detection and bridging, which only Telnyx provides in Autocloz.
Run Telnyx inside Autocloz
Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 5 users, unlimited on paid.