KretaOSHelp
Sign in
Client memory

What becomes memory

Which touches KretaOS reads for facts and promises, what it deliberately throws away, and what it never reads at all.

Updated 13 Nov 2026

KretaOS builds each client's memory by reading what your team logs and syncs and keeping what the client said or what a touch revealed. It is just as careful about what it leaves out, because a memory full of noise is a memory nobody trusts.

What KretaOS reads

  • Synced email. Mail with your clients from each connected Gmail.
  • Logged touches. Everything filed through Log, the Log activity card, outcomes typed when closing a task, and touches logged by Ask AI or the voice assistant.
  • WhatsApp chats. Read a stretch of conversation at a time rather than message by message: the messages in each quarter of an hour are read together a couple of minutes after it ends. Old chat history brought in when a number is connected is not mined.
  • Meetings. The notes and transcript of a recording, or a transcript you added, once it is attached to a client.
  • Imports. Notes columns in a file you import.
  • Your own Ask AI questions, sometimes. If you tell Ask AI something about a client in passing ("Anil said they're moving to a new plant"), it can be remembered. A message that asked Ask AI to do something is never mined, because it was an instruction, not news. A Viewer's chats are never mined.

What it throws away on purpose

  • Chat noise. "ok", "thanks 🙏", "noted", "good morning", a sticker or a thumbs-up says nothing about the relationship and is skipped before anything is read.
  • The touch itself. "Sent a WhatsApp to Vikram" is already on the timeline. Memory keeps what the touch revealed ("he did not answer", "awaiting his reply"), not that it happened.
  • Your own bookkeeping. When you mark a client dormant or change their tier, KretaOS does not record "the client considers the relationship dormant". That was your classification, not something they said.
  • Calendar invites as promises. "Review meeting scheduled for Tuesday" is the calendar's job. What was agreed in the meeting can be a promise.
  • Finished actions as promises. "Shared the invoices" is done, not owed.
  • Instructions hidden in a message. Text that tries to tell the AI what to do is treated as words to read, never as a command.

What it never reads

  • Team comments. Internal talk on a client page is never read by the AI and never becomes memory. See Comments and mentions.
  • Research briefs and Fill from website results. They help you prepare; they are not something the client told you.
  • Meetings pulled from your Google Calendar. The meeting is logged as a touch, but the invite is not mined. If the event is later cancelled or moved in Google Calendar, the logged meeting is taken off the timeline (and logged again once it has been held at its new time). A meeting your client declined is not counted. If a meeting on the calendar simply did not take place, press Didn't happen under it on the client's timeline, then Yes, it wasn't held. When nobody at the client answered the invitation, KretaOS asks you once, in the bell, whether the meeting happened.

Privacy follows the source

A fact learned from mail synced from your inbox is seen by the same people who can see that mail. A fact from a note you logged for the team is shared with the team. See Who sees synced mail.

Suggested updates after a meeting

When a meeting, call, mail, WhatsApp chat or note clearly changes something on a client's record, KretaOS suggests it: a deal's next stage, a new value or close date, a field, a next step, or who decides. It also notices when the conversation changes work you already have: a task moved to another day or time ("can we do Friday at 3 instead"), a promise given a new day, or a promise the client called off. Nothing changes until you say so.

At the top of the client's Overview, a card such as Suggested from meeting · 3 Nov lists each change with the quoted line underneath. Home shows a row like 3 suggestions · Northwind with Review suggestions, and the bell rings once per client per day.

The tick makes the change exactly as a hand edit would, and the row reads Applied with a link. The cross dismisses it for good. Accept all and Dismiss all do the whole card. If a change can't be made, it stays open and says why. To undo, use the record's normal controls.

KretaOS never suggests marking a deal lost or moving one back, and suggests money only in the deal's own currency. A suggestion from your own synced mail, calendar or WhatsApp is shown only to people who can see that message. To mute the bell, switch off Suggested updates under Intelligent alerts in Settings.

Related

  • Facts and where they come from — What a fact is, the six kinds KretaOS keeps, how verified and inferred differ, and how to trace a fact to its touch.
  • Who sees synced mail — Mail and meetings synced from your Google account are private to the people on them. Notes, calls and meetings you log are shared.
  • What is remembered from chats — How KretaOS turns WhatsApp conversations into client memory, leads and closed follow-ups, and what it deliberately ignores.
  • Comments and mentions — Talk about a client with your team right on its page, @mention a teammate to ring their bell, and keep it all internal.
Did this answer it?

Or write to contact@tamkis.com