Skip to content

Commit 5185304

Browse files
author
Justine Jones
committed
small read me tweeks
1 parent 0056d12 commit 5185304

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
## Introduction
55

6-
amazon-connect-custom-ccp provides a way to build a custom ccp dashboard for your Amazon Connect contact center. These instructions focus on how to use the software to create a ccp dashboard. This dashboard will display:
6+
`amazon-connect-custom-ccp` provides a way to build a custom ccp dashboard for your Amazon Connect contact center. These instructions focus on how to use the software to create a ccp dashboard. This dashboard will display:
77

88
- A banner to indicate if a call is priority. This is set by a field in the API response when an agent connects to a call.
99
- A section with the queue name, broker code and account name. This can be changed to suit the needs of your project
@@ -12,13 +12,13 @@ amazon-connect-custom-ccp provides a way to build a custom ccp dashboard for you
1212
- A button that will open a stats modal.
1313
- Stats modal displays daily call intent selections for the agent and daily queue stats (active agents, number of missed calls, number of customers in queue, longest wait time and average time in queue)
1414
- Cold transfer functionality (transfer to queue, quick connect or external number)
15+
- Update intent and secondary intent modal. At the end of a call, when an agent selects an intent and a secondary intent. This information is added to the agent table in Dynamo DB and is updated on the contact trace record on Amazon Connect.
1516

1617
First, you will need an Amazon Connect instance up and running. Next, you will need to deploy the CDK which will build the Lambda functions, DynamoDB table, API Gateway, S3 bucket, Cloudfront distribution and SQS queue components for you.
1718

1819
The DynamoDB table holds data that will be displayed on the dashboard such as, a list of possible call intents, and intents selected by the agent during the call). You can also collect historical and real-time data from multiple Connect instances. If you wish to collect agent events from multiple Connect instances you will need to configure Kinesis to deliver the events to Lambda manually (which will be processed by the agent event handler).
1920
The S3 bucket contains the React build and will be served from CloudFront.
2021

21-
At the end of a call, when an agent selects an intent and a secondary intent. This information is added to the agent table in Dynamo DB and is updated on the contact trace record on Amazon Connect.
2222

2323
## AWS CDK stack to deploy Amazon connect CCP
2424

0 commit comments

Comments
 (0)