Connect Salesforce CRM with Phone System (CTI Integration)
Step-by-step administrator setup guide for connecting Salesforce CRM with Phone System CTI integration.
-
OSS/BSS Answers
Access Control Security Hub Admin Audit B3Network Master Account Channel App Contract App Customer App Discount App Edge Server File Management Finance App Invoice App Number Management Payment Portal Settings Price List Product App Release V2 SMS Gateway Supplier App Support Center Support Hub Business Hub Sales Hub Finance Hub
- App Model - Organization Management
- App Model - Communication Apps Answers
- License Model - Organization Management
-
License Model - CPaaS Solution Answers
Phone System - Admin Guide Phone System - End-user Guide Mobile App Desktop App Web Phone Omni-Channel Auto Attendant - Admin Guide Developer Hub - Admin Guide Microsoft Teams Operator Connect - Admin Guide Microsoft Teams Direct Routing - Admin Guide Contact Center - Supervisor Guide Contact Center - Agent Guide SIP Trunk CPaaS - SIP Trunk Power SIP Trunk CPaaS Fax CPaaS Hotdesking Contact Campaign File Explorer Power Mobile App Files App Campaign App Data Compliance
- Telcoflow
- Integrations Answers
- Updated Regulations
- Ideas Portal
Table of Contents
Connect Salesforce CRM with Phone System (CTI Integration)
Integrate your Salesforce CRM account directly with Phone System to enable click-to-dial, inbound caller identification, and automatic call logging within Salesforce. Administrators can configure the connection entirely through self-service settings without opening a technical support ticket.
Availability & Prerequisites
| Requirement | Specification |
|---|---|
| Base License | Active Phone System license |
| Role Required | Admin or Owner |
| Supported Browser | Google Chrome (newest version) |
| Salesforce Permissions | System Administrator access to configure Connected Apps or External Client Apps |
Self-Service Setup
Salesforce integration is managed self-serve from the portal. Credentials can be activated, updated, or removed at any time directly from the CTI Integration menu.
Step 1: Obtain OAuth Credentials in Salesforce
Before connecting Salesforce in the portal, generate a Consumer Key (Client ID) and Consumer Secret (Client Secret) in your Salesforce organization.
- Log in to Salesforce as a System Administrator.
- Navigate to Setup (gear icon) > Apps > External Client Apps > External Client App Manager.
- Click New External Client App.
- Configure the required application fields:
-
Distribution State: Set to
Local. - OAuth Settings: Check Enable OAuth Settings.
-
Callback URL: Enter the OAuth callback URL provided on your portal integration card (format:
https://<your-portal-domain>/_a/cti/public/v1/oauth/callback). -
Selected OAuth Scopes: Add
api(Manage user data via APIs). - Client Credentials Flow: Check Enable Client Credentials Flow.
- Web Server Flow: Check Require secret for Web/Refresh Token Flow.
- PKCE: Ensure Require Proof Key for Code Exchange (PKCE) is disabled.
- Click Create (or Save).
- In the External Client App Manager list, locate your newly created app, click the dropdown menu, and select Edit Policies:
- Under OAuth Policies, check Enable Client Credentials Flow.
- Set the Run As field to the designated administrator username.
- Under Refresh Token Policy, select Refresh token is valid until revoked.
- Click Save.
- Locate your app again, click Edit Settings, and expand the OAuth Settings tab.
- Click Consumer Key and Secret. When prompted, verify the one-time passcode (OTP) sent to your administrator email address.
- Copy both the Consumer Key and Consumer Secret to a secure note.
Step 2: Connect Salesforce in the Portal
Once you have your Salesforce credentials, configure the connection in Phone System:
- Log in to your account on the portal.
- Navigate to Phone System > CTI Integration.
- In the Available Integrations grid, locate the Salesforce card and click Connect.
- In the Connect Salesforce dialog, complete the three connection fields:
-
Domain: Enter your Salesforce subdomain. The fixed suffix
.my.salesforce.comis automatically appended. -
Standard Production Org: Enter your company subdomain (e.g. enter
mycompanyformycompany.my.salesforce.com). -
Sandbox Org: Enter your multi-segment subdomain with dots (e.g.
orgfarm-d76fb33812-dev-ed.develop). - Client ID (Consumer Key): Paste the Consumer Key generated in Step 1.
- Client Secret (Consumer Secret): Paste the Consumer Secret generated in Step 1.
- Click the eye icon beside either credential field if you need to visually verify the input before saving.
- Click Connect.

- To disconnect, click the connected card and select Deactivate.
Credential Security & Masking
After saving, all confidential fields (Client ID, Client Secret) are securely hashed and displayed in masked format (•••• •••• •••• XXXX). Raw credentials are never exposed in plain text within the portal interface.
Step 3: Configure User Extensions for CTI Calling
To allow members to place and receive calls through the CTI widget, enable CTI on their extension settings:
Enable Inbound Calls in CTI
- Navigate to Phone System > Extension Settings.
- Open the Devices section.
- Check the CTI option.
- Click Save.
Configure Outbound Caller ID
- On the same extension edit page, open the Outbound Call section.
- Select the preferred Caller ID to be displayed when placing outbound calls from Salesforce.
- Click Save.
Managing Your Salesforce Connection
Deactivate the Integration
To temporarily suspend call logging and click-to-dial without removing credentials:
- Navigate to Phone System > CTI Integration.
- On the active Salesforce card, click Deactivate.

- The status chip transitions to Inactive. Click Activate at any time to resume calling integration.

Delete the Integration
To permanently disconnect Salesforce and purge saved credentials:
- Navigate to Phone System > CTI Integration.
- On the Salesforce card, click Delete.
- In the confirmation dialog, type
CONFIRMin the verification box to prevent accidental removal. - Click Delete.

Disconnection Warning
Deleting the integration permanently invalidates active session tokens. User extensions assigned to CTI will fall back to their primary registered device (Web Phone or IP phone) for incoming and outgoing calls.