28 Oct 2024: Journey interaction timeouts

Neelke Stadler Updated by Neelke Stadler

Change the interaction timeout of a journey from the default 5 minutes to what is suitable for your audience.

Journeys have a timeout value to prevent people from getting stuck on your chat service. The default timeout is 5 minutes. This means if a user takes longer that 5 minutes to respond to a request for input, the journey will expire. There might be a very good reason to give users more than 5 minutes to respond. Customising the interaction timeout is now simple.

Change the timeout per journey

When you open any journey, note the floating settings panel on the right. The 5 minute default is shown, allowing you to customise the value as needed. If a user is inactive for longer than the indicated time, the journey will expire.

For avid code block users: This is the interaction_timeout() functionality made visible to no-code users. If you already set that in your code, we’ll automatically use that value — no update needed from your side.

Was this article helpful?

05 Nov 2024: Seamless handover between a human and a bot

28 Oct 2024: More roles and better permissions

Contact