Want to work smarter with AI? See how Agentforce fits your business.
Connecting IVR and telephony to Salesforce so agents see the caller’s record instantly is usually a standard integration, not a custom build. Most modern contact center platforms offer a Salesforce connector, and Salesforce provides Service Cloud Voice and the Open CTI framework for this purpose. These add a softphone inside Salesforce and a screen pop that opens the matching record when a call arrives. Custom work comes in when your phone system has no supported connector, your IVR collects data that must drive specific lookups or your matching and routing rules go beyond what the connector supports.
Your Integration Options
| Option | How It Works | Best For | Effort |
|---|---|---|---|
| Service Cloud Voice | Telephony built into Service Cloud, with Amazon Connect or supported partner telephony providers | Teams that want calls, transcripts and cases in one Salesforce experience | Configuration-led, low to moderate |
| Third-party CTI connector | A managed package from your contact center provider, built on Open CTI | Teams already using a cloud contact center platform | Configuration-led, low to moderate |
| Custom Open CTI build | Developers use the Open CTI JavaScript API to connect a phone system without a ready connector | Legacy or in-house phone systems, unusual workflows | Custom development, moderate to high |
CTI, or computer telephony integration, simply means linking your phone system with Salesforce so calls, caller details and call activity are handled inside the CRM rather than on a separate screen.
How Screen Pop Works
- A call arrives and the phone system passes the caller’s number, plus any data collected by the IVR such as an account or case number.
- Salesforce searches for a matching contact, account, lead or case.
- Based on the screen pop rules you configure, the softphone opens the single match, shows a list when there are several or offers to create a new record when there is none.
- The call is logged as an activity against the record, often with duration, disposition and a recording link.
Using IVR-collected identifiers such as an account number gives more accurate matches than phone number alone, especially when several contacts share a number.
When It Becomes a Custom Build
- Your phone system or IVR has no supported Salesforce connector.
- IVR data needs to trigger lookups against custom objects or external systems.
- Matching rules depend on complex logic, such as priority customers or multiple brands.
- You need custom routing based on Salesforce data, beyond what the connector offers.
- Call data must sync to other systems as well as Salesforce.
What Affects Effort
Effort depends mostly on whether a supported connector exists, how clean your contact data is and how much custom logic the screen pop and routing need. Clean phone numbers and unique identifiers make matching reliable. Plan for agent training, testing with real call scenarios and a short period of tuning after launch.
Folio3’s Approach
CTI integration is part of Folio3’s Salesforce integration services, linking phone systems to Salesforce to log calls and route leads. For contact center teams, Folio3 also offers Salesforce Service Cloud consulting to align case management, routing and agent workflows with the telephony setup.
People Also Ask
- What is Salesforce CTI integration?
- How does screen pop work in Salesforce?
- Should you use Service Cloud Voice or a third-party CTI connector?
- Is Salesforce telephony integration standard or custom?
- We want to integrate IVR/telephony with Salesforce so agents see the caller record instantly. Is that a standard integration or a custom build?
Want agents to see the right customer record the moment a call arrives? Talk to Folio3 about Salesforce CTI integration and Service Cloud setup.
