Bridgeside AI
← All posts

Running a VICIdial AI Agent, Questions and Answers for Dialer Admins

What changes and what stays the same when you put an AI agent on VICIdial, from campaign routing, call menus and DIDs to closers, recordings, reports, a pilot plan and rollback.

You already run VICIdial. Your lists, campaigns, carriers, in-groups and reports are tuned, and nobody wants to move them. The good news is that a VICIdial AI agent does not ask you to. It is one more destination your dialer can send a call to, and the rest of the system keeps working the way it does today.

This guide is written as the questions VICIdial admins actually ask before they connect an AI voice agent to VICIdial. It assumes you know your way around Admin, Campaigns, Inbound and Users. The step by step setup lives in how to add an AI voice agent to VICIdial; this page covers the decisions around it.

What a VICIdial AI agent changes, and what it does not

What changes on the dialer:

  • One Custom Dialplan Entry (Admin > Servers > your server) that sends any call to 85 plus a three-digit dial code to the matching Bridgeside AI campaign.
  • One new block in /etc/asterisk/manager.conf: an AMI user that can only connect from Bridgeside's address and is used for the hangup event, Hangup and Redirect.
  • One new VICIdial user for the non-agent API, level 8 or higher with Modify Leads, so the AI can write the status, a two-line summary and DNC requests.
  • A firewall rule allowing AMI (TCP 5038) from Bridgeside's address only.

What does not change: your carriers and SIP trunks, campaign caller IDs, lists and hopper, lead recycling, call times, DNC settings, closers, in-groups, agent screens and recording storage. The AI is not a VICIdial user and does not log in to the agent screen.

How do outbound campaigns reach the agent?

On an auto-dialed campaign, answered calls normally go to the campaign's routing extension, which hands them to a logged-in agent. To send them to the AI instead, the routing extension points at 85 plus the campaign's dial code, for example 85001. Alternatively you can route to a Call Menu that dials that extension, which is handy if you want an option to reach a person first.

Two things to know:

  • The lead id travels in the caller ID name. On auto-dialed calls VICIdial sets the caller ID name to a string that begins with V and ends with the lead id. The generated dialplan passes it to Bridgeside, which reads the lead id from it. Do not rewrite CALLERID(name) in any dialplan the call passes through before it reaches the 85 extension.
  • Pacing is still VICIdial's job. Ratio and adaptive dialing size the number of lines from the agents logged in to the campaign. Before loading a real list, run a test campaign with the routing extension pointed at the AI and watch the real-time report to confirm how many calls your version places and how fast.

How do inbound DIDs and call menus reach it?

For inbound, go to Admin > Inbound > DIDs and route the DID to extension 85<code>. In a Call Menu, add an option whose route is that extension. The AI answers with the campaign's greeting, which can say up front that the caller is speaking with an automated assistant.

Inbound calls do not carry VICIdial's lead id in the caller ID name, so Bridgeside falls back to the caller's number and asks VICIdial to find the lead by phone number across the system. If the caller is not already a lead, there is nothing to update; the call still appears on Bridgeside's Calls page with its transcript, and the campaign webhook can send the result to your CRM.

What happens when the AI transfers to closers and in-groups?

The AI transfers by redirecting the live call over AMI, so the caller never hangs up and is never redialed. For VICIdial the clean target is a DID routed to the in-group that should take the call, reached through the trunkinbound context. Set that DID's in-group call handle method to look up the existing lead by caller ID (CIDLOOKUP or one of its variants), so the closer's screen pops the lead the AI was talking to instead of creating a new one.

On the campaign's Transfer tab you enter that DID (or an extension) and, if needed, a context; blank uses the dialer's default. The script decides when to transfer, for example only after every qualifying question is answered and the caller agrees to speak with someone. If you want the closer to see what was said, the campaign webhook's call.transferred event carries the transcript so far. For more on the handoff itself, see warm and blind transfers for AI calls.

The closer then dispositions the call as usual, and the status they choose becomes the lead's latest status.

What about recordings?

Bridgeside AI does not store call audio. Recordings stay on your dialer, and Bridgeside keeps a transcript of each call for the retention period your organization picks, from 1 to 90 days, then redacts or deletes it.

Check how your recordings are triggered. VICIdial's campaign recording usually starts when a call reaches an agent session, and a call routed straight to an extension may never get there. Make one test call and look for the file. If none was made, you can start a recording in the dialplan before the bridge, for example:

exten => _85XXX,1,Answer()
  same => n,MixMonitor(ai-${UNIQUEID}.wav)
  ; the rest of the generated entry follows unchanged

Where you store and name those files is your choice; keep them with your other recordings so QA finds them in one place.

What shows up in reports?

After each call, Bridgeside classifies the transcript into one of the campaign's disposition codes and writes it to the lead through the non-agent API, with a two-line summary in the comments. Your status and list reports count AI calls in the same schema as human calls. Create the statuses first (six characters at most). The default set is SALE, NI, APPT, CALLBK, DNC and DROP, and you can rename or add codes on the campaign's Dispositions tab. The VICIdial non agent API guide explains the user, the calls and the error messages.

Because the AI is not a VICIdial agent, it will not appear in agent performance reports. Bridgeside's own dashboard shows calls, transfers, hangups and appointments per dialer and per campaign.

A one-campaign pilot plan

  1. Pick one campaign with a short, repeatable script and a clear transfer rule. Low stakes beats high volume.
  2. Connect the dialer. Register it on the portal's Dialers page, paste the generated dialplan, reload, and click Test API to see your VICIdial version returned.
  3. Test by phone. Call 85<code> from a registered phone. Ask a question from the FAQ, ask whether it is a robot, ask to be transferred, and on a test lead ask not to be called again. Confirm the transfer lands, the status is written and the number appears in your DNC list.
  4. Route a small slice. Point the pilot campaign's routing extension, or one DID, at the AI and keep the dial level conservative.
  5. Listen for a day. Read the transcripts, listen to the recordings, and tune the greeting, questions and FAQs on the portal. Script changes take effect on the next call; nothing on the dialer changes.
  6. Decide. Compare transfers and dispositions with the same campaign handled by people, then widen it or stop.

How do you roll back?

Point the campaign's routing extension, DID or Call Menu option back where it was. That is the whole rollback, and it takes effect on the next call. The dialplan entry does nothing unless a call is sent to an 85 extension, so it can stay. If you are leaving for good, remove it, delete the [bridgeside] block from manager.conf and reload, and disable the API user.

FAQ

How do I add an AI voice agent on top of my VICIdial dialer without switching platforms?

Add one Custom Dialplan Entry that bridges calls to the AI, an AMI user for hangups and transfers, and a non-agent API user for results. Then route a campaign's answered calls, a DID or a Call Menu option to 85 plus the campaign's dial code. Your carriers, lists and agents stay as they are.

How do I connect an AI voice agent to VICIdial?

Register the dialer on the Bridgeside portal with its address, AMI user and API user, paste the generated dialplan into Admin > Servers > Custom Dialplan Entry and reload. Allow AMI only from Bridgeside's address. It takes about 20 minutes, and the VICIdial integration page has the overview.

Do I need a separate VICIdial AI agent for each campaign?

No. One dialplan entry serves every campaign. Each Bridgeside campaign has its own dial code, script, voice and transfer target, so 85001 and 85002 can be completely different agents.

Will the closer see the lead the AI qualified?

Yes, if the transfer target is a DID routed to the closer in-group with a call handle method that looks up the existing lead by caller ID. The caller stays on the same call throughout.

Can AI and human agents work the same campaign?

The cleanest setup gives the AI its own campaign or DID and keeps humans as the transfer destination. That keeps reports readable and makes rollback a single change.

What does it cost to try?

The trial gives 60 free minutes with no card. After that, pay as you go has no monthly fee, and 10 channels start at $49 a month; see the pricing page. Start at app.bridgeside.ai.

Put an AI agent on your dialer

60 free minutes, no card, one dialplan entry.