Good memory examples
| Save this kind of context | Example |
|---|---|
| Communication preference | Remember that I prefer concise answers with clear next steps. |
| Role or team context | Remember that I manage customer operations for a B2B software company. |
| Recurring project context | Remember that Project Atlas is our customer onboarding refresh. |
| Writing style | Remember that customer emails should sound warm, direct, and low-jargon. |
| Units or formatting | Remember that I prefer dates in Month Day, Year format. |
| Ongoing audience context | Remember that my weekly updates are written for non-technical executives. |
Keep this in the current chat
Some details are useful once but should not become long-term memory. Examples:- A one-time deadline.
- A temporary draft direction.
- A single customer’s private details.
- A file-specific instruction.
- A preference that only applies to this project phase.
Do not save sensitive information
Do not ask Babbily to remember:- Passwords.
- Verification codes.
- API keys.
- Private keys.
- Payment card numbers.
- Government identifiers.
- Raw connected-app credentials.
- Confidential details you are not allowed to use in Babbily.
Update memory when context changes
When a preference or project changes, say so directly.Ask Babbily what it remembers
Use Settings > Memory for the most complete view. You can also ask in chat:Memory quality checklist
Before saving something, ask:- Will this still be true in future chats?
- Would this improve many replies, not just one?
- Is it safe to reuse?
- Is it phrased clearly?
- Would I be comfortable seeing it in Settings > Memory?
Memory
Learn how to review, update, and remove memory.
Data controls FAQ
Review privacy controls for memory, sharing, connectors, and Library items.
