For most bots, storing state refers to the information that a bot retains during a conversation to provide continuity and context. It includes details such as where the conversation left off, user preferences, and previously gathered inputs.

UI Builder lets you store data into two distinct scopes: short-term and long-term scopes.

Short-term Scopes

Short-term scopes store temporary data, typically relevant only within a single session or conversation. Once the session ends, this data is lost. These are useful for short-term tasks such as processing logic or capturing information as part of a conversation.  The short-term scopes available in UI Builder are:

• This - Data stored in this scope is associated with the current action or activity
• Turn - Data stored in turn scope is associated the current turn
• Dialog - Data stored in dialog is associated with the active dialog and stored until the dialog ends

Long-term Scopes

Long-term scopes store information across multiple interactions, allowing the bot to remember users and provide personalized responses over time. These are useful for user, or conversation level data that you want to store. The long-term scopes available in UI Builder are:

• Conversation - Data stored in conversation scope is associated with the current conversation between the user and the chatbot. The data is stored until the user exits the conversation or the chatbot is refreshed.
• User – Data stored in the user scope is tied to the user and persists across multiple conversations. When a conversation is initiated, Zammo assigns a unique user ID to the user’s device. This allows previously stored data to be retrieved in future interactions, enabling a more personalized and context-aware conversation. You can see this in the captured analytics:

Below is an example of conversation design where the user’s age is captured and assigned to a user **scoped variable: