Botmaker 3.0 includes a conversational memory similar to that of assistants like Claude or ChatGPT: the bot remembers what was said throughout the conversation without you having to explicitly tell it to store each piece of data. In addition, the required data you define in each Funnel state is saved and available for the following steps. Variables still exist, but their role changes: they're used mainly for integrations and code actions.

You can:

• Rely on memory so the bot keeps the context without configuring manual storage.
• Collect specific information with the required data of each Funnel state.
• Use variables when you need to pass data to integrations or code actions.

Key concepts

Conversational memory: the bot's ability to remember what was said during the conversation, automatically.

Per-channel memory: the context is remembered within a single channel. The bot does not identify the same user across different channels on its own.

Required data: fields the agent obtains from the user in a Funnel state ("What data is required when reaching this state?" section). They're saved and available for the following steps.

Variables: values used mainly for integrations and code actions.

How to work with memory and data

Let memory carry the conversation

You don't need to configure steps to store what the user says: the bot keeps the context automatically during the conversation.

Collect data in the Funnel state

When a step needs information from the user, add it as required data in section 2 of the state. The agent will ask for it, and the data becomes available for the following states (for example, the name captured in "Data request" is reused later).

Keep in mind that memory is per channel

The bot remembers the context within the channel where the conversation happens, but it doesn't automatically recognize the same user if they write through another channel. To recognize them across channels, rely on an external system (CRM or spreadsheet) that uses a piece of data as an identifier.

Use variables for integrations and code actions

When a piece of data must be sent to an external system or used in a code action, handle it as a variable.

Note: as a general rule, let memory and required data handle the conversational part, and reserve variables for what must go in or out of external systems.

Remember to visit our Help Center for further information.