AWS re:Postを使用することにより、以下に同意したことになります AWS re:Post 利用規約
AWS re:Postre:Post

Lex v1 chatbot integration with connect

0

I have a lex v1 chatbot which has a SpeakToAgent intent. I want to be able to connect with a customer agent using amazon Connect whenever a user uses this intent. All my other intents work as expected for this chatbot.

I have created users, a queue, routing profile and a flow in my connect instance. I have also added my classic v1 bot in the connect instance and specified it in the get-customer-input block in my flow. Upon logging in as a customer support agent in aws connect and triggering the SpeakToAgent intent on my chatbot, I don't see any notifications pop up. I do not see any errors either and nothing shows up in the Connect Cloudwatch logs so I am guessing the connection from my Lex bot to Connect is not working.

Do I need to create a lambda for the SpeakToIntent lambda or inject any code anywhere? I didn't see anything like that in the documentation.

I would really appreciate any help to get this thing working. Thanks a lot for your time!

トピック
機械学習と AIアプリケーション統合ビジネスアプリケーション管理とガバナンス
タグ
チャットボットAmazon ConnectAmazon LexAWS Chatbot
言語
English
aws_scholar
質問済み 1年前408ビュー
2回答
0

How are you testing your bot? When you say the other intents work, do you see them being routed to agents?

David

profile picture
dmacias
回答済み 1年前
  • aws_scholar
    1年前

    Thanks for the response! I am testing it in the lex console. By other intents working, I mean that the chatbot replies with the responses I have set and triggers lambda functions specified. Only the linkage with connect does not work. Do you see anything I might be doing incorrectly? Thank you!

  • aws_scholar
    1年前

    Thanks for your response David! I have tried testing the bot on lex console as well as hosting the bot on a local server using the cloudformation template provided in aws documentation. When I say other intents work, I mean that they are triggering lambdas and responding with messages as expected. The only issue I am having is that the messages are not being routed to aws connect. Do you know what might be going wrong?

0

Without seeing your config nothing stands out. The fact that some intents work and other don’t tells me it’s a configuration issue on your end. Are you using slots already used in other intents which might be causing your new intents to never be selected? I’m just guessing here.

David

profile picture
dmacias
回答済み 1年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ