Option 3: Ingress to Amazon Connect and egress to Avaya for agent transfer

1. A customer calls the Amazon Connect contact center. Amazon Connect greets the customer with welcome menu and provides the caller with self-servicing menu options.

2. Amazon Connect uses an AWS Lambda function to create a customer record in an Amazon DynamoDB database instance by using the UCID as a primary key.

3. Amazon Connect initiates Amazon Lex to start self-servicing the call.

4. Amazon Lex invokes a dialog code hook and fulfills the intent by using a Lambda function.

5. The Lambda function inserts all of the customer attributes during the call and starts the routing process back to Avaya as follows:

   1. Amazon Connect makes an API call to Amazon API Gateway.

   2. Amazon API Gateway starts a Lambda function that queries the Amazon DynamoDB database instance and fetches a DNIS outbound dialing number for Avaya. It blocks the DNIS number and passes the dialing number back to Amazon Lex.

   3. Amazon Lex passes the number back to Amazon Connect in session attributes.

6. Amazon Connect uses this number to dial back to Avaya.

7. Avaya makes an API call to Amazon API Gateway.

8. Amazon API Gateway initiates a Lambda function that fetches the customer attributes associated with this DNIS number and frees up the dialing number for future use.

9. Avaya routes the call and the customer attributes to the agent.

Advantages of this architecture

• No additional hardware or licensing is required for Avaya.

• No additional telephony lines are required because calls are direct to Amazon Connect.

Disadvantages of this architecture

Disadvantages of this architecture

• After the call is transferred to Avaya, you continue to be billed for voice service charges and telephony charges in Amazon Connect because the customer called Amazon Connect directly.