Skip to main content

#Service Cloud Voice25 人がディスカッション中

Summer '24 released this feature where agents can open multiple console tabs/browser windows and Omni-Channel remains synced with only the first window/Omni session. It also keeps the agent synced with the browser window is refreshed.

 

The release notes do not confirm, nor deny, if this feature includes Service Cloud Voice. Can anyone from the production team chime in if SCV with Amazon Connect and/or Partner Telephony agents can benefit from this new feature?

4 件の回答
  1. 10月15日 12:21
    Our org is facing the same issue and calls are disconnected if they duplicate or clicks a button that opens into a new tab. With don't automatically we were able to atleast not disconnect the call in UAt org but it broke in production
0/9000

I'm building a Service Cloud Voice for Partner Telephony POC but I'm having an issue now with the Decline Call event.

We have it configured with a Declined reason and everything but we are not seeing the Decline Call getting triggered at all, either from the connector or base connector.  

When declining a call the declineCall method is never triggeredimage.png

 

 

There is no decline event either on the agent debug log.

 

 

image.png

 

 

 

Any setting we might be missing ?

1 件の回答
  1. 昨日、3:18

    To fix the issue where the declineCall method fails to trigger in your Service Cloud Voice Partner Telephony POC, first open your active presence configuration in Setup and ensure that the Allow agents to decline work requests checkbox is enabled, as disabling this setting can silently drop decline events. Verify success by reviewing your agent debug logs to confirm that clicking decline successfully fires the event payload back to the contact center event stream. 

     

    Next, inspect your telephony connector implementation code to confirm that the declineCall method is properly bound to the Omni-Channel workspace API event listener rather than an unhandled custom button action. Verify this step was successful by opening your browser console while reproducing the call decline action to check for uncaught JavaScript errors or failed postMessage payloads originating from the partner telephony softphone frame.

0/9000

When I then check the voice call record, it says the owner is autoproc.

Can anyone help on how to get available agent receive the call without being on the queue?

I look forward to your help.

 

Kind regards

@* Service Cloud Voice * 

1 件の回答
  1. 昨日、3:15

    Check your Contact Center routing configuration and Omni-Channel Flow logic to ensure that inbound calls originating from an agent's registered phone number or device do not trigger fallback queue routing rules. You should also verify that the telephony provider (such as Amazon Connect) and the associated Salesforce routing flows correctly identify agent-initiated calls and map them to the proper service channel without triggering automated fallback user ownership. 

     

    Then, review your routing configuration in Setup > Omni-Channel > Service Channels and inspect the Omni-Channel Supervisor logs to trace how the call routing attributes evaluate during test calls. Ensuring that your agent's presence status is properly synchronized with the telephony user mapping will prevent the system from defaulting to offline fallback agents and ensure incoming calls connect immediately to the intended available user.

0/9000

Hi all,

We are using Service Cloud Voice with partner telephony. Voice Calls show up in the activity timeline on Account and Contact records, which is good, but the entry only shows the Voice Call link, duration, date, day, related record and agent.

I want to show more detail there, ideally a call summary field so users can see what the call was about without opening every Voice Call record. 

How do I add more fields to the Voice Call entry in the Account/Contact activity feed/timeline?

 

Where is this controlled, and how do I add fields to it? Is it a compact layout, a page layout, something in the Lightning App Builder, or somewhere else entirely?  

I have not been able to work out which setting drives that entry. 

Also , we are retiring the Log a call task as part of migration hence that will be also be no longer available.

If this is not something you can configure, I would be glad to hear what others are doing instead on Account and Contact pages.

Thanks. 

 

#Service Cloud Voice  #Voice Call Record  #Salesforce Developer  #Salesforce Admin  #TrailblazerCommunity

6 件の回答
0/9000

Hi, 

 

Use-case: In a 3rd party VoIP softphone there is an incoming phone call from customer. The phone call is already visible in Salesforce Omni Channel widget, as a CALL_STARTED event was published. Customer rep can successfully accept the call by pressing "Accept" in Omni Channel widget/sidebar. 

 

However, in our case the rep can also accept the call directly in our softphone. In that case we need to programmatically tell Salesforce that "this call is now accepted". I'm having trouble finding the correct mechanism for this, in the Service Cloud Voice base connector (@salesforce/scv-connector-base). 

 

Any advice, please? 

 

I did find that this might be possible by using the Voice LWC Toolkit API, as it has "acceptCall" method available which sounds very tempting. But I'm trying to understand if this is really the only way. It seems to me that the Connector should support such a simple use-case. Currently we don't have the Voice LWC Toolkit in use at all, and I'm trying to avoid bloating our implementation. 

 

#Service Cloud Voice

7 件の回答
  1. 10月12日 8:04

    @Gabriel Fuoco

     no, I did not try the toolkit path (at least not yet). 

     

    Code below works in my tests to "auto-accept" call on Salesforce side . However, I would like to understand if this can have some strange consequences I'm not yet aware of. 

     

    // User accepts call in our softphone -> Programmatically accept on Salesforce side.const call = new PhoneCall({	callId: "ourVendorCallId",	state: Constants.CALL_STATE.CONNECTED,	callAttributes: new PhoneCallAttributes({		voiceCallId: "voiceCallId",		participantType: Constants.PARTICIPANT_TYPE.INITIAL_CALLER	}),	callInfo: new CallInfo({		// Unofficial workaround:		// Temporarily set isSoftphoneCall to false. With this, the work item is cleared from Omni Inbox.		isSoftphoneCall: false	})});publishEvent ({	eventType: Constants.VOICE_EVENT_TYPE.CALL_CONNECTED,	payload: new CallResult({ call })});
0/9000

Hi all,

We are using Service Cloud Voice with partner telephony. Voice Calls show up in the activity timeline on Account and Contact records, which is good, but the entry only shows the Voice Call link, duration, date, day, related record and agent.

I want to show more detail there, ideally a call summary field so users can see what the call was about without opening every Voice Call record. 

How do I add more fields to the Voice Call entry in the Account/Contact activity feed/timeline?

 

 

Where is this controlled, and how do I add fields to it? Is it a compact layout, a page layout, something in the Lightning App Builder, or somewhere else entirely?  

I have not been able to work out which setting drives that entry. 

Also , we are retiring the Log a call task as part of migration hence that will be also be no longer available.

If this is not something you can configure, I would be glad to hear what others are doing instead on Account and Contact pages.

Thanks. 

 

 

 

#Service Cloud Voice  #Voice Call Record  #Salesforce Developer  #Salesforce Admin  #TrailblazerCommunity

2 件の回答
  1. 10月9日 6:48

    Hi @Digbijaya Paikaray

    , 

    Thanks for the suggestions. We are retiring the Log a call task feature as it will duplicate the Voice call record role hence that's not a permanent solution. As for Voice Call related list  we already have activity feed we do not want to clutter the standard object pages with extra components. 

    My main issue is that I am not able to figure out which compact layout is monitoring the Activity view for Voice Calls, I tried modifying the system default for Voice calls which is currently deployed but it was of no use.

0/9000

Setup:

 

We have an Agentforce superagent with two connected subagents wired via connected_subagent blocks in the .agent file. Deployed on Service Cloud Voice (PSTN telephony channel).

Problem:

 

On every turn where the master agent routes to a connected subagent, the caller hears

"Collaborating with other agents" spoken aloud before the subagent's actual response. This happens on every single turn - not just the first handoff - making the experience very disruptive on a live voice call.

What we tried:

  • Setting loading_text to a custom string → that custom string gets spoken instead (confirms loading_text is read aloud on voice)
  • Setting loading_text: "" (empty string) → platform still speaks "Collaborating with other agents" (empty string does not suppress the default)
  • Omitting loading_text entirely → same default audio plays
  • Adding outbound_filler_sentences to the modality voice block → no observed change to the connected subagent audio

Current workaround:

 

Set loading_text: "One moment." - replaces "Collaborating with other agents" with a shorter phrase, but doesn't eliminate the audio entirely.

What we want:

 

Either silence the audio completely between turns, or understand if there is a supported way to suppress the platform's default connected subagent filler on a voice channel.

Questions for the community:

  1. Is there a way to fully silence loading_text on a voice channel (e.g., a single space, a special value)?
  2. Does outbound_filler_sentences in modality voice affect connected subagent transitions, or only action calls?
  3. Is this a known limitation of the superagent/connected subagent pattern on voice, and is there a workaround?

 

 

 

 

 

#Agentforce  #SuperAgents  #Service Cloud Voice

4 件の回答
  1. 10月1日 15:46

    Hi @Sumit Sangwan

     

    Hi Sumit, I think what you’re seeing is expected behavior with the current Voice + connected subagent setup. 

     

    From your testing, it looks like loading_text is always being spoken on the voice channel. When you leave it empty, Agentforce falls back to the default message “Collaborating with other agents”

    instead of staying silent. 

     

    outbound_filler_sentences is mainly used while actions are running, so it may not control the connected subagent handoff message. 

     

    At the moment, I’m not aware of a supported value like blank space, null, or another setting that completely removes this audio. 

     

    So your current workaround: 

     

    loading_text: "One moment."

    is probably the safest option for now. 

     

    I would also raise this with Salesforce Support or post it as an Idea, because on a live PSTN call, hearing the same handoff message on every subagent turn can definitely affect the user experience. 

     

    Thank you, 

    Venkat Yadav.

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 *

4 件の回答
  1. 9月30日 15:27

    We had a Omni-Channel flows doing screen pops, was fixed after removing it and changing the approach to open the records.

0/9000

1. Agents are receiving inbound calls, they click on accept multiple times and the call does not accept, gets routed to the next agent and the initial agent goes offline automatically.  2. Agent experiences sound quality issue where the inbound call comes in, the agent can hear the caller clearly but the caller hears a "choppy" audio on there end.    Any help or guidance is appreciated!   

1 件の回答
  1. 9月28日 12:43

    Hi Osman!

    For the two symptoms, I’d troubleshoot them separately because they can have different causes.

    For the call not being accepted and the agent going offline, check the agent’s Omni-Channel/voice presence state, browser console logs, and whether the Amazon Connect contact is actually being accepted when the agent clicks Accept. Also check whether multiple clicks are generating duplicate accept attempts or causing a timeout before the contact is routed to the next agent. 

     

    For the choppy audio heard by the caller, check the agent’s network stability, browser/device audio settings, headset, and Amazon Connect contact/voice logs. Since the agent can hear the caller clearly but the caller hears choppy audio, I’d specifically investigate the agent-to-caller outbound audio path and network/WebRTC conditions. 

     

    If possible, capture the timestamp, agent, contact/call ID, and browser/OS for one example of each issue. That should make it much easier to correlate the Salesforce and Amazon Connect logs.

0/9000

*** Important Update to Amazon AI Features on your Salesforce Voice Account | Action may be required ****** Important Update to Amazon AI Features on your Salesforce Voice Account | Action may be required ***This is an important update regarding your Salesforce Voice environment and the proactive step wThis is an important update regarding your Salesforce Voice environment and the proactive step we are taking to protect your account from unexpected billing charges.

 

What’s changed

As previously shared, Amazon, the underlying infrastructure provider for Salesforce Voice with Amazon Connect, recently introduced a new AI feature set: Amazon Connect Customer. This capability was deployed and enabled by default across all Salesforce Voice with Amazon Connect customer instances by Amazon.

 

What we're doing

Our priority remains transparency and ensuring that you only pay for services you actively choose to consume. Because this feature set was not included in your existing order form and is not part of the underlying product sold by Salesforce, we are proactively disabling additional AI features for Amazon Connect Customer across your account effective in the Winter ’27 release, which began on September 2, 2026. This change is rolling out across environments for Winter ’27, beginning with sandbox and moving through production.

Following the release, your account will have Amazon Connect Customer Basic functionality. We are taking this action to ensure you don’t incur unintended or unauthorized charges on your next billing cycle.

 

Your choice to opt in

Some organizations may want to leverage Amazon’s advanced AI capabilities to enhance their Salesforce Voice experience. You have full control to opt into AI features for Amazon Connect Customer if these fit your business needs. 

 

Please note that AI features for Amazon Connect Customer require a paid, usage-based add-on. If you choose to enable this add-on feature, usage for that add-on will be billed at 2.1× from the standard base rate. These charges originate from the underlying telephony provider's pricing and will be applied to your account in accordance with your agreement and the applicable rate card. By enabling the capability, you acknowledge and accept these charges.

 

To enable AI features for Amazon Connect Customer in Salesforce Voice with Amazon Connect, see a help article in an upcoming email communication prior to Winter ’27.

 

Billing acknowledgement: By choosing to manually enable this feature set, you are explicitly opting in to the service and agreeing to the associated 2.1x increase in usage costs.

 

Summaryimage.pngWe apologize for any confusion caused by this upstream change from Amazon. We remain committed to ensuring that you have full control over your environment and your budget.

 

If you have any questions, require assistance assessing Amazon Connect Customer features, or want to discuss how this impacts your current configuration, please reach out to your Salesforce Account Executive or contact Salesforce Support. For additional information, review this Help Article.

 

Thank you for your continued partnership. 

 

#Service Cloud Voice

1 件のコメント
0/9000