Run your workspace
Customer memory
Deze pagina is nog niet beschikbaar in het Nederlands, daarom lees je hem in het Engels.
Customer memory
What the AI employee may remember about a known customer between conversations: a few lasting facts, never sensitive ones, and only once the shop has switched it on.
Customer memory is off for every workspace until the platform team, or the agency that looks after the workspace, switches it on — after the workspace has signed the data processing agreement that covers it. Until then nothing is stored, and nothing in this page happens.
Who is a known customer
Only someone whose identity was proven: a customer who writes on WhatsApp (the channel verifies the number), or a customer signed in to the shop whose id the shop's own server signed with the workspace's identity secret (Identify signed-in customers); soon also one who confirmed their e-mail address with a code in the chat. A name or an address a visitor merely types is never enough — it may be someone else's.
Three levels of trust
Every chat session gets a level when the widget starts, carried in the session's signed token, so nothing later has to look it up again:
| Level | Who | What may happen |
|---|---|---|
| 0 — anonymous | A visitor with a cookie and nothing else. | The conversation as it always was. |
| 1 — named by the page | The page put a name or an address in
window.aiAssistantUser without a valid signature. |
The lead form is pre-filled with them, nothing more. Anyone can write a name in a page, so it is a hint, not an identity: no contact is made, no earlier conversation resumes, and no fact or order ever appears — also when the address belongs to a known customer. |
| 2 — proven | The site's server signed the customer's id (signed-in customers), or the customer confirmed their e-mail address with a code in the chat (below). | The contact and their conversations on every device; and, once those parts ship, their facts and orders in the answers. |
What is kept
- At most 20 short facts per customer that help answer them later: sizes and fit, preferences, what they own or ordered, an open return or question, how they like to be addressed. Each fact says where it came from (the conversation) and when.
- A fact is forgotten twelve months after it was last confirmed or used; when the 20 are full, the fact that was used (or learned) longest ago goes first.
- How the customer likes to be spoken to (language, formal or informal, short or long answers), once that is known.
What is never kept
Anything about health, religion, politics, finances (income, debts, benefits), sexuality, ethnicity, union membership or criminal matters, and never passwords, codes or payment details. Two checks: the model that reads the conversation labels such facts, and a word list in Dutch, English, German and French checks every fact again on its own. A fact is kept only when both say it is harmless; the rest is dropped and only counted.
When it happens
Ten minutes after a conversation of a known customer has gone quiet, a job reads its new messages against the facts already known, merges them (a new fact can update an old one) and stores the result. Nothing runs while the visitor is chatting, and a test chat from the dashboard is never read.
Recognising a customer by e-mail code
Works on any website, with or without customer accounts, and needs no plugin: the proof happens inside the chat. When a visitor who is not recognised yet asks about their own orders, returns or account — or simply asks to be recognised — the AI employee offers to send a code to the e-mail address of their account. The visitor types the address, a 6-digit code goes out in the shop's (or its agency's) name and in the conversation's language, the visitor types the code, and the session is a proven customer: the contact with that address (made on first sight), their conversations on every device, and — with memory on — their facts and orders in the answers.
- The code is valid for ten minutes and works once; after five wrong attempts it is dead and a new address starts a new one. The code is kept hashed and never logged.
- Limits: three codes an hour per conversation and per address (and a few more per visitor); beyond that the chat asks to check the inbox or wait an hour.
- The browser stays recognised for 30 days — a shop sets its own period under Settings → Workspace → Customer memory — through a signed cookie on the shop's domain; a new device asks for a new code. Forgetting the customer revokes it everywhere at once.
- Only while customer memory is on for the workspace; a test chat in the dashboard never starts it.
Orders
A proven customer's last five orders come from the shop itself, not from memory: when their chat starts, a job fetches them from the shop system and keeps a copy for ten minutes while they type; the reply reads that copy only, so a slow shop never slows an answer. Nothing is stored beyond those minutes, and nothing is fetched for a visitor the page merely named (level 1) or for a stranger.
- WooCommerce: through the WordPress plugin's signed
order endpoint — the one the
lookup_ordertool already uses; no extra setting. - Shopify: through the Admin API with a custom app's access token, pasted under Integrations › Shopify orders.
- Botble and other Laravel shops: through the Botble plugin's signed order endpoint on the shop itself, signed with the workspace's identity secret; the plugin ships with the Botble work.
- Any other shop: by the customer's verified e-mail address through the shop's own API (WooCommerce REST, Shopify, Lightspeed, Magento, PrestaShop, Shopware), or from the orders the shop sends through the order webhook or a CSV file. See Orders without a plugin.
Each order: number, date, status, total, the items with their variant and
quantity, the tracking link and — where the shop reports one — a return in
progress. Never the address or the payment details. The
lookup_order tool also recognises a customer signed in
through the signed identity,
not only the WordPress shopper token.
How the AI employee uses it
For a signed-in customer (level 2) with memory on, each answer gets one compact block of what the shop knows — who they are, how they like to be spoken to, the five facts most relevant to the message, and their last orders from the shop (see Orders). The block rides inside the prompt as data, in the same envelope as the shop's own pages, so a fact can never act as an instruction; it is capped at about 300 tokens, and it is empty — no tokens at all — for everyone else and whenever a switch is off. The facts an answer used are marked used afterwards, so they outlive unused ones.
The shop chooses, under Settings → Workspace → Customer memory, how the AI employee uses it:
- Subtle (the default): only when it helps the answer — the right size, an open return, what they ordered. It never announces that it remembers, and does not greet by name unless the customer does.
- Explicit: the widget greets a signed-in customer by first name ("Welcome back, Anna!"), and the AI employee refers to what it knows ("last time you ordered size 43 — shall I keep that?").
When a customer wants one of their earlier orders again, the answer shows that product as a card with an Order again button to its product page. Unless the shop has in-chat payments, the AI employee says the order is placed on that page — it never claims to have placed or reserved one itself.
The customers page
Customers in the menu lists every known customer of the workspace: name, address, how they were proven (WhatsApp, WooCommerce, Shopify, …), how many facts and conversations, when they were last seen, and their segments. Search by name, or by an exact e-mail address.
A customer's page shows the facts the AI employee keeps — each can be edited or deleted (a sensitive detail is refused the same way the AI refuses it) — the identities, the segments, and one timeline of their conversations (with the first question and a link), their visits and their last orders from the shop. Forget deletes the contact, the identities, every fact and every segment membership at once; the conversations keep their text but no longer point at anyone (the customer's own "forget me" in the chat deletes them as well — see below). It cannot be undone and is written to the audit log.
Segments
Under Customers → Segments the shop describes groups by rules over what it knows, for example "regular customers who often ask about delivery time": all or any of the conditions must hold. Fields:
factscontains a word — any of the customer's facts;questionscontains a word — any question the customer asked;conversationsat least / at most a number;last_seen_daysat most / at least a number of days ago;identityis a shop system (woocommerce,shopify,botble,whatsapp, …);languageis a language code;open_returnis yes or no — a return the facts say is still open.
Members are worked out right after a customer's facts change and for the whole workspace every hour (a last-seen age moves without a fact changing). Each segment shows an insight: the open questions its members asked most, with a link to answer them. Smart Segments on an AI employee are something else — knowledge areas per part of the website, not customer groups.
Orders are not a rule yet: they live in the shop and are only cached for minutes; the order table of the universal order webhook makes them one.
Export to your CRM
Through the workspace's own outgoing webhooks
(Integrations → Webhooks):
contact.updated fires when a customer's facts changed (after
a conversation was read, or after an edit in the dashboard) and
contact.segment_entered when a customer enters a segment.
Both carry the contact — name, address, phone, language, identities,
facts and segments — signed like the lead webhook. For an agency's client
they fire only while the agency opened Customers for that client.
What the customer sees
A recognised customer (level 2) is told so the moment the widget opens: the greeting bubble reads "You are recognised as Anna · we remember your questions to help you better. Ask “what do you know about me?” or say “forget me” at any time" (in the explicit mode: "Welcome back, Anna! …"). Two things they can then say in the chat are answered with fixed texts, never by the model:
- "What do you know about me?" lists their name and address, how they were recognised (WhatsApp, WooCommerce, e-mail code, …), every fact kept, and the retention: a fact is deleted so many months after it was last used.
- "Forget me" explains what will be deleted and asks for one confirmation word (FORGET, in Dutch VERGEET); the word deletes the contact, the identities, every fact and segment label, and every conversation linked to them — on every device, with their messages and the leads left in them, because the customer's own words carry contact details (the address typed for a code, for one). The browser's remember cookie is deleted, the session is a stranger's again, and the chat goes on in a fresh, empty conversation. It cannot be undone; the audit log records it.
Phrases in Dutch, English, German and French are understood. A stranger saying the same words gets the model's answer — which, by rule, offers recognition and keeps nothing about an unrecognised visitor.
Retention
- A fact is deleted a set number of months after it was last used — twelve unless the shop chose otherwise under Settings → Workspace → Customer memory (1–60). Every night the expired facts are removed.
- Conversations follow the workspace's own retention; forgetting a customer only cuts the link to them.
- A browser verified by e-mail code is remembered for the shop's period (30 days unless set otherwise); the code itself is removed a day after it expired.
Data subject requests
The data subject request tools cover customer memory: a lookup by e-mail address also finds the known customer with that address; an export carries their contact, identities, facts and segments; the dashboard's erase removes them with the rest and keeps the conversations' text without a link, as it always did; the visitor's own delete in the widget removes the contact and every conversation linked to it, like "forget me".
Forgetting
- Expired facts are removed every night.
- A data subject request that erases a visitor also deletes the customer records (identities and facts) of the conversations that visitor had; the conversations keep their text without a link to anyone.
Switching it on
- Agency: the client's Access page in your partner dashboard has a Customer memory section with the switch — once that client's data processing agreement is signed.
- Platform team: Admin → Workspaces → the workspace, Customer memory. Each change is in the audit log.
- The shop itself: Settings → General shows whether it is on; the shop cannot switch it on by itself.