The Session Management section exists on some Endpoints. Here you can set the session expiration in order to let your users start a new sessions with your Flow.
You can configure session management for endpoints individually in the Endpoint Editor you reach by clicking on your Endpoint in the Endpoints section of the left-hand project navigation pane.
This setting sets the expiration of a session on an Endpoint. This is useful for some Endpoints, e.g. Facebook Messenger, where there are no natural sessions, because the entire conversation is one chat. However, you still might want your users to enter a new session once in awhile, e.g. to start a new flight booking when they return to the chat after some weeks. In order to achieve this, you can set the session expiration in your Endpoint. This defines the amount of minutes of inactivity the Endpoint allows before a new session is created, meaning that if your user doesn't say anything for e.g. 30 minutes, then they will get a new session.
It is important to expire sessions once in awhile to give your users the chance to talk to your Flow from the beginning on again, and in order to have multiple conversations in the Contact Profile.
It is possible to prevent the sessions from expiring, in case your Flow e.g doesn't store anything in the context that needs to be reset. To do this, you can simply set the session expiration to 0. However, note that all of your Contacts will then only have one conversation with your Flow in their Contact Profile.
The following Endpoints support session expiration:
- Facebook Messenger
Default Session Expiration
The default session expiration is set to 30 minutes.
Organisation-wide Session Expiration
It is possible to configure a default session expiration the organisation. If this is the case, then setting a higher session expiration in the Endpoint than is configured for the organisation will have no effect. The organisation-wide session expiration can be configured in the Management UI.
Updated almost 3 years ago