A bot sometimes needs to
  • Remember information the user provided minutes ago
  • Personalise the same response to 2 users differently
With contextual information like Memory, User Attribute, and NLP Attribute, a bot makes smarter decisions to find a Passing Rule.


A group of user interactions with your bot that take place within a given time frame. A single session can have multiple messages, button clicks, and transactions. A single user can have multiple chat sessions with your bot, which can occur on the same day or over several days, weeks, or months. By default, a session expires after 10 minutes of inactivity. You may customise your bot's session length on the Personality page.
Changing Session Length affects the Time Spent and Sessions stats


A temporary variable used to store additional information about a chat session. It is used to remember topics and values that the user was talking about in the current session. It can be accessed in the bot's responses with the merge tag {{}}.
Here's an example of memory property usage
User: How much is the large pepperoni pizza? Bot: The large pepperoni pizza is $29.90 Bot stores a memory property: item-requested, value: pepperoni pizza ------------- User: How about the small one? Bot remembers "pepperoni pizza" from the item-requested memory property Bot: The small pepperoni pizza is $19.90
Memory properties are ALWAYS hyphenated (kebab-cased), so item-requested is a valid memory property ✅ but item_requested is NOT ❌
When your session expires, your bot forgets its memory context (i.e. all its memory properties)

User Attribute

A permanent variable used to store custom information about a user messaging your bot. The user context (i.e. all user attributes) can be accessed in User Profiles. It is used to keep track of long-term custom fields like preferences, survey answers, access levels, and transaction activity. It is essential for customer segmentation, which in turn allow you to create personalised chat experiences and targeted broadcasts. It can be accessed in the bot's responses with the merge tag {{user.attribute_name}}.
User attributes are ALWAYS underscored (snake_cased), so user_address is a valid user attribute ✅ but user-address is NOT ❌

NLP Attribute

A derived variable from connected Artificial Intelligence (AI) integrations. You may connect any number of AI integrations like Dialogflow and After adding at least one AI integration, every message sent to your bot will be forwarded to the AI integration. The AI integration will derive intents, traits, and entities and store it in the NLP context (i.e. all NLP attributes). It can be accessed in your bot's responses with the merge tag {{nlp.attribute_name}}.
NLP attributes are ALWAYS underscored (snake_cased)


A static global variable for your bot, which can be used in any response in every chat with every user. Shortcuts are declared on the Personality page. It is useful for text-replacements like on iPhones and Androids, and also for storing environment variables for Developers. It can accessed in a conversation with the merge tag {{bot.shortcut_name}}.
Shortcuts are ALWAYS underscored (snake_cased)


A way to dynamically modify contexts during a session. You can add actions in stories, and they will modify one of 4 contexts: memory, user attributes, user tags, and shortcuts. An action has 3 parts to it: a property, a function, and a value.
From our example above, we can create a story with one action
set to
pepperoni pizza
The interaction in our example will look like this
User: How much is the large pepperoni pizza? Bot: The large pepperoni pizza is $29.90 Bot stores a memory property: item-requested, value: pepperoni pizza
An action has a lifespan.


The number of messages for which a new memory property from an action remains active. The default lifespan of a memory property is 1. This means that the bot will remember that you stored the new memory property item-requested for 1 more message from the user. After the user replies with 1 message, item-requested will be removed from the memory context automatically. The 3 most commonly used lifespans are
Remembers the property for 1 more message
Direct answers from users, e.g. Yes/No Questions
Remembers the property for the entire period of the chat session
Session-wide topics, e.g Browsing subtopics
Remembers the property for the current message
Intermediate values for subsequent actions or rules, e.g. Variables for Mathematical Calculations
Only Memory Properties have customisable lifespans. User Attributes are stored permanently. NLP Attributes have a fixed lifespan value of -1


A block of JavaScript code used in conditions and actions. It is used within a condition for comparisons, or within an action for assignments.


An API request made to an external software. There are 2 methods available - GET and POST . It is used to collect and update dynamic information in your custom technology infrastructure or integrations, and to pre-populate responses, quick replies, and modify memory and user contexts.