Agent Memory

How Agent Memory Works

When a user chats with an agent, Agent Memory identifies relevant information from the conversation and stores it as a memory. In future conversations, the agent uses these memories as context to give more relevant, personalized responses.

Memory capture begins after you enable Agent Memory for an agent. For Agentforce Employee agents in Lightning Experience, memory capture begins only after the user opts in. See Manage Agent Access to Your Memories. On other supported surfaces, user opt-in isn't required.

When you disable Agent Memory for an agent, the agent stops using its stored memories, but it keeps the memories it already created.

Each agent can store up to 50 memories per user. When a user reaches the limit, Agent Memory deletes the oldest memory automatically to make room for the new one. Encourage your users to review their stored memories regularly, so they don't lose memories that matter to them.

Agent Memory uses your users' conversation data to personalize responses. That data stays within Salesforce and isn't shared with the large language model (LLM). Inform your users about how Salesforce collects and uses their data. See Trust and Agentforce.

Supported Agent Types and Surfaces

Agent Memory supports Agentforce Employee agents and Agentforce Service agents. These agents must use Agent Script in Agentforce Builder. Legacy agents don't support Agent Memory. How users manage their memories and memory preferences depends on the agent type and surface.

For Agentforce Employee agents in Lightning Experience, users manage their memories and memory preferences from the Memory & Preferences panel. On surfaces where the panel isn't available, such as a messaging channel or mobile app, users manage their memories and preferences by talking to the agent directly. See Manage Your Agent's Memories Conversationally.

For Agentforce Service agents, users manage their memory preference and stored memories conversationally, after you add the User Memory Management subagent. There's no disclaimer or separate opt-in step on Service agent channels.

When to Use Agent Memory for Agentforce Service Agents

Consider enabling Agent Memory for your Agentforce Service agents when your customers:

• Return to continue troubleshooting an issue from an earlier conversation, such as following up on a support case.
• Regularly contact support with the same preferences or context, such as a preferred shipping method or account details.
• Have a process that spans multiple conversations, such as a multi-step return or dispute that isn't resolved in one interaction.

Personalize Responses with User Profile Information

Agent Memory personalizes responses using information learned from previous conversations. User profile context provides additional information about a user, such as their name, email, locale, or time zone, so the agent can personalize the interaction without requiring the user to provide those details in conversation.

The profile information that's available depends on the type of agent and the user record associated with the interaction. For Agentforce Employee agents, user profile context can include fields such as name, email, company, locale, and time zone. For Agentforce Service agents, the available profile information depends on whether the customer is associated with a User or Contact record. A User record provides the same user profile fields. For a Contact record, profile context includes the contact's name, email, and country. Use profile fields in agent instructions and prompt templates to personalize responses, or reference them as variables to define conditions in Agent Script.

User profile context works independently of Agent Memory. Profile information isn't stored as a memory and doesn't appear in the memories that users view or manage. Enable either feature independently, or use them together to give the agent more context about the user. To enable user profile context, see Enable User Profile in Agent Script.

Conversational Memory Management

Conversational memory management lets users manage the information that Agent Memory remembers about them by talking to the agent. For example, a user can ask the agent to show or delete a stored memory, or update whether the agent can create and use memories from their conversations.

To support these requests, add the User Memory Management subagent to your agent from the asset library in Agentforce Builder. The subagent includes the Get User Memories, Manage User Memory, Get Agent Memory Preference, and Update Agent Memory Preference actions. The subagent isn’t added automatically, so you must add it for users to manage their memories conversationally.

Examples of utterances classified to the User Memory Management subagent:

• "Show what you remember about me."
• "What do you know about my last conversation with you?"
• "Delete what you remember about my shipping preference."
• "Delete the memory about my last support case."
• "Is memory enabled for me?"
• "Turn off memory for this agent."
• "Turn on memory for this agent."