Integrations · Voice infrastructure
LiveKit — The Self-Hosted Voice Stack Behind Eligoo’s AI Calls
LiveKit is the open-source real-time media platform that Eligoo runs, self-hosted, to carry every AI phone call: a media server, a SIP gateway that connects to your telephony trunk, an egress service that records audio when you enable it, and an agents worker that runs the AI voice agent inside each call. It is infrastructure, not a connection you make — you never need a LiveKit account.
By signing up you agree to the Terms and Privacy Policy.
What does Eligoo do with LiveKit?
An AI phone call is a loop: audio comes in from the phone network, is transcribed, is reasoned over by a language model, is turned back into speech, and goes out to the caller — all fast enough to feel like a conversation. Something has to hold that loop open, move the audio around with low latency, and let the agent interrupt or be interrupted. In Eligoo that something is LiveKit.
Eligoo hosts the whole LiveKit stack itself rather than routing calls through a third-party voice-AI vendor. Four pieces run together: the LiveKit server, which handles the real-time media; the SIP service, which bridges the phone network to that media; Egress, which writes audio recordings when a workspace turns recording on; and an agents worker, which runs Hook’s voice agent in each call, wiring speech-to-text, the language model and text-to-speech together.
What this means for you is that the only things you bring are the parts that are genuinely yours: a phone number on a SIP trunk, and the speech and model providers you want to pay for. The media handling in the middle is Eligoo’s responsibility.
How the integration works
There is no connect step for LiveKit. This is the path a call takes through it.
- 1
You connect a trunk and providers
A SIP trunk from Twilio, Telnyx, Plivo or Vobiz gives the stack a phone number. Deepgram, ElevenLabs or OpenAI keys give it ears and a voice; a connected model provider gives it a brain.
- 2
A call is placed or received
Outbound, the agents worker asks the SIP service to dial the number over your trunk. Inbound, a call arriving on your number is dispatched to the worker and answered.
- 3
The agent runs inside the room
The worker joins the call as a participant, streams the caller’s audio to speech-to-text, sends the transcript to the model with Hook’s brief, and streams the reply through text-to-speech back into the call. Turn detection and interruption settings control who speaks when.
- 4
Outcomes are written back
When the call ends, the transcript, outcome, notes and — if enabled — the recording produced by Egress are stored in your workspace against the lead.
- 5
Browser test calls use the same path
A test call from the browser joins the same kind of room, minus the SIP leg, so what you hear in testing is what a prospect hears on the phone.
What data flows between Eligoo and LiveKit
- Because LiveKit is hosted by Eligoo, call audio does not leave Eligoo’s infrastructure to reach a separate voice-AI vendor. It flows from your trunk into the LiveKit server and out to the speech and model providers you connected, under your own accounts.
- Stored in your workspace: transcripts, outcomes, notes, and audio recordings only when you enable recording. Recordings are kept alongside the lead record and can be deleted on request.
- Sent to your providers during a call: caller audio to the speech-to-text provider, transcript text plus the agent brief to the model provider, reply text to the text-to-speech provider.
- Sent to your telephony provider: the SIP signalling and media for the call, as with any call on your trunk.
- Not involved: any LiveKit Cloud account. Eligoo does not use LiveKit Cloud and you do not need to sign up for anything at LiveKit.
Which AI employees use it
One employee talks on the phone; the others feed it and read its results.
What businesses can automate with it
Outbound calling campaigns
A lead list dialled inside a calling window, one line at a time, with daily roll-over — after approval.
Inbound answering
Calls to your number are picked up, qualified and logged when nobody is free.
Optional recordings
Audio captured by Egress for review, stored in your workspace.
Test before you dial
Iterate on the brief, voice and interruption settings from the browser.
Frequently asked questions
Do I need a LiveKit account to use Eligoo’s AI voice agent?
No. Eligoo hosts LiveKit itself. You bring a SIP trunk and your speech and model provider keys.
Is Eligoo built on LiveKit Cloud?
No. Eligoo runs the open-source LiveKit server, SIP service, Egress and an agents worker on its own infrastructure.
Can I bring my own LiveKit deployment?
Not today. The stack is operated by Eligoo so that trunks, recordings and the agents worker behave the same in every workspace.
Where do call recordings live?
In your workspace, produced by Egress only when recording is enabled. Check consent rules for recording where you operate.
Why self-host instead of using a voice-AI API?
It keeps the call path under Eligoo’s control, lets you use your own trunk and provider accounts rather than a vendor’s bundle, and means the audio does not pass through an additional third party.
What affects call latency?
Mostly the speech-to-text, model and text-to-speech providers you choose and the region your trunk terminates in. A fast model such as one served by Groq and a low-latency voice noticeably shorten the pauses.
Sources
Hear the voice stack for yourself
Connect a trunk, write Hook’s brief and make a browser test call. Actions that reach the outside world — sending an outreach sequence, launching or changing ad spend, publishing outside an approved calendar, starting a calling campaign — wait in an approvals queue until a person approves them.
By signing up you agree to the Terms and Privacy Policy.
Last updated 23 September 2026