Manually logging every sales call into Salesforce after you hang up wastes time and guarantees some calls never get recorded at all. Connect your VoIP phone system to Salesforce once and every call, voicemail, and click-to-dial action logs itself against the right contact record automatically.

Why this matters

A sales or support team fielding 40-60 calls a day loses real hours to manual data entry if nothing writes call activity back to Salesforce. Once you connect your VoIP phone system to Salesforce, inbound calls trigger a screen pop with the contact's record already open, and outbound calls log as Tasks the moment you hang up. For a business running lead follow-up through Salesforce in 2026, that's the difference between a rep who calls a lead twice by accident and one who sees the full history before dialing.

The setup itself isn't complicated, but it breaks in predictable spots. Picking the right VoIP provider before you start the Salesforce connection saves a second round of configuration later — not every cloud phone platform ships a native Salesforce connector, and the ones that don't require a manually imported CTI adapter instead.

Before you start

• Salesforce System Administrator access — you need permission to install packages, create Connected Apps, and edit page layouts under Setup.
• Admin access to your VoIP platform's portal — most cloud phone systems gate integrations behind an Owner or Admin role, not a standard user login.
• The gotcha that breaks screen pops: Salesforce matches inbound calls to contact records by comparing phone number strings exactly. If your VoIP system passes a plain 10-digit number and Salesforce stores numbers in E.164 format with a +1 country code, the match fails silently and no screen pop fires. Normalize the number format on both sides before you test anything else.

Set up your VoIP-side connector

1. Log into your VoIP system's admin portal and open the Integrations or App Marketplace section.
2. Search for Salesforce and click Connect or Install.
3. You'll be redirected to a Salesforce login screen — authenticate with an admin account and click Allow on the OAuth permissions prompt.
4. Back in Salesforce, go to Setup > App Manager and confirm the new entry shows a status of Installed or Enabled.

Expected result: the Connected App appears in App Manager, and your VoIP admin portal shows a connected status next to Salesforce.

Configure Salesforce for call activity

1. From Setup, type Call Center into the Quick Find box and open Call Centers.
2. Click Import and upload the CTI adapter XML file provided by your VoIP platform — this comes from their integration documentation, not from Salesforce.
3. Open the new Call Center record, click Manage Call Center Users, then Add More Users to assign every rep who needs the softphone.
4. Under Object Manager > Task > Fields & Relationships, confirm a Call Duration or equivalent field exists. Most connectors create this on install, but check before go-live.

Expected result: reps assigned to the Call Center see a softphone widget in the Salesforce utility bar the next time they log in.

Map call fields and enable click-to-dial

1. Open Lightning App Builder from Setup and edit the Lead, Contact, and Account pages you want click-to-dial on.
2. Drag the Open CTI Softphone or vendor-specific phone component onto the layout, next to the phone number field.
3. Save and activate the page for the relevant record types.
4. Place a test outbound call from a Contact record's phone field and confirm a Task record is created with Call Type, Duration, and Subject populated.

Expected result: clicking a phone number on any mapped record opens the softphone and dials automatically, and the call logs as a Task within seconds of hanging up.

The verdict: DBSI recommends configuring automatic call logging first and click-to-dial second — logging captures every call regardless of device, while click-to-dial only helps reps who dial from inside Salesforce.

Variant: log calls automatically without click-to-dial

Some teams don't want click-to-dial. They just want every call on the phone system to appear in Salesforce without a rep touching a button. This works the same way through the first two configuration units above, but you skip the page layout changes and instead enable automatic call logging in the CTI adapter's settings panel, usually labeled Auto-Log Calls or Background Logging.

This variant matters most for remote and hybrid teams using softphone apps on laptops rather than desk phones. There's no shared office phone system to standardize click-to-dial across, so automatic logging catches every call regardless of device.

Troubleshooting

• Screen pop doesn't fire on inbound calls. Almost always a number format mismatch — check that both systems use E.164 with the country code, not a mix of formats.
• Calls aren't logging as Tasks at all. The rep's user profile likely lacks Create permission on the Task object, or the Call Center user assignment was skipped for that user.
• Click-to-dial button is missing from the page. The Lightning page wasn't activated for that record type after the component was added — reopen App Builder and check activation status.
• Duplicate call records appear for a single call. This traces back to webhook retry settings on the VoIP side. If the platform re-sends a call event after a slow Salesforce response, you get two Tasks. Extend the timeout window in the connector's advanced settings rather than disabling retries.
• Softphone widget loads but won't authenticate. The OAuth token has usually expired — disconnect and reconnect the integration from the VoIP admin portal.

Customize your workflow

Once calls, Tasks, and click-to-dial are working, there's more to configure depending on how the business runs in 2026. Route inbound calls by territory so a Salesforce Lead's assigned owner rings first instead of a general queue. Pass the IVR selection — the digit a caller pressed — into the call record as a custom field so reps see intent before they answer.

Businesses running phones across more than one office should also check how routing and logging behave for multi-location VoIP setups. The connector configuration is identical, but number-to-location mapping adds a layer that single-office guides skip entirely.

One more piece worth handling before you scale the integration: the cabling underneath it. A Salesforce-connected phone system inherits every weakness in the physical network, and call quality problems get blamed on the CRM integration far more often than they deserve.

FAQ

One last thing

The phone number format mismatch isn't a rare edge case — it's the top reason a Salesforce-VoIP integration looks completely broken minutes after a clean install in 2026. Fix formatting on both systems before touching anything else in the connector, and the rest of the connection usually works on the first try. DBSI handles this step during business phone system installs so reps never see a dead screen pop on day one.

Related guides

• Network cabling for VoIP phone systems
• How to reduce phone system downtime for a growing business
• How to switch from a landline to a VoIP phone system