Account memory that outlives the rep

​

The scenario

​

Step 1 — Scope every note to the account

client.record(
    space_id="accounts",
    content="Their security lead blocks anything without SSO; procurement follows whatever he says.",
    user_id="acme-corp",
    agent_id="rep-jordan",
)

​

Step 2 — Brief the new owner in one call

profile = client.get_user_profile(space_id="accounts", user_id="acme-corp")
print(profile["context"])

​

Step 3 — Ask the questions a handover should answer

print(client.ask_about_user(
    space_id="accounts",
    user_id="acme-corp",
    query="What have we committed to, and what has blocked this deal before?",
))

​

Step 4 — See what the previous rep was working on

client.retrieve(space_id="accounts", query="open commitments", user_id="acme-corp", agent_id="rep-jordan")

​

Evals

1. Write fifteen notes on one account across three months from two different reps.
2. Run the handover question. Check it surfaces commitments from both reps.
3. Ask about an account with no notes — it should say so rather than generalise from similar accounts.
4. Have the receiving rep read the briefing before their first call and tell you what was missing. That gap list is your note-taking convention.

​

Guardrails

• A commitment recorded is not a commitment tracked. Memory will tell you what was said; it does not chase it. Keep the obligation in the system that has dates and owners.
• user_id is your identifier for the account. Keep it stable — renaming it orphans every memory written under the old one.
• Don’t mirror the CRM. Record the understanding, not the activity log; the CRM is already better at the latter and the noise degrades retrieval.

​

Built from