This VICIdial AI integration guide explains how VoiceOI puts AI agents on an existing VICIdial system. Each bot is a VICIdial remote agent: VICIdial keeps dialing, the bot runs the conversation, and the outcome of each call is written back as a disposition.
Last reviewed October 2026
Published guides describe a few ways to connect AI to VICIdial. They differ in where the live call sits and how results reach VICIdial.
| Method | How it works, as the guides describe it | Described by |
|---|---|---|
| SIP trunk routing | VICIdial dials through its normal carriers and routes answered calls over a SIP trunk to the AI platform. Trillet adds an API bridge that syncs dispositions and lead updates. | Klariqo, Trillet |
| API lead injection | The AI platform handles calls independently from VICIdial, then pushes lead data back into VICIdial lists or campaigns through the VICIdial Non-Agent API. | Klariqo |
| SIP extension or agent login | The AI registers as a SIP extension, like a remote human agent's phone. Dialtera's guide creates a VICIdial user and a SIP or WebRTC phone for it. | Klariqo, Dialtera |
| Remote agents (VoiceOI) | Each bot is a VICIdial remote agent: VICIdial sends answered calls to its external extension, and the bot writes the disposition back. | This guide |
Sources, each the publisher's own guide, reviewed October 2026: Klariqo, "How to Add AI Agents to VICIdial: The Complete 2026 Guide"; Dialtera, "Configure AI Agent in VICIdial"; Trillet, "ViciDial Integration for Enterprise Call Centers: Production-Proven Voice AI". Guides change, so check them for current details.
A standard VICIdial feature. A remote agent is a VICIdial agent seat whose calls go to an external extension instead of an agent screen, which matches how a voice bot works.
VICIdial stays in charge. Lists, the hopper, the dial method, recycling and reports keep working as they do today.
The call stays live. The bot is on the answered call, so a qualified lead can go straight to a closer.
Results land in VICIdial. Call outcomes are written back as dispositions.
Bots come in blocks. Bulk provisioning creates many bot remote agents at once.
New to the feature? The guide to VICIdial remote agents quotes VICIdial's own help for every remote agent field and sets out what the feature can and cannot do.
An AI agent for VICIdial does a fronter's first-contact work: it takes the answered call, asks the qualification questions, sets the disposition and transfers qualified leads to a human closer. VoiceOI offers two kinds, both running as remote agents.
You set the persona, opening line, qualification questions, knowledge base, rules on what it must not say, and the exits that end the call, each mapped to a VICIdial status.
Real voice recordings on a branching script, for campaigns where every word must be fixed in advance.
Both are English-first. Bot types, response time and prices are on the VICIdial AI voice bot page.
The VoiceOI team carries out the integration steps with you and connects the bots to your VICIdial setup, so you do not have to configure it yourself. Talk to our team to start. The steps below show what happens, on your VICIdial server and in VoiceOI.
Lay out the script in the no-code builder, choose the VICIdial status each outcome writes, and run test calls in the simulator.
The VoiceOI team connects your VICIdial server to your VoiceOI account using an API login you provide, so VoiceOI can read the campaigns and write back statuses.
The VoiceOI team allow-lists VoiceOI's server IPs on your VICIdial server and adds your dialer's IPs in VoiceOI, so calls and status updates can pass both ways.
Your carrier is added in VoiceOI's Carrier Manager with the sip.conf or pjsip.conf block your VICIdial carrier uses. Any SIP carrier works, including Twilio and Telnyx trunks, and the configuration reloads on save.
The in-group for the closers who take bot transfers is set up and allowed in the campaign, so transfers are accepted.
Choose the starting user ID, number of bots, lines, external extension and campaign. VoiceOI creates the VICIdial users and phones for the bots through the API connection from step 2.
Run a small test campaign and check two-way audio, transfers into the in-group, and dispositions in VICIdial.
Start the campaign as usual, review recordings, transcripts and dispositions, and provision more bots when you need them.
Step 1 uses the no-code AI voice agent builder. To dial some campaigns without VICIdial, the same carrier also runs VoiceOI's built-in dialer; see SIP trunk for AI voice agents.
Since the FCC's February 2024 ruling, AI voices count as artificial voices under the TCPA, so telemarketing calls on a VICIdial campaign need prior express written consent before bots start dialing. Compliance stays with you, and this is not legal advice. The TCPA controls for AI voice bots page lists what VoiceOI provides.
A remote agent bot uses the standard remote-agent fields in VICIdial. Bulk provisioning fills them in for a whole block of bots, so you don't enter them one entry at a time.
VICIdial keeps dialing, lists and reporting; VoiceOI handles the conversation.
| Area | Stays in VICIdial | VoiceOI |
|---|---|---|
| Campaigns and lists | Campaigns, lists, lead loading and the hopper | Works the campaigns you assign bots to |
| Dialing | Dial method, caller ID, call times and recycling | No change; bots take the answered calls |
| Agent seats | Bot remote-agent entries next to your human agents | Creates the bot remote agents in bulk |
| The conversation | Not involved | Answering-machine detection, do-not-call handling, optional AI-voice disclosure, qualification |
| Call results | Dispositions in your reports | Writes call outcomes back as dispositions |
| Transfers | Closers take the call, for example through an in-group | Hands the live call over SIP, with AI comments on the Good Fronter tiers |
| Call records | VICIdial's own logs and reports | Recordings, transcripts and call logs |
| Call data export | Not involved | Google Sheets rows on the Pro LG tiers; CRM integrations coming soon |
The outcome of each bot call is written back as a VICIdial status, so your reports show it and recycling rules can act on it. You pick the status each outcome writes; for an AI agent, each exit maps to one.
| Call outcome | Status written to VICIdial | Set by |
|---|---|---|
| Answering machine detected | AM | Automatically |
| Do-not-call request | DNC | Automatically |
| Qualified and transferred | XFER, or the status you set on the transfer step | Your script |
| Not interested, callback and other outcomes | The status you map, for example NI or CALLBK | Your script |
Use statuses that exist in your VICIdial campaign. A status the campaign doesn't recognize is dropped, so add custom statuses in VICIdial before you map them.
Answering-machine detection ends the call and writes the AM status. When the person says a phrase from your do-not-call list, the bot ends the call and the DNC status is written. Both phrase lists are editable per organization and can be imported and exported. More on answering machine detection for call centers.
When a lead qualifies, a Fronter or Closer tier bot transfers the live call over SIP to your closers, for example through the in-group from step 5, and closer routing rules decide where it goes. The bot hands the call over and does not stay on the line to introduce the caller.
Closer comments. The Good Fronter tiers leave AI-written comments, so the closer sees what the lead already said.
Closers on another VICIdial. The target-closer integration connects through that system's VICIdial API and passes details the bot collected, such as the lead's age, to the closer dialer.
Lead generation tiers. LG bots collect answers but don't include live transfers.
More on how AI live transfer works.
To keep the bot's answers in a spreadsheet as well as the disposition in VICIdial, add a Google Sheets step to the script: each call that reaches it appends a row. Sheets export comes with the Pro LG tiers and writes to a sheet without importing leads from one. CRM integrations are coming soon, and there is no public API or outbound webhook today. See the Google Sheets integration.
Check that the bot remote agents are on the campaign you're dialing and that your firewall allows traffic between VICIdial and VoiceOI's servers.
Check that the closers' in-group is allowed in the campaign and has closers logged in and ready.
Check the allowed IPs on both sides, then place another test call.
Check whether the status exists in the campaign. If it does not, add it in VICIdial or map the outcome to one that does.
Check the transcript, then add the greeting's wording to your machine phrase list.
VICIdial bot tiers list from $25 to $135 per bot per month, prepaid, with discounts of up to 60% and no per-minute AI fee. Tier-by-tier prices are on the VICIdial AI voice bot and VoiceOI pricing pages. Wondering what VICIdial itself costs to run? See how much VICIdial costs, and how it relates to ViciBox, GoAutoDial and FreePBX in our open-source dialer comparison.
Talk to our team about your VICIdial setup, or sign up and build your first bot in the no-code builder.
Common questions about connecting AI agents to a VICIdial floor.
VoiceOI talks to VICIdial through VICIdial's own API, with the server address and API login you add once, so there's no code to write. The target-closer integration uses the API of your closers' VICIdial. VoiceOI has no public API of its own.
Any SIP carrier works, including Twilio and Telnyx SIP trunks. You add it in VoiceOI's Carrier Manager by pasting the sip.conf or pjsip.conf block your VICIdial carrier uses.
Not yet; CRM integrations are coming soon. Today, results go back to VICIdial as dispositions, and Pro LG tiers can add a Google Sheets row per call.
No. The bots take answered calls from outbound VICIdial campaigns and don't answer inbound calls. The in-group in the setup only receives the transfers bots send to closers.
In VICIdial terms, it is software that fills an agent seat instead of a person. VoiceOI's version covers the first-contact call as a remote agent and leaves the closing to your human team.