Back to All

Disable Global Connection on Await Response

My current bot operates largely through global connections as opposed to individual connections within interactions.

Reason being for this is it is a teaching bot - that is answering people's queries on how to use certain tools/techniques. So I wanted to ability for the user to jump around to different topics easily without having to return back to a default interaction each time.

Problem is I wanted a Human takeover if the response didn't suit the users query, for the bot to ask for the query as a question, then basically say thank you and wait for a human user to answer the specific question --- unfortunately the nature of my global connections means that likely any question they have in response to the bot asking for their query will trigger a global connection and therefore override the await response function, and then respond with the answer they perhaps previously saw (which doesn't answer their question).

Is there a way I can overcome this without changing all the global connections back to individual ones?

Equally, is there any other downside (perhaps from an efficiency/speed) point of view in working mostly off global connections instead?