AI for Virtual Assistants: Memory for Multiple Clients

Updated January 2026 | 7 min read

Monday morning. You're working on five different clients before lunch.

9am: Process invoices for the e-commerce client. They use QuickBooks, categorize shipping separately, and need invoices sent by the 5th.

10am: Schedule social media posts for the real estate agent. She wants posts at 8am and 5pm, never uses hashtags, and prefers Canva templates with her brand colors.

11am: Draft a proposal for the consultant. He likes two-page max, bullet points over paragraphs, and always includes case studies in the appendix.

You ask ChatGPT to help draft the proposal. It gives you a generic template. No mention of the two-page limit. Paragraphs instead of bullets. No case study section.

You'd have to re-explain his preferences anyway. Faster to just write it yourself.

AI has no memory. It doesn't know which client you're working on or how they want things done.

Why Generic AI Fails Virtual Assistants

Virtual assistants don't serve one client. You're managing 5, 8, maybe 10 different businesses at once.

Each client has:

• Different tools (one uses Asana, another uses ClickUp, another uses Trello)
• Different processes (invoicing schedules, communication preferences, approval workflows)
• Different brand voices (formal vs casual, emojis vs no emojis, first person vs third person)
• Different deadlines (monthly reports on the 1st, weekly check-ins on Fridays, quarterly reviews)
• Different contact lists (vendors, contractors, team members, clients)

Generic AI doesn't track any of this. Every time you need help, you re-explain which client you're working on and how they operate.

"I need to draft an email to reschedule a meeting. The client prefers phone calls over email, but their calendar is managed through Calendly. They're in Pacific time. Keep it short and friendly."

Next time, different client: "Draft an email to reschedule a meeting. This client is formal, prefers detailed explanations, and always CCs their assistant. They're in Eastern time."

Same task. Completely different execution. AI has no way to remember the difference.

What Virtual Assistants Actually Need From AI

You don't need AI to replace your judgment. You need it to remember which client you're working on and how they want things done.

AI should know:

• Client profiles — names, businesses, industries, time zones
• Communication preferences — email vs Slack vs Voxer, formal vs casual, response time expectations
• Tools and systems — which CRM, which project manager, which accounting software
• Brand voice — tone, style, formatting preferences, words to use or avoid
• Recurring tasks — invoicing schedules, report deadlines, social media calendars
• Key contacts — vendors, contractors, team members, frequently emailed people
• Standard operating procedures — how each client wants specific tasks done

When you say "Draft an invoice reminder for the e-commerce client," AI should know which client, which accounting software they use, which tone to use, and when invoices are typically due.

When you say "Schedule social posts for the realtor," AI should know posting times, platform preferences, brand colors, and whether to use hashtags.

This isn't automation. It's context routing.

How CLAUDE.md Works for Virtual Assistants

CLAUDE.md is a markdown file that lives in Obsidian. It tells Claude Code who your clients are and how they operate.

For virtual assistants, it contains:

Client Directory

One section per client. Name, business, industry, time zone, contract details (hours per week, retainer amount, start date). Claude knows who you're talking about when you reference a client by name.

Communication Profiles

How each client prefers to communicate. Email (formal), Slack (casual, quick responses), Voxer (urgent only). Response time expectations. Greeting styles. Sign-off preferences.

Tools and Access

Which tools each client uses. QuickBooks vs FreshBooks. Asana vs Monday. Gmail vs Outlook. Claude references the right tool when drafting instructions or troubleshooting.

Brand Voice Guidelines

Tone, style, formatting. Client A wants bullet points and bold headers. Client B wants flowing paragraphs. Client C uses emojis. Client D never does. Claude matches the voice to the client.

Recurring Tasks

Monthly invoicing for Client A (due by the 5th). Weekly reports for Client B (sent Friday afternoons). Social media scheduling for Client C (posts go live 8am and 5pm). Claude knows what's due when.

Key Contacts

Vendors, contractors, team members. When you say "email the graphic designer about the logo revisions," Claude knows which client's designer and their email address.

SOPs

How specific tasks get done for each client. Client A's invoice process: export from Shopify, upload to QuickBooks, email PDF by the 5th. Client B's proposal process: use the two-page template, include case studies, send as Google Doc for comments.

You write this once. Claude reads it every time. No more re-explaining client preferences.

What This Looks Like in Practice

Before CLAUDE.md

You: "Draft an email to reschedule tomorrow's call to next Wednesday at 2pm."

AI: "Subject: Rescheduling Our Call

Hi [Name],

I need to reschedule our call from tomorrow to next Wednesday at 2pm. Let me know if that works for you.

Thanks,
[Your Name]"

Generic. No client context. Wrong tone for half your clients.

After CLAUDE.md

You: "Draft an email to reschedule tomorrow's call with Martinez Consulting to next Wednesday at 2pm."

Claude: "Subject: Request to Reschedule Thursday Strategy Session

Good morning, David,

Due to a scheduling conflict, I'd like to move our Thursday session to Wednesday, February 5th at 2:00pm EST. I've updated the calendar invite and included the Zoom link.

Please confirm this works with your schedule. If not, I'm happy to find an alternative time.

Best regards,
[Your Name]

CC: Sarah (assistant, per client's standard practice)
Tone: Formal, detailed, professional (matches Martinez Consulting's communication style)"

Specific. Right tone. Includes assistant in CC. References the right time zone. Matches the client's expectations.

Another Example

You: "Create a social media post about the new listing for the real estate client."

Claude: "Post for Hannah Realty (Instagram & Facebook, scheduled for 8am tomorrow):

New listing alert! This 4-bedroom gem in West Oak just hit the market. Hardwood floors, updated kitchen, huge backyard. Perfect for families. DM me for details or to schedule a showing.

[Use Canva template #3 with Hannah's brand colors: navy and gold. No hashtags per client preference. Image: exterior front view.]"

Claude knows the client's name, posting times, brand colors, template preference, and hashtag policy.

Setup Takes One Afternoon

You're not building a CRM. You're writing a text file.

1. Install Obsidian and Claude Code (both free)
2. Create CLAUDE.md in your vault
3. Add client profiles — names, businesses, time zones, contract details
4. Add communication preferences — email style, tone, response expectations
5. Add tools and systems — which software each client uses
6. Add brand voice guidelines — formal vs casual, formatting preferences
7. Add recurring tasks — what's due when for each client
8. Add key contacts — vendors, contractors, team members
9. Add SOPs — how specific tasks get done for each client

Three to four hours of setup. AI that knows all your clients from that point forward.

When you onboard a new client, you add their section. When a client's preferences change, you update their profile. The file grows with your business.

This Isn't AI Replacing VAs

CLAUDE.md doesn't do the work for you. It doesn't log into client accounts or send emails on your behalf.

It saves time by remembering context. You don't re-explain which client uses which tools. You don't re-describe brand voice every time you draft something. You don't re-list contacts every time you need an email address.

You still make the decisions. You still review everything before it goes out. You still manage client relationships.

Claude just stops forgetting which client you're working on.

Who This Works For

VAs managing 3-10 clients at once. Executive assistants juggling multiple departments or team members. Freelance admins with recurring clients.

Anyone who's tired of context-switching between client preferences and re-explaining workflows to AI.

If you're already using Claude for VA work, CLAUDE.md makes it 10x more useful. If you've tried AI and found it too generic, this fixes that.