Persistent AI memory connections
Give supported AI features persistent context for a visitor or operator through an external memory service.
What it is
Memory lets a supported AI feature retrieve context retained from earlier interactions. It can use Mem0 or INSIDE Memory Service. The context belongs to a visitor or operator within the website, according to the feature's Scope.
Who uses it and why
Administrators decide which AI features use memory and whose context they should retrieve. Operators use AI assistance that can draw on earlier information without manually adding it to each question. Powerfront manages the connection and, for INSIDE Memory Service, the account used to process profile information.
Where to find it
Open Settings › AI › Features and edit a supported Autopilot, Copilot or Ask AI feature. The Memory selector appears when the selected AI engine supports this setup. Selecting a service reveals Limit and Scope.
The Settings role with AI permission, or the Developer role, grants feature configuration access. Ask Powerfront to manage the service connection in Settings › AI › Connections.
How it works
At the start of a supported AI execution, INSIDE takes the current question and requests relevant context for the selected identity. If the memory service returns context, INSIDE adds it to the instructions used for that execution.
At the end, INSIDE sends the extracted conversation messages and available conversation details to the memory service for storage or profile processing. Future executions can retrieve context from that service.
Auto scope uses operator memory for Ask AI and visitor memory for Autopilot and Copilot. You can choose Visitor or Operator explicitly. If the required identity is unavailable, INSIDE skips memory for that execution.
Memory failures normally allow the AI execution to continue without the additional context. An answer therefore does not prove that memory retrieval or storage succeeded.
Configure it
Ask Powerfront to set up Mem0 or INSIDE Memory Service and, for INSIDE Memory Service, select the AI Account needed for profile extraction.
Select the connection under Memory on the AI feature. Choose Scope deliberately, especially for operator assistance. Set Limit where the provider uses a match count, then save the feature. Select None to stop the feature using this connection.
Agree how the external service will retain and remove conversation-derived information before using it for persistent context. Removing the feature's Memory selection stops its use there; it does not itself erase stored memory.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Memory | Settings › AI › Features | website | None | Settings role, Developer role | Selects an external memory connection for the feature and enables its memory configuration. |
| Limit | Settings › AI › Features | website | 10 | Settings role, Developer role | Requests a maximum number of memories from providers that use a result limit; the editor accepts 1 to 50. |
| Scope | Settings › AI › Features | website | Auto | Settings role, Developer role | Chooses Visitor or Operator identity; Auto uses Operator for Ask AI and Visitor for Autopilot and Copilot. |
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| Host | Settings › AI › Connections | No | Supplies the address of the selected memory service. |
| Api Key | Settings › AI › Connections | Yes | Supplies the credential for Mem0 or INSIDE Memory Service. |
| Org Id | Settings › AI › Connections | No | Optionally scopes Mem0 requests to an organisation. |
| Project Id | Settings › AI › Connections | No | Optionally scopes Mem0 requests to a project. |
| AI Account | Settings › AI › Connections | Yes | Selects the account used by INSIDE Memory Service to extract profile information. |
Permissions
| Permission | Lets you |
|---|---|
| AI | With the Settings role, allows configuration of Memory on supported AI features. |
| Developer | Allows configuration of Memory on supported AI features. |
Limits and good to know
- Operator and visitor memory use different identities. Memory is also separated by website.
- Returning with a different visitor identity does not automatically retrieve the previous identity's memory. This feature does not itself establish cross-channel customer identity.
- Limit is a requested result count for providers such as Mem0. INSIDE Memory Service returns profile context using its own context controls.
- Memory service requests have a 30-second timeout.
- The service can receive conversation text. Its storage is separate from the visible chat history.
- Memory is not guaranteed for every execution or conversation context. Missing identity, unavailable context or a failed service request can cause it to be skipped.
Depends on and works with
View all connections as a list
This feature uses
- AI feature settings and change historyConfigured by
The feature selects the memory service, limit and identity scope.
- Autopilot for live chatConfigured by
Autopilot's Memory and Scope choices select the service and identity, with Auto using visitor memory.
- Copilot reply suggestionsConfigured by
Copilot's Memory and Scope choices select the service and identity, with Auto using visitor memory.
- Ask AI beside a visitor conversationConfigured by
Ask AI's Memory and Scope choices select the service and identity, with Auto using operator memory.
- AI accounts and shared defaultsConfigured by
INSIDE Memory Service needs a configured AI account for profile extraction; Mem0 uses its own service setup.
- Shared AI service connectionsRequires
Memory needs a configured Mem0 or INSIDE Memory Service connection.
Used by
- INSIDE AiFlow test dashboard · managed by PowerfrontEnhances
The dashboard includes external memory tooling.
- Shared AI service connectionsEnhances
Mem0 and INSIDE Memory Service connections provide long-term context.
FAQ and troubleshooting
Why is Memory not visible?
Check the feature type and selected AI engine. The inspected editor offers this control for supported Autopilot, Copilot and Ask AI features.
Why does Ask AI remember operator context instead of visitor context?
That is the Auto scope behaviour. Choose Visitor if the feature should use the selected visitor's identity and that identity is available.
Why did the AI forget something?
Check the selected service, Scope and current identity. The service may not return the fact for this question, or retrieval or storage may have failed. Ask Powerfront to check the connection if the issue persists.
Does selecting None delete stored information?
No deletion is performed by that selection. Ask Powerfront to help arrange removal through the memory service.
Can memory follow the same customer across all channels?
Do not assume that it does. This integration uses the identity available to the execution; it does not itself link identities across channels.