Cross-conversation memory

How the chatbot remembers facts about a customer across multiple conversations — and how to review and correct them in the customer profile.

Last verified: 2026-10-20

If the feature is active for your account, the chatbot remembers important details about returning customers across several conversations and channels – for example name, email address and phone number as well as details from earlier appointment bookings, such as the vehicle or the request. The feature is switched off by default; Zentor enables it for your account on request.

Step by step

  1. Open the customer profileIn the “Chatbot” area, open the “Customers” tab and select the customer.
  2. View stored memoriesIn the “Stored memories” section you see the details stored for this customer with type, value and origin (“detected automatically” or “corrected manually”).
  3. Correct a detailIf an automatically detected detail is wrong, correct it manually. Your correction counts as confirmed and is recorded in the log.
  4. Delete a detailDelete details that are no longer wanted or incorrect one by one.

Expected result

You have a transparent overview of the stored customer facts and can correct or delete them as needed.

Common error cases

The chatbot does not remember anything about recurring customers.

Cause: The feature is switched off by default and is enabled for your account by Zentor.

Resolution: Contact Zentor to activate the feature for your account.

A fact from an ongoing conversation does not immediately appear in the customer profile.

Cause: Permanent facts (e.g. from an appointment booking) are only saved after explicit confirmation by the customer and email verification, not immediately upon mere mention.

Resolution: No action needed — this is a deliberate safeguard against incorrectly captured information.

A customer is not recognized as the same person across two channels (e.g. web chat and email).

Cause: Recognition primarily happens via the channel-specific identifier; merging across channels only happens with a verified, matching email address.

Resolution: Check whether the email address was verified and stored identically in both channels.

Related articles

← Back to category