Shared Memory
Stop explaining the same things.
Your team explains the same preferences over and over: how the letters open, which format you use, who signs what. Marling can learn those once. Nothing is remembered until someone approves it.
How something gets remembered.
-
Marling notices a pattern
Overnight it reviews the day's conversations and looks for durable facts about how the office works, not about any one client.
-
It proposes, it does not decide
Each one arrives as a suggestion in a review queue, written in plain words so anyone can judge it.
-
A person approves or declines
An admin says yes or no to each. A declined suggestion does not come back, and nothing reaches an assistant without that yes.
-
Approved facts join every assistant
From then on every draft follows them, for everyone. The full list is on one page, and anything on it can be forgotten.
What leaves, what stays.
| Item | Where it goes |
|---|---|
| The nightly review of your conversations | Runs on the device, on text with identifiers already removed |
| Suggestions waiting for approval | Stay on the device |
| What has been approved, and who approved it | Stays on the device, with a record of each decision |
Never about a person
It proposes how the office works, never anything about an individual client: a preference about how letters open, not a fact about a client.
Off until you turn it on, and reversible
Shared Memory is switched on for your office rather than arriving on. Everything it holds is listed in one place, and anything there can be forgotten at any time.
Questions careful people ask.
Does it remember things about our clients?
No. It proposes durable facts about how the office works. Anything about an individual client is out of scope by design.
Who decides what it remembers?
An admin. Everyone who signs in can see both the suggestions and the current list; only an admin approves, declines or forgets.
Can we see everything it has learned?
Yes, in one place, in plain words, with the option to forget any of it whenever you like. There is no hidden memory.