Guidance for Post Call Analytics on AWS
Overview
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Operational Excellence
Data, such as speaker sentiment analysis and how well a customer’s internal compliance rules are met, is used to identify how effective contact center agents are at handling customer calls. The same data identifies the topics and entities discussed in the call. All of this data can be visualised in QuickSight to help business analysts identify trends from a customer’s perspective and potential training needs for agents.
Security
All data is encrypted both in motion and at rest, and can use customer-controlled AWS Key Management Service (AWS KMS) keys for this encryption. The solution is entirely serverless, but the AWS Lambda components can optionally run within a customer’s VPC, accessing external services such as Amazon Transcribe and Amazon S3 only through a customer’s approved endpoints.
Reliability
The solution is entirely serverless, and each of those services (Amazon Transcribe, Amazon S3) operate using multiple Availability Zones in a resilient fashion.
Performance Efficiency
The solution scales usage of its serverless components as it needs to, both up and down, in order to handle the concurrent processing of potentially thousands of calls or those times when there are no pending calls to process.
Cost Optimization
The solution only uses serverless components when there is an active call audio file to process, minimizing the incurred costs as much as possible. If required, the original audio files can be archived to lower cost long-term storage on a customer-specified schedule in order to minimize storage costs.
Sustainability
By using managed services and dynamic scaling, we minimize the environmental impact of the backend services.
Related content
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages