Skip to main content
Featured group

* 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

We are using Salesforce Voice with Genesys CX and we currently have around 100 agents in our Production environment taking incoming calls daily. 

Since the first day we implemented the SCV connector in our org we had agents complaining about not hearing any type of ringtone or any audio coming out of Salesforce, we have since modified the audio settings in the Presence Configuration and the phone Service Channel but there are agents that to this day are still reporting daily that they cannot hear any ringtone. We also have instructed the agents how to configure their audio settings both on the Omni-Channel and on the browser (Google Chrome). Since it isn't every user and it looks like it isn't every call as well, we are a bit puzzled with this issue because we cannot find out any difference between users as they have the same permissions or between the calls as every call is type Incoming. 

I was reading some other posts in this group and looks like some other partners are facing similar issues, can someone shed light on this problem we are facing? 

Thanks in advance.

2 answers
  1. Jun 17, 2:46 PM

    Hi @Abaid Ur Rehman

    thank you for your response. 

    We have already instructed the agents to enable Chrome audio/sound permissions and to not leave the tab or open another browser tab with Salesforce, and the agents still report no ringtone so we have ruled those out. 

    I agree with you and I think we are at a point where we have to go agent by agent checking their headset settings, PC audio settings, Chrome extensions, VPNs or Firewalls and inspect the logs to see what really is the issue for each agent. 

    If I actually find something that could be Salesforce Voice or platform related I will update this post just in case any other partner has this issue.

0/9000

We just recently move to Natterbox and Service Cloud Voice for our telephony. For the past few months we noticed that randomly there are no voice call pop up or agent work record created for outbound calls. Any thoughts what is the root cause of the issue. What makes the issue to investigate is it does not happen everyday to a single user

0/9000

 We are using Salesforce Contact Center with Amazon Connect (SCCAC) through Amazon Connect Partner Telephony. We need to display Amazon Connect real-time and historical metrics

 (such as Agent Status, Queue Metrics, Calls Handled, Abandoned Calls, and Average Handle Time) in Salesforce Reports and Dashboards.  

 

Is there any feasibility that report can be get from the amazon connect configuring the Dashboard & Reports of Salesforce Contact Center with Amazon Connect (SCCAC).

 please share any official documentation or configuration steps for this setup?  

 

Please mention that it is possible or not possible without  custom integration using Amazon Connect Metrics API  

 

 If custom integration is needed, please provide the recommended approach or reference architecture.  

 

@* Service Cloud Voice * 

1 answer
  1. Yesterday, 5:37 PM

    Sorry for the inconvenience. In case you don't receive a response here, may I also suggest to contact Amazon Support Team to get additional assistance on this. 

     

     

0/9000

Hi everyone,   

We are experiencing an issue with inbound routing and are struggling to find the root cause. Hoping someone in the community has seen this before or can help troubleshooting this!   

Our Tech Stack:

  • Salesforce Service Cloud Voice (Partner Telephony)
  • Enhanced Omni-Channel
  • Genesys Cloud CX

The Issue: For specific agents (not all, but the affected ones experience it randomly), when a call rings in the Omni-Channel widget, they are unable to accept it. Clicking the "Accept" button does not connect the call.   

The call eventually times out, is routed back to Genesys, and pushed to the next available agent. Oddly, if it reroutes back to the same agent (after switching status), it might work perfectly the second time.

  Symptoms & Observations:

  • Agent Suspicion: Some agents feel this happens right around a status change or when their presence is flipping, but we have not been able to reliably reproduce this.
  • Because it only affects a handful of users repeatedly, we suspect a localized issue rather than a global routing failure.

  Could this be a browser-level WebRTC/headset issue where Omni cannot establish the audio path, causing the "Accept" click to fail? How to debug this?   

 

Any guidance or pointers on where to investigate next would be greatly appreciated. Thank you!   

 

@* Service Cloud Voice *  @* Service Cloud * 

4 answers
  1. Jun 15, 8:11 AM

    Hi @Mario Zoske

    In our specific case some users had a flag on the Genesys side to auto-answer incoming work and conflicted with that same setting on the Service Channel. It might not be the best solution but it solved this issue for the majority of our agents.

0/9000
  • We currently do all our call routing in Amazon Connect contact flows, and we do not have our queues mapped/synced between Amazon and Salesforce. Does this mean that we can't take advantage of the  Wallboard and Queues Backlog features? 
  • When I look at the Wallboard in Command Center, there isn't much useful information. For instance, I don't see anything in Wait Time section. 
  • In Queues Backlog, it doesn't show any queues. Is this because it only shows queues that are defined in Salesforce and synced to Amazon? 

If we need to make adjustments to sync the queues and switch to omni-channel routing, we can do that. I just want to understand what we're missing and what's needed.

Any guidance would be appreciated!

2 answers
0/9000

Hi, our team recently upgraded the Amazon Connect CTI adapter with the intention of moving to Service Cloud Voice.  Can we run some agents through the CTI adapter at the same time as running others through to Service Cloud Voice?  

 

We keep reading that it can be done, but no-one has offered how.  If it can, where do we start?

2 answers
0/9000

In the SCCAC contact center, currently I am using  {contactcenterid}-kvsTranscriber lambda to update the Bot- customer conversation in connect flow to salesforce Voice call - Enhanced conversation (Standard lightning component).

  • This method uses the kinesis to get the Bot- customer conversation and update in Voice call - Enhanced conversation 

But I want to get Bot-customer conversation from listspans API and update the Voice call - Enhanced conversation (Standard lightning component) 

 

I found that the request can able to update: 

await axios.post( SF_TRANSCRIPT_API, payload, { headers: { Authorization: token } });

 

If the above is true, please help to get,

  • structure of conversation(payload)
  • API to update Enhanced conversation(where to find SF_TRANSCRIPT_API)

Also, help me to find that there is any other method to achieve this.  

@* Service Cloud Voice *

 

#Service Cloud Voice

1 answer
  1. Jun 11, 1:37 PM

    This approach is not supported via a public or documented API.

    Key Points

    • There is no official Salesforce API (including SF_TRANSCRIPT_API) to directly update the “Voice Call – Enhanced Conversation” transcript UI.
    • The transcript shown in the standard Lightning component is populated from: 
      • Service Cloud Voice (Amazon Connect) integration
      • Kinesis streaming / Transcribe pipeline
    • The {contactcenterid}-kvsTranscriber Lambda works because it is part of the managed SCV integration flow, not a generic API endpoint.

    Clarifications

    • Can you update transcript via REST (axios / custom API)? 

      No. The endpoint you referenced is

      internal / unsupported and not intended for custom use.
    • Is there a payload structure available? 

      No official payload schema is exposed because

      direct write access is not supported.
    • Can you push transcripts from ListSpans API? 

      Not directly into the standard Enhanced Conversation component.

    Supported Approaches

    Option 1 (Recommended)

    • Use the standard Service Cloud Voice + Amazon Connect streaming (Kinesis/Transcribe)
    • This is the only supported way to populate Enhanced Conversation UI

    Option 2

    • Store external transcript (ListSpans output) in: 
      • Custom Object / Big Object
      • Or related records
    • Surface it via: 
      • Custom LWC / UI component on Voice Call record

    Option 3 (Advanced)

    • Build a custom integration pipeline that mimics SCV ingestion (complex and not officially documented)

    Final Conclusion

    • Direct API-based update of Enhanced Conversation is not supported
    • The working Lambda method succeeds because it is part of Salesforce-managed SCV ingestion flow
    • For external transcript sources, you must use custom storage + custom UI, not the standard component
0/9000

Some of our staff are still using Zoom voice, and we'd like our customer service rep to be able to transfer a call to someone using the recipient's Zoom voice number (we understand the transcript/recording would be cut off at that point), however I'm not sure how to access the dial pad during transfer to be able to transfer the call.  We are using Salesforce Voice on Hyperforce, (not Salesforce connect).  Any support/insights would be appreciated!

5 answers
0/9000

Hi Community,

I’m hoping someone might have insight into an issue we’ve been dealing with. We have one user who’s consistently running into problems with Genesys in Salesforce either their call transcripts don’t load properly, or their calls drop unexpectedly.   

They’re using Chrome, which is the standard browser for our environment, so switching browsers isn’t an option. What’s puzzling is that this seems to be isolated to just this one person.

We’ve reached out to our Genesys support team, but unfortunately, the issue keeps getting bounced back and forth without a clear resolution. Has anyone seen something similar or know of any known issues that could cause this?   

Any suggestions or guidance would be really appreciated!

Thanks,   Jeremy   

 

@* Service Cloud *  @* Service Cloud Voice * 

1 answer
  1. Oct 30, 2025, 3:00 PM

    Did you confirm their browser settings (security, third party cookies, etc) are the same as for the other colleagues?

0/9000

I created an Agentforce Voice Agent and added the related Service Cloud Voice license/permission sets, but when I go to Setup, I don’t see the Telephony option when creating a new connection. Where did I go wrong?  

Missing the Telephony option in new Connection of Agenforce Voice Agenforce

 

 

2 answers
0/9000