Guidance for Intelligent Insurance Assistant Using Replicated Mainframe Data on AWS
Overview
This Guidance demonstrates how to implement an intelligent conversational AI chatbot that uses insurance policy, billing, and claims data from mainframe applications to receive and deliver responses using natural language. With change data capture (CDC) technology, the data is replicated from the mainframe application to AWS using low-latency, high-throughput data pipelines. The conversational AI application then reads the replicated data from the AWS data stores and provides responses to customer inquiries, such as claim status, policy status, and next premium due dates, in natural language. This Guidance can enhance your customer’s experience, reduce call center volume, and optimize your operational costs. While tailored for the insurance industry, the underlying technology used throughout this Guidance can be adopted for other industries requiring mainframe data integration on AWS.
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.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages