Skip to content
Back to case studies

Case study · Service Cloud Voice · Amazon Connect

PFT Salesforce Voice with Amazon Connect: Case Study

Problems we hit while building a voice contact center inside Salesforce, and how each one was resolved.

TwinStack Team
PFT Salesforce Voice with Amazon Connect case study: Salesforce and Amazon Connect joined by call audio waves, with the Omni-Channel softphone on desktop and mobile.

Overview

PFT moved its phone operation into Salesforce using Service Cloud Voice bundled with Amazon Connect. Callers reach an Amazon Connect IVR, are routed to the right person or department, and every call appears in Salesforce as a Voice Call record linked to the caller's contact and, where appropriate, an automatically created case. Staff answer calls from the Omni-Channel softphone without leaving the Service Console.

The platform worked well from the start, but real use surfaced practical problems. Some were configuration questions (how do we change who answers a call?), some were access questions (how do field staff take calls on a phone?), and some were genuinely confusing behavior (why did a voicemail play, then stop?). This case study documents four of them. For each, it describes the situation, the diagnosis, the resolution, and the lesson worth keeping.

The solution at a glance

LayerWhat it does
Amazon Connect IVR and flowsGreets callers, checks hours of operation, lets callers choose a department, offers voicemail when no one is available
Queues and routing profilesDecide which people can receive which calls
Salesforce Service Cloud VoiceShows the softphone, creates Voice Call records, links the caller to a contact and a case
Voicemail subflowRecords the message, tags the Voice Call, and feeds the transcription pipeline

Office hours are Monday to Friday, 8 AM to 5 PM. After hours, callers hear an out-of-hours message. During hours, if no agent is available, the caller can leave a voicemail and a case is created automatically, depending on the department selected.

Problem 1

Changing who takes a call without touching the Amazon Connect flow

The situation

The IVR menu sends callers to departments such as Information Officers, Human Resources, the Grievance Office, Staffer Representatives, and executive lines. Staff assignments change: someone goes on leave, a colleague covers a role, or a new employee joins. Treating each change as a flow edit inside Amazon Connect is slow, risky (a mistake in a flow affects every caller), and requires someone comfortable editing contact flows.

The diagnosis

The flow does not decide which person answers. It decides which queue a call is transferred to. Which people receive calls from that queue is decided one layer lower, by each user's routing profile, which lists the queues that user works. The flow can stay frozen while the people behind each queue change freely.

The resolution

Every IVR option points to a queue, and every user has their own routing profile with a default queue. The mapping, shown by role:

User roleRouting profileDefault assigned queue
Information officer 1RP_ErikInformation_Slot_1, HR_Fallback
Information officer 2RP_EdInformation_Slot_2
Information officer 3 / GrievanceRP_deniseInformation_Slot_3, PFT Grievance Office
Human resourcesRP_SharonPFT Human Resources
Staffer representatives 1 to 6RP_Staffer_1 to RP_Staffer_6Staffer_Rep_1 to Staffer_Rep_6
Political DirectorPolitical DirectorPolitical Director
Communications DirectorCommunications DirectorCommunications Director

Each IVR choice transfers to a queue:

QueueReached from
Information_Slot_1, 2, 3Information Officers (IVR option 2)
PFT Human ResourcesHR (IVR option 3)
HR_FallbackIf HR is unavailable (IVR option 3)
PFT Grievance OfficeGrievance Office (IVR option 4)
Staffer_Rep_1 to 6Staffer Representatives (IVR option 5)
PFT VoicemailVoicemail failsafe (IVR option 6)

To change who takes a call, an administrator opens the person's routing profile in Amazon Connect and changes the queue assigned to it. For example, to have a colleague answer HR calls while the HR lead is out, add the PFT Human Resources queue to that colleague's routing profile. The next call to that queue rings the new person. No flow was opened, edited, or republished.

The same design handles hours. Separate hours-of-operation records (one Information slot covering 8 AM to 9 AM, another 9 AM to 1 PM and 2 PM to 5 PM, and another covering the 1 PM to 2 PM lunch hour) let different people cover different parts of the day while callers still hear a single menu. New users are simple to add: create the user, assign any existing routing profile, and they begin receiving that profile's calls.

The lesson. Keep the flow stable and put the variability in the routing profiles. Flows describe the path a call takes; routing profiles describe who is available at the end of that path.

Problem 2

Letting standard users make voice calls from a mobile phone

The situation

Field staff needed to place and receive calls with the Amazon Connect softphone from their phones, with the same benefits desk users get: caller lookup, a Voice Call record, an automatically created case, and the ability to work the case afterward. The org has two custom profiles, PFT System Admin and PFT Standard User, and the goal was to enable Service Cloud Voice for standard users so they could take calls without administrator rights.

The diagnosis

There were two separate obstacles.

Access. Voice setup pages in Setup, including the Amazon Contact Centers page, were visible only to the System Admin profile. A standard user does not need to see them to take calls, but does need to be a member of the contact center, hold the voice permissions, and have a matching Amazon Connect user with a routing profile.

The phone itself. The Omni-Channel softphone behaves differently by platform:

FactorAndroid (Chrome)iPhone (Safari and Chrome)
Browser engineBlink (Chromium)WebKit (required by iOS for every browser)
Third-party cookiesAllowed or easily promptedBlocked by Intelligent Tracking Prevention
Softphone sign-inAuthenticates normallySingle sign-on fails silently inside the Utility Bar iframe
Audio and microphoneWorks in desktop modeStrict user-gesture rules block audio access
Official supportWorks, though not formally supportedNot supported

On Android, Lightning loads in the mobile browser once Desktop Mode is on (otherwise the Classic view appears), and the softphone, Voice Calls, and the Case subtab with its fields are all visible. On iPhone, every browser is a wrapper around Safari's WebKit, so switching browsers changes nothing. iPad is worse: Salesforce hides the Utility Bar there, and telephony providers support only desktop Chrome, Firefox, and Edge.

The resolution

  • Enable the standard user for voice. Add the user to the contact center, assign the voice permissions, and create or link their Amazon Connect user with the appropriate routing profile (see Problem 1).
  • Android: open Salesforce in Chrome with Desktop Mode enabled and use the Omni-Channel softphone as on a desktop.
  • iPhone: log in to Amazon Connect through Salesforce so calls are handled outside the blocked iframe sign-in. In testing this works on iPhone: the app keeps running in the background, calls work with the screen off, cases are still created automatically, and case work is done in the Salesforce mobile app.
  • Tablets: use a touch-enabled Windows tablet (such as a Surface Pro) or an Android tablet with Chrome in desktop mode. iPad is not workable.

A commercial fallback also exists: a marketplace mobile app for Amazon Connect at roughly $29.99 per user per month, with a ten-user minimum and a trial available. We kept it in reserve since the Salesforce-based login met the requirement without extra license cost.

For the step-by-step version, see our guide to Salesforce Voice on mobile: calls on iPhone and Android.

The lesson. The iPhone limitation is a platform rule, not a misconfiguration, so the answer is a different entry point, not more troubleshooting. Document the supported device for each type of user.

Problem 3

Cookies, and logging in as a second account

The situation

While testing, we signed into a different Salesforce account in the same browser without clearing site data, and Amazon Connect kept showing the previous account's users. It looked like a permissions problem or an out-of-date sync.

The diagnosis

It was neither. It was saved login data in the browser. Amazon Connect relies on cookies for its login session, and the browser still held the first account's session, so Amazon Connect kept treating it as the earlier identity. The same dependency explains why third-party cookies matter: Amazon Connect runs on a different domain from Salesforce, and if the browser blocks third-party cookies the login can fail without an obvious error. The confirming test is simple: the problem disappears in a clean browser session.

The resolution

  • Clear cookies and site data for the site.
  • Enable third-party cookies, because Amazon Connect relies on them for login.
  • If you switch between Salesforce accounts regularly, use a separate browser profile for each account so the sessions never overlap.
The lesson. When the data on screen belongs to the wrong account, suspect the session before the permissions. Try the same action in a private window or fresh browser profile first. If it behaves correctly there, you have confirmed it is saved login data.

Problem 4

Voicemail recordings that play, then stop playing

The situation

A voicemail was playable in Salesforce right after the call. Once it finished processing, it stopped playing, and the player showed only "We can't load the recording. Try again later." This was alarming because the audio had clearly been captured: it had played minutes earlier.

The diagnosis

The first clue was in the data. At the exact moment playback broke, the owner of the Voice Call record changed from an automated system user to the Voicemail queue. That change is part of post-call processing, which suggested processing was also changing which audio file the player was pointed at.

The second clue came from comparing against an earlier project where playback worked. In the Amazon Connect settings under Enable conversational analytics, the broken build had Automated interaction analytics switched on. The working build had only Real-time and post-contact analytics selected.

The explanation fits both clues. A voicemail never reaches an agent, so Amazon Connect treats it as an automated interaction and stores its recording separately from agent call recordings. With Automated interaction analytics on, a different file was produced than the one the Salesforce player was looking for. The player was not broken; it was asking for a file that was no longer the one that existed.

The resolution

Turn Automated interaction analytics off, keeping Real-time and post-contact analytics. After the change, voicemails kept playing after processing finished.

The lesson. Two habits solved this. First, watch what else changes at the moment something breaks (here, the record owner). Second, when an earlier build worked, compare settings side by side rather than debugging the broken one in isolation. One toggle that looks unrelated to playback was the entire cause.

Related open item: voicemail that times out

Voicemail uses a dedicated Connect subflow with a 170-second recording window. When a caller presses a key to finish, the Voice Call completes with a duration and a transcript. When the window instead runs out, the Voice Call stays in the New state with no duration and no transcript. This is under investigation. Like Problem 4, the recording exists but post-call processing does not complete on the normal path.

Summary of problems and fixes

#ProblemRoot causeFix
1Change who takes a callPeople are set by routing profiles, not flowsChange the queue on the routing profile
2Standard users calling from mobileVoice access setup plus WebKit limits on iPhoneEnable voice for the user; Android desktop mode; Salesforce-based Connect login on iPhone
3Connect shows the wrong account's usersSaved login data and cookiesClear site data, enable third-party cookies, one browser profile per account
4Voicemail plays, then stopsAutomated interaction analytics stored a different recording fileTurn Automated interaction analytics off

Key takeaways

Separate the path from the people

Flows stay stable; routing profiles carry staffing changes.

Know the device matrix

Desktop and Android work; iPhone needs a different entry point; iPad is not supported.

Suspect the session first

Many "wrong data" symptoms are cookies, not permissions.

Compare with a working build

One analytics setting explained a failure that looked like a Salesforce problem.

Building a voice contact center in Salesforce?

We can help you set up Service Cloud Voice with Amazon Connect and avoid the problems above.

Talk to our Salesforce team

Return to all case studies