AI Memory for Client Management: Stop Asking "Who's This?"

Updated January 2026 | 6 min read

"Draft a follow-up to John about Q2."

AI asks: "Who's John? What's Q2 about?"

You've told AI about John three times this month. It forgot. Again.

Every chat starts from zero. You re-explain clients, projects, history. The assistant that's supposed to save time costs time.

The problem is memory. ChatGPT doesn't store client details. It doesn't know John runs a chiropractic clinic, prefers morning calls, and needs content for three locations.

Context files fix this. One file per client. Name, company, project scope, communication preferences, history. AI reads it before every interaction.

You say "follow-up to John about Q2" and AI knows exactly who John is.

What Client Management Looks Like With Context

Give AI a context file for each client—one markdown document per relationship—and it becomes client-aware.

Each client file stores:

• Basic info (name, company, role, contact details)
• Project scope (what you're working on, timeline, deliverables)
• Communication preferences (email vs. calls, response time, meeting availability)
• History (past projects, decisions made, what worked/didn't work)
• Notes (pain points, goals, things to remember)

Now when you ask AI to draft an email, schedule a call, or summarize a project status, it has full client context.

No more "who's this?" No more re-explaining.

What Goes in a Client Context File

Start with the basics. Who they are, what you do for them.

Client info section example:

## Client: John Martinez

**Company:** Limitless Chiropractic (Austin, TX)
**Role:** Owner / Lead Chiropractor
**Contact:** john@limitlesschiro.com | (512) 555-0123
**Locations:** 3 clinics (North Austin, South Austin, Round Rock)

**Project:** SEO + Content Marketing
**Retainer:** $2,500/month
**Start Date:** Oct 2025
**Contract:** Month-to-month, 30-day notice
    

Add communication preferences. How they like to work with you.

Communication section example:

## Communication Preferences

- **Email:** Prefers short, bullet-point updates
- **Calls:** Morning only (8-10am CT)
- **Meetings:** Bi-weekly check-ins, 2nd & 4th Tuesday
- **Response time:** 24-48 hours is fine, doesn't need same-day
- **Style:** Direct, no corporate speak
- **Pet peeve:** Long emails with buried questions
    

Document the project scope. What you're delivering, when.

Project scope section example:

## Scope

**Deliverables:**
- 4 blog posts/month (1,200-1,500 words each)
- Google Business Profile optimization (all 3 locations)
- Monthly SEO report
- Quarterly keyword refresh

**Topics:**
- Chiropractic care education
- Injury prevention
- Sports performance
- Wellness (holistic focus, no medical claims)

**Avoid:**
- Medical diagnosis content
- Competing with MDs (stay in chiro lane)
- Generic wellness fluff
    

Track history. Past wins, past mistakes, context for decisions.

History section example:

## History

**2025-10:** Onboarded. Initial audit showed low local rankings, thin content.
**2025-11:** Published 4 posts, set up GBP. Traffic +15%.
**2025-12:** Holiday slow month. John requested pause on new content.
**2026-01:** Resumed. New focus: sports injury content (John's specialty).

**What works:**
- Case study style posts (patient success stories)
- Video embeds (John records short clips)
- Local SEO focus (Austin-specific keywords)

**What doesn't:**
- Generic "back pain 101" content
- Long-form (2,000+ words)—John's audience wants quick answers
    

Add notes. Things to remember that don't fit elsewhere.

Notes section example:

## Notes

- John is ex-NFL (played safety, knee injury ended career)
- Passionate about sports performance work
- Wants to position clinic as "athlete-focused"
- North Austin location is highest revenue
- Considering 4th location in 2026 (Georgetown)
- Wife handles admin, prefers not to be CC'd on emails
    

How to Set It Up

Create one file per client: client-john-martinez.md

Add five sections:

1. Client info — Name, company, contact, project basics
2. Communication preferences — How they work, response expectations
3. Project scope — Deliverables, topics, boundaries
4. History — Timeline of work, what worked/didn't
5. Notes — Anything else worth remembering

Save it in Obsidian. Tell Claude Code to read it when you reference the client.

One file per client. Permanent relationship memory.

Before and After

Before (no context):

You: "Draft a follow-up to John about Q2 deliverables."

AI: "Who is John? What deliverables are you referring to?"

You: "John Martinez, the chiro client. We do SEO for him."

AI: "Got it. What's the scope of the SEO work?"

You: "4 blog posts a month, GBP optimization, reports."

AI: [Generates generic corporate email]

You: [Spends 10 minutes rewriting it]

After (with context):

You: "Draft a follow-up to John about Q2 deliverables."

AI: [Reads client-john-martinez.md]

Draft output:

Subject: Q2 Plan — Sports Performance Focus

John,

Here's the Q2 lineup:

Content:
- 12 posts (April-June), sports injury focus
- 4 video embeds (can you record short clips?)
- North Austin GBP update (new service pages)

SEO:
- Keyword refresh for "sports chiropractor Austin"
- Monthly reports (same format as Q1)

Let's sync 2nd Tuesday in April to review. Grab a time here.

Victor

No back-and-forth. AI knew the client, the scope, the communication style.

What This Fixes

You stop re-explaining clients every chat. Client details live in the file.

You stop forgetting client preferences. Communication rules are documented.

You stop generic client emails. AI knows the relationship, the history, the tone.

You stop asking yourself "wait, what did we decide last month?" History section has it.

What This Doesn't Fix

It won't manage deadlines for you. You still need a project management system.

It won't auto-update when things change. New project scope? Update the file.

It won't replace actual client notes from meetings. This is reference, not transcription.

Why This Works

Your brain can't hold 10+ client relationships with full context. You forget details. Mix up names. Lose track of who prefers what.

AI can hold infinite context. But only if you give it to AI.

The client file is how you offload relationship memory. Name, preferences, history, notes. AI reads it. AI remembers.

One file per client. Permanent memory.

That's how you stop asking "who's this?" every time.