> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rogeriq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer Memory

Use project and customer memory to preserve context across conversations.

# Customer Memory

Memory helps RogerIQ avoid treating every conversation as the first interaction.

## Memory Types

| Type | Scope | Use |
| --- | --- | --- |
| Project memory | Project | Product facts, support policies, team preferences, and stable context. |
| Customer memory | Contact | Customer preferences, account facts, previous decisions, and repeated issues. |
| Pending memory | Project | Suggested memory updates waiting for review. |

## Review and Rollback

Project memory keeps version history. When a memory update is wrong or too broad, roll back to a previous version.

## Good Memory Entries

Good memory is factual, short, and useful across future conversations.

```txt
Enterprise customers require approval before refunds over $500.
```

Bad memory is vague or overfit to one message.

```txt
Customer was upset and needs help.
```

Do not store sensitive secrets, raw payment data, or private credentials in memory.