Voice agent integration
Deepgram's Voice Agent API runs speech, language and voice behind one WebSocket. Bridge it to a Vobiz stream and you have a phone-callable agent on numbers in 130+ countries, reaching 190 — with one vendor for the conversation, one for the line, and no turn-taking logic of your own.
Before you start
This one is code you run, not a provider you select. Vobiz publishes an open-source reference bridge in Python that joins a Vobiz media stream to Deepgram's Voice Agent API, and you deploy it somewhere Vobiz can reach over HTTPS and WSS — a tunnel is fine while you are building. Two values are required to configure it. Everything else ships with a working default.
Why this pairing
Most voice agents are an assembly job: a speech-to-text vendor, a language model, a text-to-speech vendor, and your own code deciding when the caller has finished talking. Every seam is a place where latency accumulates and turn-taking goes wrong. Deepgram collapses that into a single API — speech, language and voice behind one WebSocket, with turn-taking and interruption handling built in, on one API key and one bill.
What is left is the phone leg. Vobiz provides the numbers and carries the audio, and publishes the bridge that joins the two, so you end up with a working phone agent, two vendors and source code you own.
What you get
The bridge is a thin relay. Deepgram owns the conversation, Vobiz owns the call, and the code between them is yours.
Speech-to-text, the language model and text-to-speech run behind a single Deepgram WebSocket. No separate speech vendor, no separate voice vendor, and no separate model provider key — Deepgram manages the model connection and bills it through your account.
An open-source Python reference implementation, maintained by Vobiz, with the whole protocol handled: format negotiation, frame slicing, barge-in, checkpoints and the Vobiz control messages. Two required values to configure. Fork it, deploy it, change what you need.
Local, mobile and toll-free inventory across 130+ countries, with outbound reach to 190, including regulated formats where a market demands them — India's 140-series and 1600-series among them. Inbound and outbound both run through the same bridge.
When a caller talks over the agent, Deepgram signals it and the bridge tells Vobiz to flush whatever is still buffered, then waits for confirmation before the next reply starts. Without both halves the agent either keeps talking over the caller or starts its next sentence mid-word.
Sending audio is not the same as playing it. After each turn the bridge asks Vobiz to confirm playback, which is what lets an agent say goodbye and hang up without clipping its own last word — and makes a reply the caller never heard show up in your logs rather than only in the call.
The bridge ships configured for a region, a voice and a recognition vocabulary, and a single setting moves all of it. A health endpoint echoes the region, models, voice and audio profile actually in use, so you can confirm what is running rather than what you meant to set.
How it works
Two required values, a public endpoint, and a number pointed at it.
Clone the repository, create a virtual environment, install the requirements, and copy the example environment file. Fill in your Deepgram API key and the public hostname Vobiz will reach. Everything else has a working default.
Start a tunnel if you are developing locally, then start the app. Call the health endpoint to see the resolved answer URL, stream URL, region, models, voice and audio profile before you point a call at it.
For inbound, create a Voice Application in the Vobiz Console with your answer URL, then attach a number to it. For outbound, place a call through the Vobiz API with the same answer URL — the bridge does not care which direction the call came from.
Dial the number, or answer the outbound call. The bridge prints the conversation as it runs, with a per-turn latency breakdown across recognition, model and synthesis so you can see which stage is costing you time.
The full protocol reference, the troubleshooting table and the deployment notes are in the Vobiz docs.
Read the integration guide
Get started
Create a Vobiz account and get a number, clone the bridge, and add your Deepgram key.
The health endpoint tells you when it is ready for a call.
FAQ
CRM and helpdesk integrations: Salesforce · ServiceNow · ClickUp · Pipedrive · Expedify · HubSpot · Freshdesk · Zendesk
Voice AI platforms on Vobiz: Bolna · Vapi · Retell AI · LiveKit · ElevenLabs · See all integrations
Connecting by API instead of the dashboard: Retell AI API guide · ElevenLabs API guide
Deepgram builds speech-to-text, text-to-speech and voice agent APIs. Vobiz is not affiliated with Deepgram; this integration uses Deepgram's public Voice Agent API.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.
