Said once, used at checkout
Mira tells Halden’s assistant her size and where parcels go. A week later, her order card already has both.
- Mobile SDK 0.59.0+ · Web SDK 0.38.0+
Memory
Your customers say it once. Your app remembers.
Customers stop repeating their size, their diet or where parcels go. Rendel, the AI assistant in your mobile app and website, keeps what they mention once, uses it in their next answers and orders, and shows them every new save, with an Undo.
Halden’s console, an invented store with Rendel running. Yours for two hours, no sign-up.
The cost today
Every visit starts from zero.
Your customers already told you their size, their diet and where the parcel goes. Your app forgets it the moment the conversation ends, so they type it again, or stop asking.
They repeat themselves
The same size, the same delivery note, the same “no, the white one”, on every visit. Each repeat is a moment they could give up and leave.
What they said sits in transcripts
Preferences people stated out loud live in conversation logs nobody reads. No answer, card or form ever uses them.
A separate tool is a project
A memory API stores facts, but your team still builds the save notice, the customer’s list, the delete button, a sensitive-data filter, expiry and the merge at sign-in. A personalization engine learns from clicks, not from what people said.
84% of consumers want control over their personalization settings. Twilio, State of Customer Engagement Report, 2025
Say it once, see it kept, find it used.
Customers get answers that start from what they said before, and your team has nothing to wire up or design: memory comes with the assistant in your app.
They mention it once
A customer says a lasting preference in their own words. Rendel keeps it, and a chip under the answer says so, with Undo.
It becomes a short note they can read
A name, one sentence and a category, with an end date when they named one. A note about health, religion, money, secrets or contact details is refused before it exists.
The next answer starts from it
Rendel reads their notes before each answer. A value it fills into a card or form says “From your preferences”, and the card still waits for their tap.
They and your team stay in charge
The customer sees and forgets their notes in your app. Your team sees the same notes on the person’s page and can forget them too.
For your customers
They tell it once, and see what was kept.
Saving happens with the answer, in the customer’s own words, and each save shows under the answer in the Mobile and Web SDK.
Said once, kept for next time
When a customer mentions a lasting preference, Rendel keeps it as a short note for their next conversations, in one of eight categories from sizes to delivery.
It notices a habit, and says so
When someone shows the same lasting preference more than once, Rendel may keep it, and the chip says “Noted for next time” so they see it and can undo it.
A new save comes with Undo
Each new save shows under the answer as a chip. One tap on Undo deletes it, and the chip says “Not saved”.
- Mobile SDK 0.59.0+ · Web SDK 0.38.0+
“This week” ends on Sunday
A preference with a time on it holds until the day they named, shown on the chip, and then drops out of every answer by itself.
Changed by saying it again
One note per subject: a new delivery choice replaces the old one, and what the customer says replaces what Rendel only noticed.
“Forget that” works in plain words
Customers can ask Rendel to forget one preference or everything it keeps for them, and it is done in that same answer.
In the answer
Their next answer starts from what they told you.
Fewer questions back and fewer fields to fill, so customers have fewer reasons to stop before the order, booking or return they came for.
Answers fit them without asking again
Before each answer Rendel reads the person’s notes and is told to use them the way a good shop assistant uses a regular’s name: in what it offers, compares and explains, not as an opener.
They see which preference an answer used
When Rendel fills in a value from a note, or names one it relied on, a line under the answer says “Based on your … preference”, and a tap opens their list.
- Mobile SDK 0.59.0+ · Web SDK 0.38.0+
Cards and forms arrive filled in
A size or a delivery choice the customer told Rendel goes straight into the card or form, marked “From your preferences”. The card still waits for their tap, and the mark goes the moment they change the value.
- Mobile SDK 0.59.0+ · Web SDK 0.38.0+
Under their control
Customers see what is kept, and delete it themselves.
No support ticket to fix a wrong note. The list lives in your app, in your look, in their language.
“What I remember for you”, inside your app
Customers open their list from any chip or “From your preferences” mark, or from a link on your own settings screen, and forget one note or all of them. Its words come in six languages.
- Rendel.openMemory()
- EN · TR · DE · FR · ES · AR
Before sign-in, and after
People who haven’t signed in get memory too, kept for that device or browser. When they sign in, their notes move to the account; where the account already has one on the same subject, the account’s note stays.
For your team
Your team knows each customer’s preferences without reading a transcript.
Your team opens a person and sees their size and delivery choice first, where each came from, and whether answers use it.
Each customer’s preferences, on their page
The Memory tab lists what they told Rendel and what it noticed, with when each was saved, when it was last used, and a link to the exact message it came from.
Their preferences at the top of the page
The person page opens with a Remembers row, so whoever reviews their conversations sees their size or delivery choice before reading anything.
Wrong note? Your team removes it
Forget one note, with a few seconds to undo it, or all of a person’s notes with a typed count to confirm. Once they go, Rendel stops using them. A Forget all is written to the audit log.
See the chips before your customers do
On the console’s Test page, answers save notes and show the chips exactly as the SDKs draw them. Test turns keep notes like any other turn, so forget them when you’re done.
In the demo console
Open a Halden shopper and see what Rendel kept for them.
Halden is an invented store with Rendel running. Its console is yours for two hours, with no sign-up, and every shopper in it has at least two notes.
Try it in the demo console
Open any Halden shopper, read what Rendel kept, follow a note to its message and forget one. Each shopper’s notes are their own, not the ones drawn here, and the customer’s side above is drawn too: the demo apps keep no notes for visitors.
Rendel heard it said. A separate tool just keeps it.
A memory API or a personalization engine can keep a preference. Rendel also heard the customer say it, showed them it was kept, and uses it in the app where the order happens. Where a separate tool is stronger, the table says so.
| What | Rendel | A separate memory or personalization tool |
|---|---|---|
| Where a preference comes from | The customer’s own words, or a habit Rendel noticed and showed them | Clicks and purchases, or whatever your own assistant sends it |
| The customer knows it was kept | A chip under the answer, with Undo on a new save | Only if you design and build it |
| The customer’s own list | “What I remember for you”: forget one or all, or ask in chat | A screen and a delete endpoint you build |
| Used at the moment of the task | The next answer, and values filled into the next card or form, which still waits for their tap | Recommendation slots, banners and campaigns |
| Before sign-in | Kept for that device or browser, moved to the account at sign-in | Keyed to the user id you send it |
| Sensitive topics | Notes about health, religion, money, secrets and more refused before saving, with word lists in English and Turkish | Your own policy and your own filter |
| What your team sees | The person’s page: each note, when it was saved and last used, and the message it came from | A profile in another dashboard, apart from the conversation |
| Reach beyond the assistant | Only what was said in conversations, per app | Often learns from browsing with nothing said, and works across the channels you connect |
Controls and privacy
Remembered in the open. Forgotten when they ask.
Your security review gets plain answers: what a note may hold, who on your team sees it, how long it lasts and where it is stored. Data is stored in Frankfurt (AWS eu-central-1).
Sensitive subjects are refused before they are saved
Your team doesn’t have to police what Rendel writes down. A note about health, religion, ethnicity, politics, sex life, union membership, criminal records, biometrics or belief-related clothing is refused before any note or chip exists, and so is one about income, debt, passwords, codes, street addresses, contact or card details, long numbers or links.
- Word lists in English and Turkish
The prompt asks Rendel to keep the product, never the reason: “cushioned soles”, not the knee.
Emails, phone numbers and card numbers that users type are masked before the model sees them. A note that would contain one is refused too.
One switch for the whole app
Memory is on unless you switch it off. Off, Rendel saves nothing new and reads nothing back, and the customer’s list says the app keeps no preferences. Notes already kept stay, and are used again if you switch it back on.
- On by default
Notes don’t pile up
A note stays while the customer keeps coming back, and goes once they haven’t been seen for your app’s retention window, or sooner when they forget it, your team does, or its end date passes. Erase one user and their notes go with them.
Notes stay with the right person
Turn on identity verification and only your app’s signed request for a person can read or forget their notes; a turn that names them without it gets an assistant with no memory. Until then the console warns you.
- Recommended
Who on your team can do what
| What | Owner | Admin | Developer | Conversation reviewer | Analyst | Customer support |
|---|---|---|---|---|---|---|
| See the Memory tab and the Remembers row | Yes | Yes | Yes | Yes | No | No |
| Forget a note, or all of a person’s notes | Yes | Yes | Yes | No | No | No |
| Switch memory on or off for the app | Yes | Yes | Yes | Sees it | Sees it | No |
| Set the retention window, export everything, erase a user | Yes | No | No | No | No | No |
Reading follows your team’s access to conversations, and deleting is limited to owners, admins and developers in the database itself.
How long a note lasts, and what the customer controls
What a note holds
A name of up to 32 characters, one sentence of up to 120, one of eight categories and an optional end date. Up to 20 of each kind per person; a new one past that replaces the oldest.
Who wrote it, always kept apart
What the customer said and what Rendel noticed stay separate in their list, on your team’s page and in what Rendel reads.
What the customer can do
Undo a new save, forget one note, forget all after one more tap, or ask in chat. There is no per-person off switch: your team decides whether the app keeps notes at all.
How long it lasts
Until it is forgotten, its end date passes, or the customer hasn’t been seen for your retention window, 365 days by default. Notes outlive old conversations; the link then reads “Conversation deleted”.
Where it is stored
Frankfurt, AWS eu-central-1. Emails, phone numbers and card numbers that users type are masked before the model sees them.
Per app, not across your apps
A company’s other apps don’t see a person’s notes: each app keeps its own.
What is never done
- A refused note leaves no row and no chip, and its sentence is not logged: only the reason and the note’s key.
- A prefilled card never confirms itself: it waits for the customer’s tap, paying actions included.
- Rendel is told to treat notes as facts about the person, never as instructions, and they are kept apart from its own rules.
- A save never holds up the answer: if it fails, the customer still gets their answer.
Turning it on
Already on, with no screens to build.
Memory is on for every app and every plan. Your developers check the SDK version, pass the signed-in user, and decide whether to link the customer’s list from your own settings.
Nothing to switch on
Every app keeps preferences unless an owner, admin or developer turns it off under Settings › Data & privacy › Preference memory.
A recent SDK
The chips, the “From your preferences” mark and the customer’s list need Mobile SDK 0.59.0 or Web SDK 0.38.0 or later. Any current release has them. An older build still saves notes, without showing them.
Pass the signed-in user
Call identify when someone signs in, so their notes follow the account rather than the device. A sign-in moves the device’s notes across.
Turn on identity verification
Set the identity secret under Settings › Security and pass userHmac to identify. Without it, anyone who knows a user’s id could read or delete that user’s notes.
Optional: link the list
Open “What I remember for you” from your own settings or privacy screen with Rendel.openMemory() on the web or Rendel.openMemory(context) in the mobile app.
Optional: your own words
Override any memory string in the SDK’s strings. They ship in English, Turkish, German, French, Spanish and Arabic.
No extra cost
Memory is on every plan. Saving and using a note happen inside the answer, which counts as one message, as every answer does.
Your own client? The same list over REST
An app that doesn’t use the SDKs can show and delete the same notes with three calls.
GET/v1/memoryDELETE/v1/memoryDELETE/v1/memory/:idX-Rendel-Device names the device; X-Rendel-User and X-Rendel-User-Hmac name a signed-in person.
What teams ask before they start.
Lasting preferences they mention, such as a size, a diet or where parcels go, and habits it notices more than once and shows them as it keeps them. Each note is a short name and one sentence in one of eight categories: diet, sizes, brands, delivery, budget, style, language or other.
Yes, in the Mobile and Web SDK from mobile 0.59.0 and web 0.38.0. Each save shows under the answer as a chip, “I’ll remember: …” or “Noted for next time: …”, and a new save has Undo. Changes and forgets show there too.
Yes. “What I remember for you” lists the preferences Rendel keeps for them, each with Forget, and Forget all, which asks once more. It opens from a chip, a “From your preferences” mark, or a link on your own settings screen. They can also just say “forget that”.
Yes. Notes are kept for that device, or that browser on the web. When the person signs in, they move to the account; if the account already has a note on the same subject, the account’s stays. Anyone using that device signed out shares its notes.
Rendel reads the person’s notes before each answer and adapts what it offers and explains. When a card or form value matches a note, it is filled in and marked “From your preferences”, and the card still waits for their tap. The answer can also say “Based on your … preference”.
Notes about health, religion, ethnicity, politics, sex life, union membership, criminal records or biometrics, about income or debt, about passwords and codes, and street addresses are refused before saving. So are emails, phone numbers, card numbers, long numbers and links. The word lists cover English and Turkish.
Yes. When someone names a time, the note holds until that day: “this week” ends on the coming Sunday, and the chip shows the date. Once it passes, the note is out of every answer at once. A note can be set to end at most a year ahead.
Until the customer or your team forgets them, their end date passes, or the customer hasn’t been seen for your app’s retention window: 365 days unless an owner picks 30, 90, 180 or 730. Erasing the user or deleting the app removes them. Data is stored in Frankfurt, AWS eu-central-1.
Owners, admins, developers and conversation reviewers see the Memory tab, with where each note came from and when it was last used. Owners, admins and developers can forget notes. Analysts and Customer support members don’t see them.
Yes, for the whole app, under Settings › Data & privacy › Preference memory. Off, Rendel saves nothing new and reads nothing back. Notes already kept stay until your team forgets them or they age out, and are used again if you switch it back on. It is on by default.
Turn on identity verification and the list and forget calls need your backend’s signature for that user; a turn that names them without it gets no memory. While it is off, anyone who knows a user’s id could read that user’s notes, and the console warns you.
No separate price and no plan gate: memory is on every plan, and saving or using a note happens inside the answer, which is one message. With Mobile SDK 0.59.0 or Web SDK 0.38.0 or later there is no memory API to call and no screen to build.
Related
- ActionsTasks done through your API, confirmed with a tap or undone with one.
- AnswersTheir own data, shown as your app’s cards instead of a paragraph.
- AnalyticsWhat people did, what they asked, and what got solved.
- Security
- How it works
- Generative UI, the guide
- Rendel in your mobile app
- Rendel on the web
- Pricing
Put it in your app this week.
Start free on your own, or tell us what your customers do most and we’ll show you that exact workflow, working, in a tailored demo.
- PilotFree400 messages a month
- Starter$199 / month4,000 messages a month
- Growth$799 / month20,000 messages a month
Prefer email?
sales@rendel.aiPrefer to write first?
Tell us about your app and we’ll show the right workflow in a tailored demo.