Amazon Connect after 3 years of use for voice and WhatsApp
Use Cases and Deployment Scope
We started using Amazon Connect for voice 3 years ago, through an IVR with different flows, some of them with automations integrated with our core systems, and others scaliting to agents. 1 year ago we added WhatsApp, using text with flows connected to different AWS services as Amazon Lex. Both channels are focused for customer service, and developed trying to optimize the selfservice. After 3 years of use, we have more than 60% of the contacts automated and confirmed the resolution by the customer, and around 20% attended by an agent. Our goal is to continue improving the selfservice, reducing the agent's contact, and aligned with the business goals of impriving the customer experience and reducing the call center cost.
Pros
- Selfservice flows
- Integrations with third party systems
- Integrations with AWS services as Amazon Lex, Lambdas, S3, etc.
Cons
- CCP (Contact Control Panel) Amazon Connect for agents very basic
- Automated outgoing calls
- Omnichannel to attend voice and text by the same agent
Likelihood to Recommend
Best features:
Easy to set up, with a few steps you can start attending customers. For a basic use, you don't need to know programming, with a few customizations it can be ready.
Easy to mantain, even the end user with a basic training, can change texts and options with a drag and drop system.
Easy to integrate.
Needs improvement:
Complex contact center features not included, needs development
Poor analytics, specific KPIs need to be developed out of Amazon Connect