What we do
Tools
Industries
Department
How we workLet's talk →
Home/Service Cloud/Salesforce Telephony Integration
Salesforce Service Cloud

Salesforce Telephony Integration: Three Ways In, and What Makes the Screen Pop Worth Having

Getting a phone call to ring inside Service Cloud is the easy half. You can use Salesforce's own voice, keep the phone vendor you already pay for, or run Amazon Connect underneath. Each route puts a softphone in the console. What agents actually notice is whether the call arrives as a customer with an open case, or as ten digits they now have to search for.

Which route fits where you are now

Most teams don't pick from scratch. They start from a phone system they already have, a contract that's ending, or a support team about to grow.

Where you are Route to look at Ask before you sign
No real phone system yet, or one you want gone Salesforce's own voice, sold as its Contact Center editions (what most people still search for as Service Cloud Voice). Voice and digital channels come in one package. What happens to your existing numbers, and which reporting you'd lose from the old system.
Happy with RingCentral, Five9, NICE, Aircall or similar Your vendor's Salesforce app, built on Open CTI, or Salesforce's Partner Contact Center option, which brings a partner's telephony into the agent workspace. Which of the two the vendor supports. Salesforce notes that transcription on the partner route is licensed from the telephony partner, so ask who bills for it.
Already on AWS, or want Amazon Connect underneath Partner Contact Center with Amazon Connect: preintegrated telephony with a monthly minute allotment. Minutes against your real call volume, and the annual contract the edition requires.
Calls work, but agents still hunt for the customer Keep the route you have. The gap is the lookup and the wrap-up, not the telephony. Whether the caller's number is stored where the search expects it. See the list below.

Why the screen pop shows a number instead of a customer

Every route matches the incoming caller ID against phone fields in Salesforce. These are the reasons that match comes back empty or wrong.

The number lives somewhere the search doesn't look

How you'll know: The caller is a known customer, but their number is on the Account, a custom field or an old Lead, not the Contact.

Fix: Decide which records and fields the match should search, and backfill numbers onto Contacts. Clean data does more here than any phone setting.

One number, many people

How you'll know: Calls from a clinic's front desk or a company switchboard pop a list of twelve contacts, and the agent picks one at random.

Fix: Match to the Account first, then show its open cases, so the agent asks one question instead of scrolling.

The right customer, the wrong context

How you'll know: The pop shows the contact, but the agent still has to check the order system to learn the delivery is three days late.

Fix: Do an outside lookup before the pop renders: order status, account tier, unpaid balance. The same lookup can route a late-order caller straight to a senior queue.

Call logs that land nowhere useful

How you'll know: Every call is saved as an activity, but nobody can report on why people called, and the case itself never changes.

Fix: Tie the disposition to the case and give it outcomes your team actually uses, such as refund approved, redelivery booked or escalated.

From ring to logged: where each step lives

This is the path a call takes in a well-built setup. The first three are telephony. The last two are where custom work usually sits.

  1. 1

    The call rings in the console

    Whichever route you chose, the softphone sits inside Service Cloud with answer, hold, transfer and click-to-dial.

  2. 2

    Caller ID is matched to a record

    Salesforce searches phone fields for the number and pops the match. This is the step the pitfalls above break.

  3. 3

    Context comes in from outside Salesforce

    A small service checks the order, billing or scheduling system and adds what it finds to the pop, or changes which queue gets the call.

    Watch for: lookups that are slow. If the agent has already said hello by the time it arrives, nobody reads it.

  4. 4

    The agent picks an outcome

    A short disposition list on the case, not a free-text box, so the next step can act on it.

  5. 5

    The outcome changes the other systems

    Refund approved starts the refund. Redelivery booked updates the shipping date. Neither Salesforce's voice nor Open CTI does this by itself; it's built on top, often with Salesforce Flow plus a call to the outside system through the Salesforce API.

Questions people ask

What's the difference between Service Cloud Voice and Open CTI?

Service Cloud Voice is Salesforce's own voice product, now sold as Contact Center editions, with calls and their data kept inside Salesforce and an Amazon Connect option underneath. Open CTI is the older JavaScript API that lets a phone vendor put its own softphone in the console, with click-to-dial, screen pops and call logging, while the calls run on that vendor's network.

Does Service Cloud automatically match an incoming call to the right case?

It matches the caller ID to records with that phone number, which works when the number is stored cleanly on the contact. It doesn't pick the right case when a customer has several, and it won't check an outside system before routing. Both need logic built on top.

What telephony providers work with Salesforce Service Cloud?

Salesforce's own voice, Amazon Connect through the preintegrated edition, and most major business phone and contact center vendors, including RingCentral, Five9, NICE and Aircall, through their own Salesforce apps. Salesforce lists ready-made CCaaS integrations on its AgentExchange marketplace. Check which route your vendor's app uses before you plan around it.

Can a call automatically trigger an action outside Salesforce, like a refund or shipping update?

Not from the telephony connection alone, whichever route you use. The disposition has to be wired to the other system, usually through a Flow or Apex calling that system's API. n-frames builds that piece, so an agent's one click on the case does the follow-up work too.

Do we have to replace our phone system to integrate it with Salesforce?

Usually not. If your vendor has a Salesforce app on Open CTI or the partner route, you keep your numbers and contract and gain the softphone in the console. Switching only makes sense if the contract is ending anyway or the vendor's Salesforce app is weak.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.