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

# Remember the people you meet

> Who they are, what they're working on, what they said last time — without keeping a CRM you'll never update.

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

## The scenario

You meet someone at a conference. Six months later they message you and you have
nothing — not their company, not what they were building, not the thing you
promised to send them.

A CRM would fix this if you ever updated it. You won't. The reason is that the
useful stuff arrives as sentences in conversation, not as fields in a form.

**What this recipe shows that no other does:** treating a *person* as the unit
of memory, so everything you ever learn about them accumulates under one name
and comes back as a briefing.

## Setup — once, then never again

```bash theme={null}
claude mcp add --transport http anona https://memory.anonalabs.com/mcp \
  --header "Authorization: Bearer anona_live_YOUR_KEY"
```

Add the [Agent Skill](/integrations/skills) too. MCP gives the assistant the
*ability* to remember; the skill gives it the *habit*, so you stop having to say
"remember this".

```bash theme={null}
npx skills add anonalabs/Anona-Memory-SDK
```

## Using it — there is no step 2

You talk normally:

> *"Met Priya at the Berlin meetup. She's building an agent for warehouse
> logistics, hit the same pgbouncer problem we did. Said she'd share their
> config. Two kids, one just started school."*

Nothing else happens. No form, no tags, no "save" button.

Months later:

> *"What do I know about Priya?"*
> *"Who have I met who works on logistics?"*
> *"Did I owe anyone a config file?"*

The third one is the interesting one — you have forgotten the person's name and
you are searching by the *obligation*. A notes app cannot answer that.

## Evals

Worth checking before you trust it with anything that matters:

1. Tell it three things about one person across three separate sessions.
2. In a fresh session, ask what you know about them. All three should come back.
3. Ask something about them you never said. It should say it doesn't know —
   an assistant that fills the gap plausibly is worse than one that forgets.
4. Ask a question that names no one, only a detail ("who was the warehouse
   person?"). That is the query that proves this is memory and not a contact list.

## Guardrails

<Warning>
  **This is other people's personal data, kept by you.** Notes about someone's
  family, health or job situation are exactly the kind of thing that reads
  badly out of context, and the person never consented to it. Record what helps
  you be a decent correspondent, not a dossier.
</Warning>

* **Don't record what you were told in confidence.** The assistant will recall
  it cheerfully, months later, in front of whoever is watching your screen.
* **Names collide.** Two people called Priya will merge into one confusing
  briefing unless you give the assistant a distinguishing detail when you first
  mention them.
* **This is a private space by default.** If you share it, everything about
  everyone goes with it — see
  [Support memory the whole team shares](/use-cases/shared-team-support-memory)
  for how sharing actually works before you turn it on.

## Where to go next

The same shape, but for a product you are building for other people rather than
for yourself: [Everything you know about one user](/use-cases/one-user-profile).