Memory by use case
AI memory for sales copilots
Every call starts where the last one ended.
Why memory matters here
Deals run for weeks across calls, emails and several people on both sides. The details that close them are small: who signs, what worried the finance lead, which date was promised. A copilot with memory can brief a rep in a few lines before each call, and keeps that knowledge when the account changes hands.
Who a memory belongs to
One memory per account and deal, shared by the selling team, alongside the customer record it is drawn from.
The moment it shows
Before a call the rep gets three lines: the open objection, the promised follow-up and the name of the new stakeholder.
What to remember
- Who is involved, their role and what each one cares about.
- Objections raised and how they were answered.
- Commitments and dates from both sides.
What to forget
- Personal remarks that have no place in a business record.
- Prices and terms from offers that were withdrawn.
- Contacts who have left the company.
See recall before you build it
Add a few facts from your own use case and ask a question.
Sales copilots: common questions
Does agent memory replace the CRM?
No. The CRM stays the system of record. Memory is the short working summary an assistant reads from it and from recent conversations.
Who should be able to read a deal memory?
The same people who may read the account in the CRM. Memory should inherit those permissions, not get around them.
Other use cases
Tutoring and learning
A tutor that remembers what you got wrong last week.
What to rememberHealth and wellness coaches
Continuity for habits, with care about what is kept.
What to rememberResearch agents
Long investigations that survive a full context window.
What to rememberGame characters
Characters that remember what the player did to them.
What to rememberPack the doko. Ask it anything.
Nine memories, one question, no account. See which facts an agent would carry into its next answer.