Picking a Connector is mostly about phone vendor relationships and feature depth. Installation is a standard AppExchange package install plus tenant configuration.
- Identify your telephony platform and supported Connectors
List the phone vendors that have Salesforce Connectors. Most major ones do. If your phone vendor is not on the list, evaluate switching or building a custom Connector.
- Pilot in sandbox
Install the vendor Connector in a sandbox. Walk through the included setup wizard. Test core flows: inbound call screen pop, outbound click-to-dial, call log to Voice Call or Task.
- Verify feature coverage
Compare the Connector features to your business requirements: skills-based routing, call recording, real-time agent monitoring, conversation analytics. Some Connectors are surface-level; others go deep.
- Compare to Service Cloud Voice
For any new deployment, do a parallel evaluation of SCV. The first-party integration depth is significantly higher; the trade-off is licensing cost and the requirement to move telephony to Amazon Connect.
- Plan tenant credential storage
Connectors store telephony vendor API keys in Salesforce. Use Named Credentials or the Connector recommended pattern; do not hardcode credentials in custom fields.
- Install in production after sandbox sign-off
Repeat the install in production. Train agents and supervisors on the Connector-specific UI before go-live.
- Connector and Adapter are often used interchangeably. Read the vendor documentation for what is in the package, not just the marketing material.
- Vendor Connectors require a vendor license for the underlying telephony service in addition to the Salesforce installation. The Salesforce side is free; the phone side is not.
- Some Connectors have hard dependencies on Service Cloud Voice; check before installing on a Sales Cloud-only org.
- Connector packages can grow large enough to bump against Salesforce managed-package field count and tab count limits. Audit before installing on a mature org.
- Connector upgrades may add new permission sets that require manual assignment; users without the new perms hit unexpected errors.