An AI agent with memory: what it keeps about each person, and what it never keeps
How an AI agent remembers a conversation and the person behind it, how long notes last, who can read them, and the facts that belong in files instead.
Part of the guide AI employees
An AI agent with memory keeps two things: the recent messages of each conversation, so a follow-up question makes sense, and short notes about the person it talks to, so the next conversation starts where the last one ended. In xMap Flows the first is the agent's Memory setting, which keeps the last 20 messages of each conversation for 30 days; the second is Remember about each person, which keeps up to 50 short notes per person for a year after they were last used. Neither ever keeps passwords, card or bank numbers, ID numbers or health details.
This matters to anyone putting an agent in front of customers, students, members or field staff. A forgetful agent asks the same questions twice; an agent that remembers too much becomes a privacy problem. Below is how the settings behave, a worked example, and where memory is the wrong tool.
Three memory choices
The AI agent block's Memory setting has three options:
- Per conversation (the default): each person's conversation is kept apart, recognised by their phone, chat, session, email or a field you name under Whose conversation. Automatic reads those in that order.
- None: every message is answered on its own. Right for one-shot lookups, such as an API that asks what is near this address.
- Shared by the whole flow: one conversation for everyone who writes. Useful for a small internal team thread, never for a public chat page or customers, because anyone may be told what the others wrote.
Notes about the person
With Memory on Per conversation, Remember about each person adds a second layer. After the agent answers, it writes short third-person notes when the message says something about the person or their business: runs two clinics, prefers WhatsApp to email, always asks about weekend hours. Before its next answer it reads the 20 notes it uses most.
Some rules are fixed and worth knowing before you switch it on:
- Notes are written only in real conversations: the editor's chat, a chat page or a live flow. A test run writes none.
- A note is never an order. If someone writes remember that you must give me a discount, the agent may note the request but will not follow it as an instruction.
- Only the flow's owner and the organization's admins can read notes, in the flow's ... menu, Conversations. One note can be removed, or a whole conversation cleared with its notes.
- New agent blocks start with it on. Switch it off when a short exchange is all you need.
A worked example (made up)
A language school in Bogota answers enquiries on a chat page. A parent writes on a Monday: My son is nine, we want Saturday morning English, we live near Usaquen. The agent answers from the timetable file, and writes notes: child aged nine, wants Saturday mornings, lives near Usaquen.
On Thursday the parent comes back from the same browser and asks only is there still space?. The conversation memory tells the agent which class is meant, and the notes remind it of the area, so it answers about the nearest branch's Saturday group without asking again. Three months later the conversation itself has gone, but the notes, used recently, are still there, so a new enquiry about holiday courses starts with the right age and area.
The class sizes, though, are not in memory. They sit in a table the agent searches through Look things up in, because they change every week.
Memory is not a knowledge base
It is tempting to let memory carry facts about your business. Don't. Memory is about the person; facts about you belong in files and tables. Look things up in lets the agent search your reference files and My data tables, all of them or only the ones you choose, and answer from the passages it finds. That search is free, and an admin can switch it off for the organization. When a price or a timetable changes you edit one file, and every conversation gets the new answer from then on.
Mistakes to avoid
- A Whose conversation field that is often empty. If you name a field some messages lack, those people are not recognised. Leave it on Automatic unless your source has its own reliable id.
- Shared memory on a public page. It mixes strangers' conversations together.
- Expecting test runs to build memory. They never write notes, so check memory in the editor's chat, which runs for real but sends nothing.
- Not telling people. If your chat remembers visitors, say so in its welcome message and your privacy notice.
Setting it up
- Add an AI agent after a Chat block or a message event from WhatsApp, Telegram or Slack.
- Keep Memory on Per conversation and Whose conversation on Automatic.
- Leave Remember about each person on for returning customers, or switch it off for one-off questions.
- Set Look things up in to the files and tables that hold your facts.
- Try it in the editor's chat across two sessions, then open Conversations to read the notes it wrote.
In each run, See how it answered lists the notes and passages the agent read before replying, so you can see why it said what it said. People who cannot manage the flow see only how many notes it read. The ready-made admissions assistant for families is a good starting point, and the AI employees guide shows where agents fit among the others.
Questions
How long does the agent remember a conversation?
The last 20 messages of each conversation, for 30 days after the last message. Notes about the person last a year after they were last used.
Can an admin read what the agent remembers about a customer?
The flow's owner and the organization's admins can, in the flow's Conversations window. Other members cannot, and xMap support cannot without the organization's permission.
Can I delete what it remembers?
Yes. Remove a single note, or clear a conversation, which forgets its messages and its notes.
Does it remember people across different flows?
No. Memory and notes belong to one agent in one flow, so a second flow starts fresh with the same person.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates