What does a VICIdial Salesforce integration do?
A VICIdial Salesforce integration lets agents work calls in the VICIdial agent screen while Salesforce stays the record of who was called, when, and what happened.
VICIdial is an open-source predictive dialer built on Asterisk, and Salesforce knows nothing about it until something joins the two. VICIfast runs managed VICIdial servers and builds that link as a scoped project; the patterns every CRM shares are on VICIdial CRM integration.
Salesforce has its own vocabulary, and the first job is deciding which of these records the dialer touches:
| Salesforce record | What it is | What the integration does with it |
|---|---|---|
| Lead | A prospect nobody has qualified yet | Loaded into a VICIdial list and dialed |
| Contact and Account | A person and the company they belong to | Dialed, or matched when that person calls in |
| Campaign and Campaign Member | A named group of Leads and Contacts | A tidy way to choose who goes to the dialer |
| Task | A logged activity, such as a completed call | Written after each call with the disposition, agent and time |
| Opportunity | A deal in progress | Usually left alone, or updated by a disposition you pick |
One Salesforce habit shapes most builds: converting a Lead creates a Contact and an Account, so the same phone number can sit on more than one record. Deciding which record wins is the first design question.
Which way does data move between VICIdial and Salesforce?
Data moves both ways; most call centers want three or four of these flows:
- Records in. A sync picks Leads or Contacts by Campaign, owner or Lead Status, checks them against what VICIdial already holds, and loads them into a list with the Salesforce record ID attached.
- Screen-pop. When a call connects, the agent's browser opens the Salesforce record. Outbound, the record ID travels with the lead. Inbound, the build searches Leads and Contacts for the caller's number first.
- Outcomes back. Each disposition is logged on the record as a completed call Task, and can also update the Lead Status, so a "do not call" said on the phone reaches Salesforce.
- Click-to-dial. A button on the record asks VICIdial's agent API to place the call for an agent signed in to the VICIdial agent screen.
What can VICIdial do with Salesforce before any custom code?
VICIdial can already open a Salesforce page for each call and announce each outcome, using settings in the campaign.
The campaign web form is a URL filled in with the lead's fields, and setting Get Call Launch to that web form opens it as the call reaches the agent. If the lead's vendor lead code holds the Salesforce record ID, the URL lands on the record itself. The Dispo Call URL is requested every time an agent saves a disposition, and the non-agent API lets a script on your side add or update leads. Our VICIdial API and AGI overview explains each one.
What VICIdial cannot do alone is talk to Salesforce's API. A plain URL request cannot sign in to Salesforce, refresh a token, respect your org's daily API allowance or retry when Salesforce is busy, so a small service has to sit between them. That service, plus the record matching and field mapping, is the custom part.
What does a Salesforce build cost, and what sets the price?
Every VICIfast build is fixed-fee, and for Salesforce the price depends mostly on how much of your org the integration has to understand.
The things that move a Salesforce quote:
- How many objects are involved. Leads alone are simpler than Leads, Contacts, Accounts and Opportunities together.
- Custom fields and validation rules. A required field or a validation rule can reject a write the sync expected to work, so each one needs a decision.
- Duplicate rules. Your org's matching and duplicate rules can block an insert, and the integration has to handle that cleanly.
- API access and limits. Not every Salesforce edition includes API access by default, and every org has a daily API request allowance the sync must stay inside.
VICIfast publishes its ranges. Logging each disposition as a Task is the simple-webhook kind of job, listed at $1,500-$3,000. Two-way sync with deduplication, field mapping and a TCPA scrub is listed at $5,000-$12,000. Screen-pop and click-to-dial are quoted after discovery. We have built Salesforce integrations before, always the same way: a written quote within 48 hours of the discovery call, a build tested in a Salesforce sandbox on your side, usually 1-3 weeks of work, then a 30-day warranty. Full terms are on custom integrations.
Who is a VICIdial Salesforce integration for?
It suits call centers that already run sales in Salesforce and need more conversations per hour than reps clicking one number at a time can manage, as in B2B sales teams, insurance and financial services. Teams on HubSpot should read the VICIdial HubSpot integration page.
Where VICIfast is not the right fit
We do not sell an AppExchange app; every Salesforce integration is a project scoped to your org. If a handful of reps make a few dozen calls a day, a dialer that runs inside Salesforce may suit you better than a predictive dialer beside it. VICIfast is not affiliated with or endorsed by Salesforce; we build against Salesforce's published APIs.
Where to start
Write down which Salesforce objects you dial from, what an agent should see when a call connects and what should be written back, then book a discovery call; we will sign an NDA first if you need one. To try VICIdial itself, start a free trial. Hosting is per server, not per agent, from $49 a month on shared cores; every plan is on pricing.