Closed and forgotten.
A chatbot's context ends when the session does. Every new conversation starts with someone — usually you — re-explaining the company, the people, the preferences and the decisions that were already made once.
Capabilities / Agent Memory
One chronological recordPer teammate, per organizationEvery channel feeds it
You explain it once.
How your company writes, who signs off, what was decided in March and why — right now that lives in your head, and everyone gets it from you. Agent Memory is the dated record a Busy teammate keeps of all of it: decisions, preferences, corrections and facts, gathered from every channel she works in and read before she acts.
Session vs. record
The second month should be easier than the first.
Appended and reread.
A Busy teammate writes what she learns into her record and reads it before the next job. You give the explanation once, and it holds across months of work without you checking that it held.
Memory is part of the teammate substrate. Every Busy teammate carries it from her first day; there is nothing to configure or maintain.
Across channels
What you say on the phone shapes the email.
The record is shared across every channel the teammate works in. A constraint given on a call is already in hand when she drafts the email, joins the meeting, or answers in Slack — so saying it once on one channel is enough to have said it.
Feedback becomes behavior
A correction is made once.
The correction is given once.
“Stop CCing the whole team on drafts.” Said in passing, on whichever channel the conversation happened to be in.
It becomes a working rule.
The teammate writes it into her record as she works — dated, with its source, alongside the decisions and facts around it.
Every job after honors it.
Each later draft goes to the reviewer alone, on every channel. The rule holds until you change it the same way you made it.
Repeating yourself is how people learn that feedback did not take. Here the correction is a durable entry, so the second time you notice the behavior is the second time you would have noticed it in a person: rarely.
Month over month
The record compounds into competence.
Early weeks are spent learning how your organization writes, decides and signs off. Because each of those lessons is retained, the work she can carry alone keeps widening — the same brief that took a review cycle in week two ships without one by week twelve, and the review cycle it no longer needs was yours.
Wk 2
Wk 4
Wk 6
Wk 12
Boundaries
Whose memory it is.
Each teammate keeps her own.
The record belongs to the individual teammate and the work she does. One teammate's operating knowledge does not blur into another's.
Scoped to your company.
Everything learned working for your organization stays inside it. Nothing carries to any other customer, in either direction.
Dated and in order.
Entries carry their date and source. When guidance changes, the record shows what changed and when, so behavior can always be traced to the instruction behind it.
Forgetting and misremembering
The two ways memory lets you down, and what holds here.
The record is read, not recalled.
Entries are written down as she works and read back before the next job. Nothing depends on a session staying open or a conversation staying short.
You can open it and see what she thinks is true.
The record is plain text with dates and sources. When she behaves a certain way, the entry behind it can be found, so a wrong belief is something the team can locate instead of guess at.
A wrong entry is fixed by saying so.
Tell her it is wrong on whichever channel you are on. The newer entry supersedes the older one from that point forward, and the history of the change stays visible.
The record holds what she learns doing your work. It grows by being told and corrected, and it is scoped to your organization, so what she holds is what you have given her.
Three durable layers
Mandates own. Playbooks instruct. Memory remembers.
The ongoing work.
Scope, objective, delegated authority, accountability, results, and cadence for work the teammate is trusted to drive.
Read about Mandates →The repeatable method.
Sources, steps, naming, filing, delivery, and limits for a job the teammate will run again.
Read about Playbooks →The facts and context.
People, preferences, decisions, and history learned through the work — the context both of the other layers draw on.
This page.The teammate substrate
The longer she works with you, the less you re-explain.
Decisions, preferences and corrections stay in force across every channel, and the record of how they got there stays readable. The context your company keeps in one person's head has somewhere else to live.