Executive summary
A public-benefit family support helpline ran its phone line on a system that sat apart from its CRM. Agents switched between tools during every call, and the history of a conversation lived in two places.
We brought the phone line into Salesforce with Salesforce Service Cloud Voice, connected to cloud contact-centre telephony. A call record is now created in Salesforce the moment a call arrives. Hours of operation, queue availability, voicemail, extension transfers and a short post-call survey are handled by designed call flows, and agents work from a single screen.
The business challenge: a phone system cut off from the CRM
The helpline supports families, so every call matters and context matters even more. The existing setup made both harder than they needed to be.
-
Two disconnected systems
The phone system was separate from the CRM, so the call and the person's record never met.
-
Constant tool switching
Agents moved between tools mid-call to look up details and type notes.
-
Calls missing from cases
Calls were not reliably recorded against cases, so the history of a conversation was incomplete.
-
Out-of-hours calls lost
Callers who rang outside opening hours had no way to leave a message that reached the team.
-
No view of busy queues
Supervisors could not see when queues were busy or who was available to take a call.
-
No feedback loop
There was no structured way to ask callers how the call went, or to act on the answer.
-
Manual extension routing
Callers who knew who they needed relied on manual routing to an extension, which depended on whoever picked up first.
The solution: Service Cloud Voice inside the agent workspace
We implemented Salesforce Service Cloud Voice so that calls are handled inside the same console agents already use for cases. When a call arrives, a serverless function creates the call record in Salesforce straight away. The agent sees the call, the caller's record and the related case together, without leaving the workspace.
Calls are recorded, and real-time sentiment analytics give supervisors a read on how conversations are going. Everything that happens before an agent answers, and after the call ends, is handled by purpose-built call flows.
How a call moves through the system
See the agent experience
Key features of the Service Cloud Voice implementation
Each feature handles one moment in the call, so callers get a clear path and agents only take calls they can help with.
Hours-of-operation check
Each call is checked against opening hours. Outside them, the caller hears an out-of-hours message and can leave a voicemail.
Greeting and keypad menu
A greeting leads into a keypad menu: next available agent, individual agent queues, a language-specific option, voicemail, extension dialling, and a repeat-options choice.
Agent-availability check
Availability is checked before routing. If everyone is busy, a busy message offers voicemail rather than leaving the caller waiting.
Voicemail subflow
Voicemail messages are routed into a follow-up queue in Salesforce, so each one is picked up and tracked like any other piece of work.
Extension transfer
Callers who know their extension can dial it. The entry is validated, and a wrong number leads to a friendly fallback instead of a dead end.
Post-call survey
A two-question automated survey runs after the call, and the answers are written back to the call record in Salesforce.
Call recording and sentiment analytics
Calls are recorded against the call record, and real-time sentiment analytics help supervisors and agents see how a conversation is going while it is happening.
Implementation overview: from call mapping to go-live
The work followed the call journey, from first design through to monitoring once the line was live. It is the same shape as our wider Salesforce implementation approach.
-
1
Map call journeys
Document how callers reach the helpline today and what each type of call needs to happen next.
-
2
Configure Service Cloud Voice and telephony
Set up Service Cloud Voice and connect it to the cloud contact-centre telephony.
-
3
Build the call flows
Create the main inbound flow, the voicemail subflow and the survey flow.
-
4
Connect flows to Salesforce
Use serverless functions to create call records and write survey answers back, an integration pattern we cover under Salesforce integrations.
-
5
Set queues, hours and routing
Define the queues, opening hours and routing rules the flows rely on.
-
6
Test the edge cases
Try calls after hours, with a busy queue, with a wrong extension and with errors in each connected step.
-
7
Train agents and go live
Walk agents and supervisors through the new workspace, then switch the line over.
-
8
Monitor and refine
Review call records, survey answers and queue behaviour, and adjust the flows as the team learns.
Service Cloud Voice use cases
The same pattern suits any team that takes calls and needs them tied to customer or constituent records.
Customer help desks
Calls arrive with the customer's cases and history already on screen.
Nonprofit and public-sector helplines
Sensitive conversations are recorded against the right case, with a clear trail for follow-up. See our Salesforce for nonprofits work.
Multilingual routing
A language option sends callers to agents who speak their language.
Office-hours teams
Out-of-hours messages and voicemail keep after-hours calls from disappearing.
Feedback and quality monitoring
Post-call surveys and sentiment data feed coaching and service reviews.
Benefits of unifying voice and CRM
We describe the results by what changed for agents, supervisors and callers, rather than by figures.
- A single agent workspace. Calls, cases and records sit on one screen.
- Instant context. The call record exists the moment the call arrives.
- No lost after-hours calls. Voicemail lands in a follow-up queue.
- Smarter routing. Availability, language and extension choices guide each call.
- Measurable feedback. Survey answers are stored with the call they relate to.
- Supervisor visibility. Queues, availability and sentiment are easier to see.
- Auditable call history. Recordings and call records give a trail to review.
Lessons learned from the Service Cloud Voice rollout
Design the call journey before the configuration
Mapping what each caller needs made the flows simpler to build and easier for the team to explain and maintain.
Plan for the unhappy paths
After-hours calls, busy queues, wrong extensions and connection errors are where callers get lost. Each needs a clear, friendly outcome.
Keep surveys short
Two questions is enough to start a feedback loop without asking too much of callers.
Treat go-live as the start of tuning
Real calls show which menu options, messages and queues need adjusting, so monitoring and refinement belong in the plan.
Service Cloud Voice FAQ
What is Salesforce Service Cloud Voice?
Service Cloud Voice brings phone calls into Salesforce Service Cloud. Agents take and manage calls in the same workspace as their cases and records, and each call is logged against a call record in Salesforce.
How long does a Service Cloud Voice implementation take?
It depends on scope. The number of queues, languages, menu options and integrations all change the effort, so we agree a plan after mapping your call journeys rather than quoting a fixed duration.
Does Service Cloud Voice need a telephony provider?
Yes. Service Cloud Voice works with a telephony system that carries the calls. In this project that was cloud contact-centre telephony, connected to Salesforce.
Can Service Cloud Voice capture post-call surveys?
Yes. Here, a short automated survey runs after the call and the answers are written back to the call record in Salesforce, so feedback sits next to the conversation it describes.
Bring your phone support into Salesforce
If your agents still switch between a phone system and the CRM, we can map your call journeys and show what a single workspace would look like for your team.
Talk to our Salesforce team