Skip to main content
Groupe à la une

* Service Cloud Voice *

Welcome! This group is dedicated to your success with Salesforce Service Cloud Voice. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

Hi everyone, 

 

I wanted to ask if Salesforce Voice automatically associating Related Record field in Voice Call with the record you are displaying on screen is something standard from the Salesforce Voice package and if it is configurable in some way, deactivating it if possible. 

 

We have some custom processes that, for any type of Voice Call (Inbound, Outbound, Callback, etc.), search for any Contact or Lead that exists for the call's phone number and if any exist we fill the Related Record field on Voice Call with said records. Recently users have reported that when they are displaying another Contact or Lead on screen somehow this record ends up on the Related Record field of an unrelated call instead of the one found by our processes. We have debugged everything and we see that our flows do run and get the record correctly, but somehow get overridden by something. This something we suspect is something native from the Voice package. 

We have also tried to take control of this through the console workspace API but it is still happening. 

 

Does anybody have any info on this? Does this native functionality overriding our processes actually exist or have we just done this ourselves with our flows? 

 

Any help is welcome!

4 réponses
  1. 9 sept., 08:00

    I’d look closely at whether the value is being populated by the Voice package through the active console context. If the flow is correctly finding the Contact/Lead but the value changes afterward, that timing would be the first thing I’d try to isolate. 

     

    A useful test would be to temporarily remove the custom assignment and watch the Voice Call record through the full lifecycle: call creation → console record context → flow execution → final Related Record value. That should help identify whether the native behavior happens before or after the flow. I’d also check whether the behavior differs between inbound, outbound, and callback calls. 

     

    More broadly, this is a good example of why Salesforce telephony needs to be evaluated beyond just “does it make calls?” The interaction between call context, CRM records, routing, logging, and automation can become important very quickly. I’ve seen this discussed in the context of comparing the different

    Salesforce telephony options as well.

0/9000

Open CTI Retirement: A Better Migration Path

With Salesforce Open CTI officially reaching end of life on February 28, 2028, many organizations are stuck in an awkward spot:

  • You know you need to move 
  • But you’re still under contract with a third-party CTI vendor 
  • And migrating too early (or too fast) introduces risk 

We’re offering a different path.

AMC Technology will buy out your remaining Open CTI contract with your current provider and replace it with our DaVinci Toolkit, giving you a controlled, low-risk transition to Salesforce Voice.

What this means for you:

  • No double-paying for overlapping solutions 
  • No forced migration timeline
  • No disruption to your current operations

Instead, you can:

  • Continue supporting your existing CTI environment 
  • Gradually introduce Salesforce Voice use cases 
  • Migrate on your schedule—well ahead of the 2028 deadline 

Why this matters:

Most migration strategies assume a “rip and replace” approach, that’s too disruptive to busy contact centers. 

DaVinci was built to orchestrate use cases across platforms

, so you can run hybrid environments while you transition, without locking yourself into a single vendor decision too early. 

 

If you're currently evaluating your Open CTI exit strategy, I’m happy to share how we’re working with other customers who are actively migrating.   

 

Here's a link to the specifics of the buyout offer.

2 commentaires
  1. 8 sept., 07:13

     

    The hybrid approach makes a lot of sense for organizations that can’t afford a “rip and replace” migration. The bigger challenge with Open CTI retirement is usually not the technology itself, but timing the move around existing vendor contracts, integrations, agent workflows, and operational risk. The post makes a good point about avoiding unnecessary double-paying while still having a clear path toward Salesforce Voice. 

     

    I’d also build the migration plan around total cost rather than just the replacement license. Existing CTI contracts, implementation effort, call usage, storage, training, testing, and any temporary hybrid architecture can all affect the real number. 

     

    That’s why I think this

    Open CTI Migration Cost Guide is relevant to the discussion. It looks at the cost side of the migration rather than assuming the cheapest-looking replacement will necessarily have the lowest long-term TCO.

0/9000

Some agents are getting sometimes the message 'Can't access object' when taking phone calls, they are still able to take the call but they can't see any of the call information in the omnichannel window, users should already have full permissions to access the Voice Call object so i'm not sure what could be causing this. 

 

We are using Genesys CX Cloud as the Telephony provider. 

 

Regards 

Salesforce Omnichannel - Can't access object

 

#Service Cloud Voice

 

@* Service Cloud Voice *

3 réponses
0/9000

I'm testing Unified Routing in an SDO (AWS). I've read this article about transfers. 

https://help.salesforce.com/s/articleView?id=service.voice_omni_unified_routing_transfer_destination.htm&type=5

 

 

I can see the list of transfer destinations has changed and flows are no longer there. Only being able to transfer to queues and profiles seems limited. Transfer to queues seems redundant as the Unified Routing guide recommends using a single holding queue. 

 

Without flows, how can you transfer and still make routing decisions to reskill?

4 réponses
  1. 6 août, 08:51

    Hello @David Stevens  thank you for the response. However, it doesn't fully add up for me, because in AWS I have the ability to create different types of quick transfers, such as to a queue or a user. On the other hand, with Unified Routing and enabling a single contact flow, you can define the target dynamically within the flow, but the agent's input is not as flexible. In contrast, with Quick Connect, I see more flexibility on that side. 

0/9000

Has anyone found the release changes for contact center upgrade version 21.1? I'd like to get rid of the annoying orange bar on my screens but I'm not deploying unspecified changes.  

 

The documentation only shows v20.0:

https://help.salesforce.com/s/articleView?id=service.voice_cc21.htm&type=5

3 réponses
  1. 28 juil., 14:22

    I was informed that official Contact Center v21.1 release notes are expected to be published after August 5, 5:00 PM PST

0/9000

Previously I can be able to login amazon connect SAML instance with salesforce user.  

 

But now Unable to login SAML instance of amazon connect with Salesforce user. Setup>Partner Telephony Contact Centre> Open YOUR Contact center > Click 'Telephony Provider Settings'. when clicked the below page appear.

 

Unable to Login Amazon connect SAML Instance with IDP salesforce user and Inbound Call not receiving in omni channel.

 

 

In the SCCAC contact center connected with above SAML connect instance, active status achieved in omni channel when I login with amazon IAM user(not salesforce contact center user) in SAML connect instance in same window of browser, otherwise showing Log into Omni-Channel failed.

 

When the status is active 

  • The Incoming Voice call is not receiving in the omni channel where the same configuration worked before.
  • But the outbound calls are made with the omni channel and working fine.

image.png

 

 

What is the possible fixes for the above problem.

2 réponses
  1. 8 mai, 12:22

    @Naveen Kumar S these are two issues. The Insufficient Privileges page on Telephony Provider Settings

    usually points to access/configuration, not an Amazon Connect outage. Make sure the Salesforce user has the correct Service Cloud Voice / Partner Telephony permission sets and is added as a user on the Contact Center. Also check the Amazon Connect side. Salesforce permission sets do not automatically give the user Amazon Connect admin/security profile access. 

    Found a similar thread:

    https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000K0pExSAJ

     

     

    For the SAML login issue, I would also check whether the contact center SSO connected app access changed, whether the SAML certificate expired/changed, and whether the Salesforce user still maps correctly to the Amazon Connect user. Salesforce docs say Salesforce users with the Service Cloud Voice permission set should be automatically logged into the associated Amazon Connect instance when SSO is configured correctly. 

    https://help.salesforce.com/s/articleView?id=service.voice_amazon_config_sso.htm&type=5

    For the inbound call issue, since outbound works, the softphone/browser side is probably okay. I would check the inbound path: Amazon Connect phone number, contact flow, queue, routing profile, agent availability, Omni presence, capacity, and whether the VoiceCall record is created in Salesforce. If VoiceCall records are created but not routed, focus on Omni/routing config. If no VoiceCall is created, focus on Amazon Connect/contact flow/Salesforce integration.

    Also confirm you are not mixing Amazon external routing and Salesforce Omni-Channel Unified Routing in the same contact center. Salesforce docs say to use only one routing system per contact center.

0/9000

We have had several reports of agents having issues with the Omni channel call controls. These agents are actively answering calls via omni channel, but when voice call record opens and they try to reopen the omni channel widget to use the call controls the buttons/numbers are greyed out, and unclickable. They end up stuck with the caller on the phone but unable to transfer. 

 

Similarly, on occasions agents are able to make outbound calls via click to dial for known contacts but the keypad is greyed out/unclickable if they try to dial a number manually.

 

Has anyone else experienced similar issues? 

Thank You 

John

5 réponses
  1. 24 juil., 12:58

    The keypad going greyed out is usually just the CCP (Contact Control Panel) trying to establish a connection to Amazon Connect in the background. It normally only takes a few seconds, but if your internet is slow or unstable it can take a bit longer, and during that time the buttons stay unclickable.

    One thing that helps: go into your browser settings and add your Salesforce org URL to the "always keep active" tabs list, so the tab never goes to sleep in the background.  

     

    The keypad going greyed out is usually just the CCP (Contact Control Panel) trying to establish a connection to Amazon Connect in the background.

     

     

0/9000

We have agents reporting that when an inbound call comes in and the agent clicks accept, the call does not accept and then gets routed to another agent, and the original agent automatically goes offline. 

 

@* Service Cloud Voice * 

5 réponses
  1. 24 juil., 11:46

    HI @Osman Rehman , This can also happen if unified routing is enabled but not configured properly. If you have unified routing enabled in your contact center, make sure it's disabled unless it's fully set up. Also, when agents mark themselves online, tell them to wait until the dialpad's input bar becomes editable (you can actually type a number into it). There's usually a lag between marking yourself online and the dialpad actually going live,  that moment when the dialpad becomes editable is when you're actually online. 

0/9000

We are facing an issue in the Salesforce Service Cloud Voice SCC-AC integration where the caller name is not displayed during incoming calls.

Current behavior:

  • During the incoming call popup, only the phone number is displayed.
  • The caller/contact name is not shown in real time.
  • After the call ends, the VoiceCall record gets linked correctly to the Contact record.

Configuration already completed:

  • Enabled “Match Callers to End User Records” in Partner Telephony Setup.
  • Caller phone numbers are available in Salesforce records.
  • VoiceCall records are getting created successfully.

Expected behavior:

  • Caller name should appear during the incoming call itself instead of showing only the phone number.

 

Caller Name Not Showing During Incoming Calls in SCC-AC

Please assist with the required configuration changes or troubleshooting steps get the contact's name while incoming calls.

Thanks.

4 réponses
  1. 16 juil., 11:51

    If you're comparing different Salesforce CTI implementations, it can also be useful to see how other solutions handle real-time caller identification during screen pops. I came across 360 CTI

    while researching similar use cases: 

    https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000HEVm1UAH 

    Out of curiosity, are you using the native Salesforce Voice connector with Amazon Connect, or a partner telephony integration? 

0/9000

We use Service Cloud Voice connected to Talkdesk. When a call comes in, we hear the default Omnichannel ringtone played, but at the  same time there is a second ring tone that goes "Doo-Dee-Doo" playing. We just can't figure out where that second ringtone is coming from. If we change our audio settings to take a call on a headset and have the Ringer Output go to our computer speakers, then the default omnichannel ringtone goes to the computer speakers and the Doo-Dee-Doo ringtone goes to the headset. 

 

This happens in both Chrome and Edge, so doesn't seem to be browser related. It happens in both our stage and prod environments. It happens to agents with different profiles. If I change the default ringtone in "Service Channels" or "Presence Settings", the default ringtone is replaced, but the Doo-Dee-Doo ringtone will still play at the same time as the custom ringtone.

 

Anyone else heard this Doo-Dee-Doo ringtone playing at the same time as the default Omni ring tone?

@* Service Cloud Voice * 

3 réponses
  1. 14 juil., 12:11

    @Rick Waller

    when you figured out the issue were you able to surpress one?  

     

    We are experiencing the same double tone with SCV and Five9 as our BYOT vendor. We have gotten the terminal answer of "it is a limitation" from Five9 who reports talking to the Salesforce product team. 

0/9000