Pega IVR IVA integration with AWS
|Request to Publish|
|Description||Pega IVR IVA integration with AWS|
|Version as of||8.5|
|Capability/Industry Area||IVR IVA Channel|
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.
When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
Pega IVR IVA integration with AWS
IVR IVA: Using the IVR-IVA (Interactive Voice Response – Intelligent Virtual Assistant) API and channel configuration, Pega Customer Service delivers customer self-service over Interactive Voice Response (IVR) systems.
Create the IVR-IVA channel to configure the Pega Intelligent Virtual Assistant (IVA) for the Interactive Voice Response (IVR) systems. Using the IVR-IVA channel, customers can interact with Pega Customer Service over different IVR systems for self-service.
End user calls to contact center, Amazon Lex finds the intent and utterance from user response.
AWS lambda integrates with Pega platform using IVR IVA Api call by sending the utterance and event name. Pega uses the utterance and event name to process the api call and sends the response back to AWS.
MCP: Multichannel case processor (MCP) framework purpose is to speed up implementation of Pega applications that interacts with user leveraging integration with third party communication channels.
Create the following assets in Pega and AWS to support the IVR IVA
Create IVR IVA channel
1. Create IVR-IVA channel.
2. Add case commands in your IVR-IVA channel so that it creates cases in the Pega Customer Service application based on related user input, in the Content section, click Add caste type and define a case command. The IVR-IVA channel detects the case type by using text analysis and automatically creates the case.
3. In the connect tab, select the Template operator ID of an existing Pega Customer Service operator.
IVR-IVA API is an API that any modern IVR system can use to exchange data with Pega Customer Service. The IVR-IVA channel parses the events or user inputs from the API to execute the corresponding actions. The IVR-IVA channel supports the four out-of-the-box events supported by the IVR-IVA API by default. When an IVR system sends an event notification to the API, the IVR-IVA channel executes the corresponding channel action, such as gathering contact details against ANI or running a case type.
Sample Payload for run_case event:
"case_key": "PEGACPMFS-WORK-SERVICE M-58322",
"interaction_key": "PEGACA-WORK-INTERACTION I-32221"
"content": "What type of manifestation"
In the response sending the Next question which is configured in IVR IVA flow in service case.
Additional details regarding IVR IVA API,
Create IVR IVA Flow
Create IVR IVA process flow in customer service case type.
Create the flow and configure the questionnaire to process the IVR IVA conversation.
Create CTI Link
Create Pega CTI link to connect from AWS to Pega interaction portal to support transfer to agent queue scenario.
1. Open Pega CTI call
2. Add CTI Link, create the AWS Connect implementation
amazon connect as Agent profile for login setup.
Transfer to agent work queue:
To receive the call from IVR connect to CTI Link and login into Pega.
· Login as CSR and Launch the interaction portal
· Click on phone login in the right top corner.
· Select the CTI link as AWS connect and login, successful connection will enable the phone icon into green. Now agent is ready to accept the incoming call.
To support IVR IVA from AWS, we need to create the below amazon assets.
Amazon Connect is an omnichannel cloud contact center. Create contact flows which defines the customer experience with your contact center from start to finish. Amazon Connect contact flows integrate with Amazon Lex and provide text to speech and can enable natural language-based self-service interactions.
Please follow the below to support the IVR IVA interaction to create the service case creation in Pega and transfer to agent scenarios
1. Claim a phone number in order to receive and make calls.
Note: Once the contact flow created, add that to phone number under Contact flow/IVR
2. Set hours of operations if required
3. Create queues to route to the agent
4. Create and define contact flow how a customer experiences the contact center from start to finish.
Lambda and Lex can be invoked from contact flow,
· Can invoke AWS lambda function, which makes a call to AWS Lambda and optionally returns key/value pairs, which can be used to set contact attributes
· Can invoke the Amazon Lex intents from Get customer input
5. Create routing profile and add that to routing profile queues.
6. Configure users and select the above created routing profile and select the security profile (amazon supports default security profiles, if required create new).
· Amazon Lex is an AWS service for building conversational interfaces for applications using voice and text
· Build Lex bot to automatic speech recognition (ASR) for converting speech to text, and natural language understanding (NLU) to recognize the intent of the text.
· create Lex bot, specify the basic conversation flow in the Amazon Lex console. Amazon Lex manages the dialogue and dynamically adjusts the responses in the conversation. Using the console, you can build, test, and publish your text or voice chatbot.
Create custom bot for specific scenario, AWS also support sample bots for couple of scenarios.
Create a custom Lex bot and configure it with one or more intents that you want to support. Configure the bot so it understands the user's goal (intent), engages in conversation with the user to elicit information, and fulfills the user's intent.
Note: We can configure the Lambda function under Fulfillment (business logic required to fulfill the user’s input) or Initialization and validation (validate the user’s input) with in Lex bot.
Build the bot, publish a version and create an alias.
· Create the Lambda function and write the code to integrate with Pega platform using Pega API call.
· Write Lambda functions in your favorite language (Node.js, Python, Go, Java etc).
Under configuration tab, write your code in Function code. Deploy the code and test.
Your function should call the relevant API as indicated in https://community.pega.com/knowledgebase/articles/pega-customer-service-implementation-guide/85/ivr-iva-api with the appropriate request input, then handle the response and pass the relevant information back to the contact flow.
Note: Monitor the logs in Cloud watch.
AWS access and permissions
In AWS there are certain access and resource permissions that are required to be set in order for Amazon Connect to access Amazon Lex and Amazon Lambda. Please refer to the Amazon documentation on IAM: https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
Enter your topic description
Describe what you try to solve with this design pattern.
Use case examples
Provide a business example to help users understand the objective.
Before you begin
Is it necessary to plan anything in advance, or are external steps using other tools required to achieve the goal? If any specific configuration procedures (how-tos) exist on Pega Community pages, you can link to those assets here by providing the URL.
Process/Steps to achieve objective
What do individuals need to know to achieve the outcome? What do individuals need to know to achieve the outcome? Enter the precise steps to guide the user to achieving the desired outcome. Remember to always state where in the software the user must perform an action, before giving the action.
If “How To…” documents exist for specific configuration procedures please link (using the url) to those assets on the community **
What do you expect the user to see or be able to do after they complete this design pattern?