Is your feature request related to a problem? Please describe.
The Timeout Flow Feature is hard to access or come by (non-intuitive) as it is completely hidden in the interface, like an easter-egg. A user may only know of its existence by discovering it through reading aimlessly through the documentation. This is the same for the Conversation End flow.
It's also frustrating to handle conversations where users timeout and he's redirected to the beginning. It feels like it's not in the flow.
Describe the solution you'd like
The existing solutions need in-product discovery, because no one thinks this might exist.
The most expedient way would be to add a timeout node in all starter templates with text like "Whoops, you've timed out. Sending you to a new user session.".
Describe alternatives you've considered
Always enforce a Timeout flow and optionally a timeout node in a chatbot.
Is your feature request related to a problem? Please describe. The Timeout Flow Feature is hard to access or come by (non-intuitive) as it is completely hidden in the interface, like an easter-egg. A user may only know of its existence by discovering it through reading aimlessly through the documentation. This is the same for the Conversation End flow.
It's also frustrating to handle conversations where users timeout and he's redirected to the beginning. It feels like it's not in the flow.
Describe the solution you'd like The existing solutions need in-product discovery, because no one thinks this might exist. The most expedient way would be to add a timeout node in all starter templates with text like "Whoops, you've timed out. Sending you to a new user session.".
Describe alternatives you've considered Always enforce a Timeout flow and optionally a timeout node in a chatbot.