Memories are collected automatically by the agent during conversations. You define what to collect and how—the agent handles extraction and storage on its own.
How Memories work
You create Memory Configurations, each of which defines:- A name and goal (what this configuration is trying to learn)
- One or more fields (the specific data points to capture)
- The channels where this configuration is active
You can create up to 10 Memory Configurations per agent.
Creating a Memory Configuration
Create a new configuration
Click New Configuration and give it a descriptive name (e.g.
User Profile) and a goal that guides the agent (e.g. Capture the user's name, company, and role to personalize future interactions).Add fields
For each piece of information you want to capture, add a field with:
- Field name — what you’re collecting (e.g.
full_name,company,email) - Data type — text, number, date, or boolean
- Prompt instructions — how the agent should extract this field (e.g.
Extract the user's full name if they introduce themselves or sign off)
Assign channels
Select the channels where this memory configuration should be active. The agent will only collect memories on conversations happening through those channels.
Field types
| Type | Description |
|---|---|
| Text | Free-form string (name, company, preferences) |
| Number | Numeric value (age, account ID, order number) |
| Date | Date value (last purchase, renewal date) |
| Boolean | True/false flag (is a premium user, opted in for updates) |
Viewing collected memories
You can see the memories collected for any specific user from the Contacts section. Open a contact and view their stored memory fields under the memory tab.Key notes
- Memories are stored per user, per agent—different agents maintain separate memory stores.
- If a user provides conflicting information in a later conversation, the most recent value wins.
- Memories are only collected on the channels assigned to each configuration.
- You can edit or delete configurations at any time without affecting previously collected data.