Conversation Memory
How the chatbot remembers facts about recurring customers across multiple conversations.
The page “Conversation Memory - Help Center” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. Conversation Memory is disabled by default and must be enabled per tenant. Persistent facts are stored only after explicit confirmation and email verification.
Conversation Memory is live but disabled by default. It has to be enabled for the tenant before confirmed facts may persist across conversations.
A permanent fact is stored only after explicit confirmation and email verification. This reduces the risk that an incidental or incorrectly attributed statement becomes a long-term customer fact.
Stored facts can be reviewed and corrected in the customer profile. When an entry appears wrong, verify the customer's identity and the specific memory record. All processing remains tenant-isolated.
Use this feature only for stable and useful information. Sensitive or unnecessary details should not be stored as long-term memory. A normal conversation transcript does not represent the same as a confirmed cross-conversation fact.
For “Conversation Memory - Help Center”, the expanded text is required to remain specific to https://zentor-app.de/en/hilfe/conversation-memory, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case needs to identify this exact page, the active tenant and the observed step without disclosing credentials.
This page also explains its role within the Help Center, from the first check to the expected result, while naming verified limitations and the relevant detailed area. Statements that are not supported for https://zentor-app.de/en/hilfe/conversation-memory are not added. The expansion is therefore substantial without importing unrelated features or repeating generic filler.
When using “Conversation Memory - Help Center”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.