Lesson 87.2 built the triage loop that handles each ticket well. But tickets end; relationships continue. Without a memory, every conversation restarts: the customer re-explains, the teammate re-asks, the promise made in March is forgotten by May. A CRM is that memory — used well, it makes the next conversation the most useful one yet.

The vocabulary, in plain language

• CRM: the shared record of customer relationships — who, what happened, what was promised, what comes next. A tool holds it; the discipline *is* it.
• Contact: a person — name, reach, preferences, consent. People make requests; companies do not.
• Account: the organization or household the contacts belong to — plan, seats, renewal date. One account, many contacts, one truth about the commercial state.
• Activity: anything that happened — email, call, ticket, purchase, opened guide. Activities are facts with dates, not impressions.
• Lifecycle stage: where they stand — lead, trial, customer, lapsed, advocate. Shared with Class 86's journey; updated when signals earn it.
• Owner: the named human responsible for the next step. Every open item has exactly one owner. "The team" owns nothing.
• Consent: what they agreed to receive and how to leave — carried over from Class 78, enforced here. The CRM is where suppression becomes real.
• Note: the human-readable summary a future helper needs — what matters, in plain words, with a date.
• Next step: the one committed action with an owner and a date. A record without a next step is an archive; with one, it is a workflow.

The mental model: the CRM is the chart at the foot of the hospital bed. Any qualified helper picking it up should know the history, the allergies (preferences, consent), what was promised on the last round — and what must happen before the next one.

Tool note: this lesson teaches the durable discipline — fields, owners, consent gating — which outlasts any one product's screens. When you implement it in a specific CRM, map each section of CRM-FIELDS.md to that tool's contact, company, activity, and list objects, and confirm where consent/suppression lives before importing anyone. For one widely used reference implementation, see the HubSpot knowledge base.

What the memory must preserve

Six things, no matter the tool:

1. Explicit requests — what they asked, verbatim enough to honor. Paraphrase loses the promise. 2. Relevant product use — plan, key features touched, known friction. Not surveillance — the context the next helper needs. 3. Support context — ticket links, resolutions, open issues. Never make them re-explain ticket #412. 4. Preferences — channel, cadence, topics, language. Respect recorded here prevents the Lesson 86.2 suppression failure. 5. Completed promises — what was delivered and when. The antidote to "nobody ever got back to me." 6. Assigned next actions — owner plus date. The chart always says who moves next.

Two disciplines keep this honest. First, write the note for a stranger: future-you in six months, or a teammate at midnight, should understand it cold — date, facts, promise, next step. Second, consent gates everything outbound: before any campaign or follow-up pulls a list, it filters on the CRM's consent fields. A CRM that cannot suppress is a liability machine.

Exercise: define your fields

Create CRM-FIELDS.md. Every field earns its keep with a purpose and an owner — fields nobody owns decay into fiction within a quarter.

# CRM-FIELDS.md — [Project]

## Contact
- Name / reach: purpose ___ / owner ___ / updated when ___
- Preferences (channel, cadence, topics): purpose ___ / owner ___
- Consent (scope, date, source, unsubscribe state): purpose ___ / owner ___

## Account
- Plan / seats / renewal: purpose ___ / owner ___
- Commercial notes: purpose ___ / owner ___

## History
- Activities logged as: ___ (fact + date + link) / owner ___
- Support context linked via: ___ / owner ___
- Promises (made / kept): ___ / owner ___

## Motion
- Lifecycle stage (values + entry rule): ___ / owner ___
- Next step (action + owner + date): ___ / rule "no open record without one": ___

## Hygiene
- Stale-record review (cadence + owner): ___ / duplicate rule: ___ / deletion on request: ___

Worked mini-example — creator-led publication: contact holds name, email, "weekly teardown only, no calls," consent "teardown + launch notes, joined via checklist 2026-04, unsub link honored." Account (for team seats): plan, seats, renewal. History: "asked for invoice copy 2026-08-03 — sent same day," "ticket #118 export bug — resolved with patch note." Motion: stage "member," next step "founder sends reading-path reply by Friday — owner: founder." Hygiene: monthly stale review by the editor; deletion within 7 days on request, confirmed in writing.

Finish line: a CRM-FIELDS.md where every field states its purpose, its owner, and when it is updated — including consent, next step, and hygiene.

Verify quickly: pick one real relationship and reconstruct it from the CRM alone. If a stranger could take the next step correctly — right channel, right promise, right owner — the memory works. If they would re-ask anything, add the missing field.

Common failure mode: the write-only CRM — hundreds of contacts, no owners, consent blank, next steps missing, duplicates everywhere. The team stops trusting it, works from memory and DMs, and the "memory" becomes a graveyard that still gets mailed. Fewer fields with owners beats fifty fields with none.

Check your understanding

1. What six things must the CRM preserve, and why does each matter to the next conversation? 2. What is the "write the note for a stranger" rule, and what breaks without it? 3. How does the CRM enforce consent — and what happens when it cannot?

Next

Memory exists — now use it at the right moments. Lesson 87.4 maps lifecycle follow-up that arrives with progress instead of noise: onboarding, activation, nurture, renewal, and reactivation, each with a trigger, a message, an exit, and an owner.