2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
How are you testing your bot? When you say the other intents work, do you see them being routed to agents?
David
con risposta un anno fa
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
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
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!
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?