> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anonalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account memory that outlives the rep

> Stakeholders, commitments and objections stay with the account when the person handling it changes.

[← All use cases](/use-cases/overview)

<div className="uc-examples"><a href="https://github.com/anonalabs/Anona-Memory-SDK/blob/main/examples/support_bot_scoping.py">support\_bot\_scoping.py</a><a href="https://github.com/anonalabs/Anona-Memory-SDK/blob/main/examples/user_profiles.py">user\_profiles.py</a></div>

## The scenario

A rep leaves. Their accounts go to someone else, along with a CRM full of
activity records and none of the understanding — who actually decides, what they
objected to last time, what was promised on a call in March.

The next conversation starts from zero, and the customer notices.

## Step 1 — Scope every note to the account

```python theme={null}
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",
)
```

Two scopes, two jobs: `user_id` is the account the note is *about*, `agent_id`
is who wrote it. The account is what survives the handover.

## Step 2 — Brief the new owner in one call

```python theme={null}
profile = client.get_user_profile(space_id="accounts", user_id="acme-corp")
print(profile["context"])
```

## Step 3 — Ask the questions a handover should answer

```python theme={null}
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

```python theme={null}
client.retrieve(space_id="accounts", query="open commitments", user_id="acme-corp", agent_id="rep-jordan")
```

Scoping to both gives you one person's working view of one account — useful
during a handover, and correctly irrelevant afterwards.

## 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

<Warning>
  **These notes are about identifiable people and they are not private.** "Seems
  disengaged", "not the real decision maker" — write nothing you would not want
  read aloud. In many jurisdictions the individual can request a copy, which
  means [the deletion runbook](/use-cases/delete-a-users-memories) applies here
  too.
</Warning>

* **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

Both are complete, runnable scripts:
[`support_bot_scoping.py`](https://github.com/anonalabs/Anona-Memory-SDK/blob/main/examples/support_bot_scoping.py),
[`user_profiles.py`](https://github.com/anonalabs/Anona-Memory-SDK/blob/main/examples/user_profiles.py).