Integrations · VICIdial

AI voice on your VICIdial floor — without touching your server.

Revolv attaches to VICIdial as a SIP destination. Your dialer keeps dialing, pacing, and recording exactly as it does today; answered calls route to an AI fronter that discloses, qualifies, and warm-transfers to your closers. Nothing gets installed, and nothing about your campaigns has to change.

SIP destination · zero installs · fronter-only
The architecture

Your dialer keeps dialing. The AI answers.

VICIdial already does the hard telephony: list management, lead recycling, pacing, answering-machine detection, recording, and the reports your floor runs on. An AI integration that asks you to replace any of that is solving the wrong problem. Revolv leaves the dialer alone — we hand you a SIP destination, and your admin points a campaign at it. It's the same routing move you'd make to send calls to a remote closer floor, and it's exactly as reversible.

From there the call flow is short. VICIdial dials your lists at your pacing. When someone answers, the call bridges over SIP to a Revolv fronter, which greets, discloses that it's an AI assistant, and asks the one or two qualifying questions your script defines. Qualified prospects warm-transfer to your human closers — the fronter gives the closer a short spoken brief before connecting, so the caller never repeats themselves. Everyone else gets a polite exit and an accurate disposition. Calls ride your existing trunks the whole way: your carrier, your numbers, your caller IDs.

Software installed on your server

None. No AGI scripts, no patches, no database access, no custom dialplan.

Carrier, trunks & caller IDs

Unchanged — calls leave on your trunks under your numbers, like every other call.

Campaign logic

Yours. Lists, filters, recycling, pacing, and dial levels all stay in VICIdial.

What you add

One routing target: point the campaign or in-group at the SIP destination we provision.

The model

A fronter, not a sales bot.

Revolv agents on VICIdial are deliberately scoped to the front of the call: greet, disclose, qualify with a question or two, transfer. The close stays human. That's not a limitation we apologize for — it's the one AI pattern that consistently holds up on a real outbound floor, and the only one experienced VICIdial operators tend to take seriously. A long, improvising AI sales conversation sounds impressive in a demo and bleeds conversion at volume; a disciplined fronter does one job on every connect and hands the judgment work to people.

The economics are the argument. A fronter spends human time only on conversations that survived qualification: your closers stop burning their shift on "hello, who is this?" and spend it on prospects who already said yes twice. The dialer's job doesn't change — connects in. The floor's job gets better — qualified transfers out.

Rollout

Live in under a day, typically.

1. Scope it (30 minutes) Your campaign, your script, your transfer targets, your AMD posture. We map the exact fit before anything is configured.
2. Point a campaign at the SIP destination We provision the fronter and hand your admin a SIP destination. One routing change in VICIdial — the same move as routing to a remote closer floor.
3. Test calls You dial the line and hear the disclosure, the qualifying questions, and the exit paths. Wording gets tuned with you, on the call.
4. Verify transfer & write-back A warm transfer lands on a real closer with the spoken brief, and the disposition, recording, and transcript land in your reports. End to end, before go-live.
5. Go live, ramped Start with a slice of one campaign, watch the numbers together, widen as they hold.

Onboarding typically completes inside a working day, because there's nothing to install and nothing to migrate. The self-serve runway — what to have ready, what happens when — lives at onboarding.revolv.cx.

Prefer the short version first? The 5-minute overview is in our SIP bridge guide.

AMD

Answering-machine detection: two honest postures.

AMD is where dialer-AI integrations quietly fail, so we're explicit about it. Two postures work. Posture one — our default recommendation: turn dialer AMD off for the AI campaign and let the fronter screen every connect. The agent hears the line the way a human agent would: a person gets the conversation, a voicemail greeting gets a hangup (or your approved message) and an accurate machine disposition. You spend a few seconds of AI time per machine, and in exchange you retire AMD's oldest failure mode — hanging up on live humans it misread.

Posture two: keep VICIdial's AMD and pass its verdict downstream — the dialer forwards the result in a SIP header (X-AMD-Status), so the fronter knows what the dialer concluded and handles the call accordingly. This preserves your current dial economics; it also preserves AMD's error rate. Both are supported, and we'll tell you plainly which one fits your list quality before you commit to either.

Write-back

Your reports stay whole.

A fronter that swallows outcomes breaks the floor's feedback loop. Every Revolv call writes back the four things your operation runs on: the disposition, the call recording, the full transcript, and the per-call cost. Outcomes flow over standard rails — VICIdial's own APIs and your CRM's — so list recycling, campaign stats, and client reporting keep working from the same data they do today. Transparent per-call cost also means you can audit the spend line by line, not trust a monthly invoice.

Compliance

Enables compliance. Doesn't replace it.

AI disclosure ships on by default: the fronter identifies itself as an AI assistant at the top of every call. The wording is configurable with your counsel — weakening it is a deliberate choice, never a silent default.

The division of responsibility is the honest one: you own your telephony, your lists, your consent capture, and your calling hours — Revolv is a tool in your stack, not your compliance department. What the platform does is make compliant behavior structural: disclosures that can't be skipped, opt-outs honored the moment they're spoken, and a recording plus transcript that prove what was said on every call. Under the TCPA, AI voice is "artificial or prerecorded voice," which makes consent-first the only workable posture — your counsel sets that policy, and the rails enforce it. The platform-wide picture is on our compliance page; the regulatory detail is in the TCPA & AI voice guide.

Economics

Priced the way the dialer thinks.

Pricing is per-minute, from $0.13/min of connected talk — no seats, no licenses, no per-agent fees. A machine screened in seconds costs cents; spend follows conversation, which is the same logic your pacing already optimizes for. For the framework against seat economics, see cost per connected minute.

Questions

What VICIdial operators ask us.

Does anything get installed on my VICIdial server?

No. The integration is a SIP destination your campaign points at — no AGI scripts, no patches, no database access, no dialplan surgery. Your admin makes one routing change, and it is exactly as reversible as any other routing change.

Does the AI replace VICIdial?

No. VICIdial keeps doing what it is good at — list management, lead recycling, pacing, AMD if you use it, recording, reporting. Revolv only answers the calls your dialer connects, qualifies them, and transfers the good ones to your people.

How do answered calls reach the AI agent?

Your campaign or in-group routes to the SIP destination we provision, the same mechanism you would use to send calls to a remote agent floor. Calls travel over your existing trunks; your carrier, your numbers, and your caller IDs stay yours.

Should I leave VICIdial’s AMD on?

For AI campaigns we usually recommend turning it off and letting the fronter screen every connect — humans never get hung up on by a false positive. If your dial economics depend on dialer-side AMD, keep it and pass the verdict to the bot in a SIP header (X-AMD-Status). Both postures are supported.

How do dispositions and recordings get back into my reports?

Full write-back on every call: the disposition, the call recording, the complete transcript, and the per-call cost, delivered over standard APIs into VICIdial and/or your CRM. List recycling and client reporting keep working from the same data they do today.

Will the AI tell people it’s an AI?

Yes. AI disclosure ships on by default — the fronter identifies itself as an AI assistant at the top of the call. The wording is configurable with your counsel; weakening it is a deliberate choice, never a silent default.

Who is responsible for TCPA compliance?

You are — your lists, your consent capture, your calling hours, with your counsel setting policy. Revolv enables compliance rather than ensuring it: disclosures that cannot be skipped, opt-outs honored the moment they are spoken, and recordings that prove what was said.

What does it cost?

Per-minute pricing from $0.13/min, metered on connected talk — no seats, no licenses, no per-agent fees. A machine screened in seconds costs cents; spend follows conversation.

How long does setup take?

Typically under a day from scope call to first live calls, because nothing has to be installed or migrated. The self-serve runway lives at onboarding.revolv.cx.

Can I hear it before talking to anyone?

Yes — call the live demo line at +1 (646) 965-8504 and a Revolv agent answers. Same engine, same disclosure, same transfer behavior your prospects would hear.

Hear it

Call the line before you book anything.

The fastest way to judge an AI fronter is to be its prospect. The demo line runs the same engine, the same disclosure, and the same transfer behavior your callers would hear.

See it on your VICIdial.

A 20-minute walkthrough on your campaigns, your transfer targets, and your compliance posture — hard questions first.