Personal Memories
Personal Memories store facts about individual email senders, enabling agents to provide personalized, context-aware responses over time.
Overview
When an agent processes emails from the same contact repeatedly, Personal Memories allow it to remember:
- Communication preferences (e.g., "prefers concise responses")
- Ongoing projects and their status
- Personal details relevant to interactions
- Past conversation history and context
This enables more natural, personalized interactions without asking the same questions repeatedly.
How Personal Memories Work
During Email Processing
When an agent receives an email:
- Memory Lookup - The agent queries for existing memories about the sender
- Context Enhancement - Retrieved memories are added to the agent's context
- Informed Response - The agent uses this context to craft a personalized response
- Memory Creation - The agent may store new facts discovered during the interaction
Memory Structure
Each personal memory contains:
| Field | Description | Example |
|---|---|---|
| Email Address | The contact this memory is about | john.smith@acme.com |
| Memory Key | Short identifier for the fact | preferred_format |
| Memory Value | The actual information stored | Prefers responses in bullet points with action items clearly marked |
| Category | Type of memory | preference |
| Importance | Priority level | normal |
| Expiration | When the memory expires | null (never) or specific date |
Categories
Personal memories are organized into categories:
| Category | Description | Example |
|---|---|---|
| preference | Communication or service preferences | "Prefers responses in Spanish" |
| project | Active projects or initiatives | "Working on Q2 marketing campaign" |
| personal | Personal details relevant to interactions | "Based in London, GMT timezone" |
| history | Past interaction context | "Had billing issue resolved in January" |
| other | Miscellaneous facts | "Referred by Sarah Johnson" |
Importance Levels
| Level | Description | When to Use |
|---|---|---|
| critical | Must always be considered | Legal requirements, accessibility needs |
| high | Important context | Key project deadlines, VIP status |
| normal | Standard context | General preferences |
| low | Nice-to-have information | Minor details |
Managing Personal Memories
Viewing Memories
Navigate to Admin > Data & Logs > Memories and select the Personal tab.
The list shows:
- Contact email address
- Memory key and value
- Category and importance
- Creation date and source (agent or admin)
- Access statistics
Filtering Options
| Filter | Description |
|---|---|
| Email Address | Filter by specific contact |
| Category | Filter by memory type |
| Importance | Filter by importance level |
| Search | Search in keys and values |
Creating Memories Manually
To pre-populate contact information:
- Click Add Memory
- Enter the contact's email address
- Provide a descriptive memory key
- Enter the memory value with relevant details
- Select appropriate category and importance
- Optionally set an expiration date
- Click Save
Example:
Email: vip-client@partner.com
Key: account_status
Value: Premium enterprise client with dedicated support. Direct escalation to Account Manager (Amy Chen) for any issues.
Category: preference
Importance: high
Editing Memories
- Click on a memory in the list
- Modify the key, value, category, importance, or expiration
- Click Save
Note: You cannot change the email address of an existing memory. Delete and recreate if needed.
Deleting Memories
- Click the delete icon on a memory
- Confirm the deletion
Deleted memories are soft-deleted and no longer appear in agent queries.
Agent-Created Memories
Enabling Memory Tools
To allow agents to create memories:
- Edit the agent in Configuration > AI Agents > Agents
- In the Tools section, add:
manage_personal_memory- Store, update, delete memoriesquery_global_memory- Query existing memories (read-only)
- Add instructions guiding memory usage (see below)
Memory Tool: manage_personal_memory
Agents use this tool to store facts about contacts:
Parameters:
| Parameter | Required | Description |
|---|---|---|
action | Yes | store, update, or delete |
contact_email | Yes | Email address of the contact |
key | Yes | Memory identifier |
value | For store/update | The information to store |
Example agent instruction:
## Memory Guidelines
When processing emails:
1. If you learn something useful about the sender (preferences, projects, important details), store it using manage_personal_memory
2. Use descriptive keys that will be easy to find later
3. Store facts, not opinions
4. Don't store sensitive information (SSN, passwords, etc.)
Memory storage examples:
- Preference: "prefers_format" -> "bullet points with headers"
- Project: "current_project" -> "Website redesign, due March 2024"
- Personal: "timezone" -> "PST, prefers calls before 2pm"
Automatic Context Injection
When personal memories exist for an email sender, they are automatically retrieved and included in the agent's context. The agent sees something like:
## Context: Known Information About john.smith@acme.com
- preferred_format: Prefers responses in bullet points
- current_project: Working on Q2 product launch
- timezone: Based in EST, available 9am-5pm
Use Cases
Customer Support
Store customer preferences and history:
- Preferred communication style
- Previous support tickets and resolutions
- Product usage patterns
- Escalation preferences
Sales
Track prospect information:
- Current stage in sales funnel
- Budget discussions
- Decision-maker relationships
- Competitor mentions
Executive Assistant
Remember stakeholder preferences:
- Meeting format preferences
- Travel preferences
- Scheduling constraints
- Communication styles
Access Statistics
Each memory tracks usage:
| Metric | Description |
|---|---|
| Access Count | Times the memory was retrieved |
| Last Accessed | When an agent last used this memory |
| Created Date | When the memory was first created |
| Created By | Agent name or "Admin" for manual entries |
Use these statistics to identify:
- High-value memories (frequently accessed)
- Stale memories (never accessed)
- Active contacts (many memories)
Best Practices
For Administrators
- Pre-populate VIP contacts - Create memories for important contacts before first interaction
- Set expirations for time-sensitive data - Project deadlines, temporary preferences
- Review agent-created memories - Periodically audit for accuracy
- Use consistent keys - Establish naming conventions for memory keys
For Agent Instructions
- Be specific about what to remember - Guide agents on valuable vs. trivial information
- Set boundaries - Explicitly state what NOT to store (sensitive data)
- Encourage updates - Tell agents to update memories when information changes
- Value threshold - Only store information that would help future interactions
Key Naming Conventions
Recommended patterns for memory keys:
preference_communication_style
preference_response_format
project_current_name
project_current_deadline
personal_timezone
personal_role
history_last_issue
history_last_purchase
Troubleshooting
Memories Not Appearing in Agent Context
- Verify the sender's email address matches exactly
- Check that the memory is not expired
- Confirm the memory is active (not deleted)
- Review agent logs for memory lookup errors
Agent Not Creating Memories
- Verify
manage_personal_memorytool is assigned - Check agent instructions include memory guidance
- Review execution logs for tool call failures
- Ensure the agent is configured with appropriate permissions
Duplicate Memories
The system prevents duplicate keys for the same email address. If you see duplicates:
- They may have different keys (slight variations)
- Check for spaces or capitalization differences in email addresses
- Consolidate by deleting duplicates and keeping the most accurate
Privacy Considerations
Personal memories may contain PII. Best practices:
- Retention policy - Set expirations for non-essential data
- Minimization - Only store what's needed for the use case
- Access control - Limit who can view memories in admin console
- Audit regularly - Review stored data periodically
- Agent instructions - Explicitly prohibit storing sensitive data (SSN, passwords, etc.)
Related Topics
- Global Memories - Organization-wide policies
- Artifacts - Store agent-generated content
- Tools - Memory tool descriptions
- Agents - Agent configuration