Legacy Dev Forum Posts

 View Only

Sign Up

Call Lex V2 Bot always ends up in Intent Fallback

  • 1.  Call Lex V2 Bot always ends up in Intent Fallback

    Posted 06-05-2025 19:04

    Fglawe | 2024-05-28 15:32:00 UTC | #1

    Hello, I am currently running in some issue while integrating Lex V2 with Genesys. In the bot itself, I have an intent plus the fallback intent. There is a “BookingNumber” slot in the intent (GetBookingNumber). In addition, a confirmation has been configured in the intent, i.e. when the user has made an entry, it is read out to him again and he should confirm it. If he confirms it, “end conversation” is called in the bot. (In the case of an integration with Amazon Connect, for example, this leads to the interaction being ended and the next step being executed in the flow). If I now call up the bot from Genesys, I am correctly asked for my booking number and also asked to confirm it. Afterwards, however, nothing happens (at least you don't hear anything anymore) after some time, the fallback intent is now triggered because no “input” was recognized. This can be seen from the bot's conversation logs.

    My question is, what information must be given from Lex or in Lex so that the “interaction” is completed and you can get out of the corresponding intent in Genesys?

    Thanks in advance FG


    system | 2024-06-28 15:32:04 UTC | #2

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 26500