Personalization
Open in CMSThe Agent Personalization screen declares what this agent may remember about the people it talks to. Anything outside that list is never stored. Found in the agent sidebar under Conversation → Personalization.
Master Switch
| Remember things about each person | Turns on memory for this agent. Off by default. Nothing is stored until you declare what may be remembered and the person has agreed to it. Everything else on the page appears only while this is on. Has no effect while the organization's Privacy Mode is on: no memory is captured at all. |
| Previous personalization mechanism warning | Shown only while the retired personalization mechanism is still on for this agent. Switch it off marks it to be switched off when you save. |
| Tabs | Configuration and Memory Fields. The master switch and the Save button sit outside both, because one Save commits the settings and the field list together. |
Configuration Tab
| Prompt Budget (tokens) | Required. The limit that actually binds: fields are trimmed by priority once memory exceeds it. Default 400, at most the organization's ceiling (the helper text shows it). |
| Confirm Before Storing | The agent asks the person before it writes anything down, rather than capturing it silently. Off by default. |
| Say Where It Came From | The agent says "based on what you told me earlier" when something it remembers shapes a reply. On by default. |
| Personalization AI Model | The model used to pick out declared details from what the person says. It runs only when a turn actually contains something declared. Defaults to Organization default. |
Memory Fields Tab
| Declared count | Shown as "n of ceiling declared"; the ceiling is the organization's field limit, at most 30. |
| Add field | Opens the New memory field dialog. Disabled at the field limit, with a note to raise the limit or remove a field. |
| Field | Label, key, and a summary line of type, retention and when it is included. Carries a core chip and a sensitive chip where applicable. |
| Purpose | The purpose sentence of the field. |
| Filled | How many people have a value for the field, with a progress bar and the number to review. No individual values are shown. |
| Action | Edit opens the Edit memory field dialog. Remove asks for confirmation: values stop being used immediately and are erased after a 30-day grace period. |
| Scheduled for deletion | Lists removed fields still inside the 30-day grace period, each with a Restore button. Declaring a new field with the same key replaces the removed one. |
Memory Field Dialog: Identity and Retention
| Key | Required. Stable identity, for example preferred_branch. Lowercase letters, digits and underscores, starting with a letter; must be unique. Changing it creates a different field. |
| Label | Required. Shown to the person this is remembered about. |
| Purpose | Required. This exact sentence is what the person is told, and it limits what the data may be used for. |
| Type | Text, Number, Date, Choice, Yes / No, or List. |
| Retention (days) | Required. After this, the value is erased; it cannot be unlimited. Default 180, minimum 1, maximum 3650. |
| Options | Shown for Choice and List. Comma-separated. Required for Choice (the value must match one of them); optional for List, where empty accepts any item. |
| Which items reach the prompt | List only: Most recently confirmed (default) · All of them · Closest to the conversation. |
| Items in the prompt | List only. How many reach the prompt, not how many are stored. Default 10, maximum 25. |
Memory Field Dialog: Activation and Policy
| When it is included | Always (default) · When the conversation mentions a keyword · When a particular tool is available · Only on request. On-demand is never injected; the agent fetches it only when it needs it. |
| Priority | Required. When the token budget is exceeded, the highest numbers are dropped first. Default 100. |
| Keywords | Comma-separated. Required when the field is included on a keyword. Plain word matching, not similarity search. |
| Tools | Comma-separated tool names. Required when the field is included when a tool is available. |
| How it may be captured | Only when stated outright (default) · May be inferred from context. |
| When the value changes | Keep the newest (default) · Keep the first · Ask before replacing. A correction the person made themselves is never overwritten by a guess. |
| Lawful basis | Consent · Necessary for a contract · Legitimate interest (default). Chosen by you as the controller, per field. Set to Consent automatically when you pick special category. |
| Sensitivity | Ordinary personal data (default) · Special category (health, beliefs, …). Disabled unless the organization allows special-category data. |
| Core field | Always included and never trimmed by the token budget. Cannot be combined with Only on request. |
| Show prominently | On by default. Gives the field its own place on the person's memory page rather than in the full list. |
| The person may correct it | On by default. The person can change the value themselves, and their correction is never overwritten by a guess. Every field always appears in their access view and export. |
| Cancel / Apply | Apply puts the field into the list. Nothing is stored until you click Save on the page. |
Saving
| Save | Saves the settings and the field list together. |
Data Subject Controls
| Your Memory Page | Sidebar link for signed-in users of a memory-enabled agent. Lists each stored value with its purpose, expiry, and source quote. |
| Correct | Available per field where the field was declared user-editable. |
| Forget | Available on every field; always sent with do-not-record-again so the fact is not recaptured. |
| Download a copy | Exports everything held about the person. |
| Erase everything | Erases all stored values and stops further recording until the person says otherwise. |
| Pause remembering | Stops reading and writing without erasing anything. |
| In-conversation Controls | The same actions by asking in plain language. Available from the first turn, for signed-in users only. |
| Consent | Raised in conversation when a declared detail would naturally come up, never as an opening interruption. Nothing is written until answered. |
Organization Limits
| Memory fields per agent | How many fields any agent may declare, up to 30. Set on the organization; the agent has no field-count setting. Add field is disabled once reached. |
| Prompt budget ceiling | The most any agent may spend on remembered data, up to 800. Each agent sets its own budget under it. |
| Who may change them | Organization Owner or Admin — a lower bar than the two switches, which are Owner-only. |
| Lowering a limit | Never erases fields already declared; the agent simply cannot add more. A budget above a lowered ceiling is clamped to it. |
Staff Visibility
| Aggregate by Default | Contributors see fill rates only, with no individual values. |
| Per-participant Access | Requires an explicit grant, is reached from a specific participant, and every opening is recorded. See Managing Agent Access. |
| Staff Access Switch | Organization-level, Owners only, off by default. While off, every contributor grant is inert. |
| Special-category Switch | Organization-level, Owners only, off by default. While off, the Sensitivity control is disabled. |
| Staff Corrections | Marked as staff edits, and are not protected from later overwrite the way a person's own correction is. |
Related guide: Remember Each User