The Short Answer
The quality of a CTI connection is measured in three seconds: from the moment an agent answers until they see who is calling, their history, and open records. If caller identification fails, the agent starts every call by asking "Who am I speaking with?" – rendering all other investment in integrated telephony imperceptible.
The central decision isn't which adapter to choose, but where the routing decision is made: in the PBX or in Salesforce. This is where most of the risk and cost lie.
The Key Decision: Who Manages Routing
| Aspect | PBX Routing (CTI Adapter) | Omni-Channel Routing (Voice) |
|---|---|---|
| Decision Source | IVR and PBX rules | Availability and skill in Salesforce |
| Cross-Channel Balance | Phone managed separately from chat and email | Single capacity across all channels |
| Rule Changes | Dependent on telecom provider | Within Salesforce settings |
| Implementation Complexity | Relatively low | High, impacts contact center operations |
| When Suitable | Dedicated call center, mature PBX | Multi-channel contact center with mixed workload |
The problematic scenario is dual assignment – the PBX assigns, and the system reassigns. The result is agents receiving calls while handling chats, and availability metrics that are meaningless. If you choose Voice, you break routing rules from the PBX; if you keep the PBX, you don't enable Omni-Channel for the voice channel.
Caller ID: A Data Problem Before a Technology Problem
Most Screen Pop failures aren't integration issues but a lack of phone number normalization. The same customer appears as 050-1234567, +972501234567, and 0501234567 in three different systems, causing matches to fail.
What's required before connection:
- Uniform Format - E.164 as the standard, with conversion at entry, not during search.
- Defined Search Order - First Contact, then Account, then an open Case by number. The order determines what appears when there are multiple matches.
- Handling Multiple Matches - A quick selection screen, not guesswork. In enterprise PBXs and for corporate customer main numbers, this is the norm, not the exception.
- Handling Non-Identification - A rapid creation screen, so the call doesn't end without documentation.
Principles of identification and record merging are detailed in Deduplication and Record Merging.
What Happens When the Call Doesn't Flow Smoothly
Edge cases determine whether the contact center trusts the system:
- Agent Transfer - Does the Case transfer with the call, or is a new one opened? A transfer that creates a second Case disrupts both FCR metrics and the customer experience, as they recount their story twice.
- Mid-Call Disconnect - A "call back" rule with a time window is needed; otherwise, inquiries disappear without a trace.
- Outbound Call - Is it logged and associated with a Case? Without this, agent workload data is missing by about a third.
- Queue Hold and Abandonment - Abandoned calls must be available in Salesforce, not just in PBX reports; otherwise, the operational picture is incomplete.
Each of these four scenarios must be written as an end-to-end test case before going live. Only testing a standard call proves nothing.
Recording, Transcription, and Privacy
Automatic transcription has become readily available and affordable, making the temptation to apply it universally high. Three questions must be answered first:
What is the legal basis for recording and processing; how long is the transcription kept, and who can search it; and is the content used to train models? Transcription is sensitive information – it includes details customers provide orally that they wouldn't enter into a form. Field-level access restrictions and defined retention policies are part of the implementation, not a post-launch task.
Measurement After Go-Live
| Metric | Why It's Important |
|---|---|
| Automatic Identification Percentage | Direct measure of data and connection quality |
| Time to Screen Pop | Above two seconds is perceived as slow |
| Calls Without Associated Case | Reveals documentation gaps |
| Duplicate Cases Opened on Transfer | Reveals continuity failure |
| Queue Abandonment | Indication of assignment failure or staffing issues |
Summary
A successful CTI connection isn't measured by adapter installation, but by the agent starting the call knowing who is on the line and what's open, and by defining every non-standard scenario – transfer, disconnect, multiple matches – beforehand. The decision on routing location is the first to confirm, as it dictates both the operational model and the cost.