- Newest
- Most votes
- Most comments
There appears to be a misunderstanding in your question. The scenario you're describing - integrating an Azure bot with AWS services like Lambda and Amazon Connect - is not a standard or supported configuration based on the information available.
The sources provided discuss Amazon Lex, which is AWS's own chatbot service, and how it integrates with other AWS services like Lambda and Amazon Connect. There's no mention of Azure bot integration with these AWS services.
If your goal is to create a chatbot that can route conversations to Amazon Connect agents based on intent, you would typically use Amazon Lex as the bot service, not Azure Bot. Here's a general approach using AWS services:
- Create an Amazon Lex bot with the necessary intents and utterances.
- Use AWS Lambda functions to extend the bot's functionality if needed. Lambda can be invoked at various stages of the conversation, such as after intent recognition or during intent fulfillment.
- Integrate the Lex bot with Amazon Connect. You can add the bot to your Amazon Connect contact flow.
- Set up an "Agent" intent in your Lex bot. When this intent is triggered, you can transfer the conversation to a human agent in Amazon Connect.
- Configure your contact flow in Amazon Connect to route the chat to the appropriate queue based on the intent information from Lex.
If you specifically need to use Azure Bot, you would likely need to create a custom integration between Azure and AWS services, which would be a complex undertaking and is not a standard configuration. In that case, you might need to explore custom API integrations or use a third-party service to bridge between Azure and AWS.
Sources
Amazon Connect - Self service chatbot | AWS re:Post
Attach an AWS Lambda function to an bot using the console - Amazon Lex
Creating an AWS Lambda function for your bot - Amazon Lex
Integrating an AWS Lambda function into your bot - Amazon Lex
Hello,
As mentioned in the above suggestion, I would recommend you to use Lex bot with Amazon Connect for your use case. However, if you still wish to use Azure bot with Connect then I would request you to kindly reach out to AWS Support with the detailed implementation of Azure bot and the APIs that can be used to access the intent in Lambda which can be invoked in the Connect contact flow and post that interaction can start.
