Skip to main content

#SCV0 discussing

With service cloud voice the OOB callback option  system pushes the callbacks to the available agent on priority before the normal calls , our requirement is to let agent control when they want to initiate/act on a callback request  rather then the system pushing the callback request to the agent as soon as they become available. is this configurable OOB in SCV or we need some to implement some custom solution . Has anyone implemented a custom callback solution would be curious to hear the challenges faced. #DSOfficeHours #Service Cloud #SCV

2 answers
0/9000

Hello Service Cloud Voice Team,

 

We plan to implement Service Cloud Voice (SCV) with Amazon Connect.  We have yet to find any good salesforce documentation that talks from end to end, both from Salesforce and Amazon.  It will be helpful if any of you share your experiences & reference blogs that talk about Service Cloud Voice with Amazon Connect implementation. #SCV #AWS

3 comments
  1. Feb 15, 2023, 2:30 PM

    @Peter Jones I also found the Quip docs in the Partner Learning Camp module 'Dive Deeper with Service Cloud Voice' really useful - if an updated/extended version of that could be made widely available, that would be super helpful as it covers in detail the setup for the OAuth / Connected App that I couldn't find in the official docs.

0/9000

The AWS account spun up from SCV is pretty restricted in terms of the additional services which we can install in that account. Is there a document outlining the services which are not allowed in an SCV AWS account ? For example, we tried to install an Elastic Search service in the AWS account and got this error, 

=======================

Error: User: arn:aws:iam::XXXXXXXXXXXX:user/IAMLogin is not authorized to perform: es:DescribeElasticsearchDomain on resource: arn:aws:es:ap-southeast-2: XXXXXXXXXXXX:domain/emite-kinesis-connect with an explicit deny (Service: AWSElasticsearch; Status Code: 403; Error Code: AccessDeniedException; Request ID: 0a993fef-0c74-4283-9ec7-46604ace93f5; Proxy: null) IAM user or role experiencing the issue: arn:aws:iam:: XXXXXXXXXXXX:user/IAMLogin

=======================

 

The IAM user who performed the install, is a Full Administrator in that AWS account. Is there a way to get around this account restrictions ? 

0/9000

Using SCV with Amazon Connect.  It has been working for all agents with no issues.  Today 1 agent is now not receiving inbound calls but all other agents are.  Anyone know what might affect just one agent?  I can see all my agents in available in Connect Real Time reports, but she doesn't show up at all.  So for some reason this one agent's SF is not communicating with Connect at all.

Thanks

Sarah 

5 comments
  1. Mar 12, 2021, 2:45 PM

    Glad it worked. Sometimes, reboot helps.

    I used to remove and add the users back to the contact center in Salesforce. This helped me in the past. 👍

0/9000