Introduction
Memory lets Bland agents remember callers between conversations, creating more natural and human-like interactions. When a caller returns, your assistant can reference details from previous calls without needing the user to repeat themselves. Key capabilities include:Persistent Context
Bland automatically links users by phone number or memory ID and recalls their prior interactions.
Multi-Session Awareness
Keep conversations coherent across separate touchpoints or campaigns.
Personalized Responses
Store metadata and summaries for more tailored conversations.
Simple Setup
Enable memory from the UI or API — no custom logic required.
Real-World Example
Imagine a healthcare provider running two campaigns:- Medication Adherence — Bland checks if patients are taking their medication.
- Wellness Program — Bland invites patients to enroll in a new service.
Memory Overview
Memory in Bland is managed through Memory Stores, which are collections of user records and associated data. Each record can include:- Phone Number (used to match users)
- Metadata (freeform user info)
- Previous Call Summary (short recap for LLM context)
- Memory ID (optional — for grouping conversations across a campaign)
Setting Up a Memory Store
To create a memory store:- Navigate to Memory Stores in your Bland workspace.
- Click Create New Memory
- Provide a name for your memory store (e.g. “Customer Support”, “Outbound Wellness Campaign”)

Inserting Users and Metadata
Once you’ve created a memory store, you can optionally add user records:- Select a store and click Insert
- Enter the user’s phone number (required)
- Optionally, include:
- Metadata: Any persistent info like “21-year-old male from New York”
- Previous Calls Summary: A freeform summary of prior interactions

Attaching Memory to a Call
To enable memory for a call:- Go to the Send Call page to create an outbound call
- Under the Knowledge header, select a memory store from the dropdown

Optional: Use Memory IDs in API
To group calls by context or campaign, pass amemory_id
field when making an API request to /v1/calls
. This allows you to isolate memory usage within a subset of calls.
This is useful when the same user appears in multiple use cases (e.g. Support vs Sales).
Learn more about our memory API here.