You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How might this work with persisted context? In real world, context will be persisted somewhere in a redis database. This means that as of now, the mapping will have to be relied upon the skill name.
Also, when a followUp flag is set, should the response automatically be marked final or can multiple skills mark their own followUps? How will this scale to multiple responses?
Potentially, upon a multiple response to multiple followups, the bot could split the response into a stack and then pass the response one by one to each of the followup skills who can then decide what to take off of the stack.
How can a skill release a follow-up? Think about the following conversation:
YOU:[1]> I'd like to make a payment
BOT:[2]> Sure! What's your payment method? <----------- Lock acquired
YOU:[3]> You know what, nevermind.
BOT:[4]> No problem <----------- Lock naturally released
Here the natural locking works quite well. However, it does not for the following:
YOU:[1]> I'd like to make a payment
BOT:[2]> Sure! What's your payment method? <----------- Lock acquired
YOU:[3]> Actually, what's my balance?
BOT:[4]> It is £350.00. <----------- Lock manually released, sentence gets re-evaluated.
Special flag in context to be set followUp mapped to a skill name.
This also means that each skill needs a unique name before it can be added to the bot.
The text was updated successfully, but these errors were encountered: