Systematic WhatsApp Chat Extraction for Context Packs

Codified from Gmail draft 19dc1310f8883da4 · Apr 24 2026

Honest answer first

You manually screenshotted 47+ messages for the EG context pack. That was the wrong way.
WhatsApp lets you export entire chat histories as text files — instantly, no screenshots.
This is the way every future consulting context-pack should start.

Time to set up: 10 min one-time. Time per chat thereafter: 60 seconds.

The 3 extraction methods (use #1 99% of the time)

Per-chat Export — what you should be using. Text file (.txt) of full chat with timestamps.
iCloud / Google Drive backup → 3rd party reader — only if you need historical chats from old phones. Risky for privacy.
WhatsApp Business API — only if it's a business number + you want programmatic access. Overkill for context-pack work.

Method 1 — Per-chat export (the only one you need)

iPhone:
1. Open the chat (e.g., "Zalmy at EG" group)
2. Tap the contact/group name at top → scroll to bottom
3. "Export Chat"
4. Choose:
- Without Media (faster, smaller file, works for text analysis)
- OR Attach Media (if you need photos/videos — much larger)
5. Share Sheet appears → choose:
- Mail to yourself (easiest)
- Save to Files → /On My iPhone/Hook Street/WhatsApp Exports/
- AirDrop to Mac
6. You get a .txt file (and a folder of media if you chose attach)

Android:
1. Open chat → 3-dot menu → More → Export chat
2. Same options re: media
3. Same export targets

WhatsApp Web / Desktop: ❌ Not available. Mobile only.

What the export looks like

[1/14/26, 8:29:47 PM] Zalmy Treitel: Hi I've set up the email, BH...
[1/14/26, 10:21:14 PM] Huvie Steinhardt: Ty. Let's talk tomorrow

Clean, parseable, every message timestamped. Same format as the EG _chat.txt (1,124 lines per the Session 13 audit).

Workflow — from export to context pack

Export the chat → save .txt to:
/Hook Street/[Client Name]/WhatsApp/_chat.txt
Open Claude Code in that working dir
Prompt:
Read _chat.txt. Extract all critical moments chronologically: - Commercial commitments (dollar amounts, deadlines, scope changes) - Decisions made or deferred - Off-scope work agreed to - Payment-related signals (positive or negative) - Anything Sam said in writing that protects/exposes him Output as structured chronological timeline with date, who said what, why it matters.
Claude Code produces the equivalent of EG-CONTEXT-PACK v3's Section 9 (the "Critical WhatsApp Moments" section took 5 hours manually — should be 10 min via export).
Plug into your Reusable Prompt template (see reusable-engagement-context-prompt.md).

Privacy + storage

Export files contain client conversations — treat as privileged
Save to private folder, NOT to public GitHub repo
After context pack built, decide:
Keep .txt for audit trail (recommended for active engagements)
Delete after engagement closes + 90 days

Watch-out — large group chats

If chat has 1000+ messages:

Without Media — usually under 1MB, parseable in one pass
With Media — can hit 100MB+, slow to email; AirDrop or Files
For very long chats, Claude Code may need to process in chunks

Build this for all active WhatsApp channels

Active channels worth periodic export:

"Zalmy at EG" group — done (EG_chat.txt exists)
Any future consulting client group
Mildred direct chat (for SOP / handoff continuity)
Asher direct chat (for legal trail)
Vendor groups (if they become contentious)

Cadence: Export each active client/legal channel monthly. Cumulative archive.

Done state

Folder structure: /Hook Street/[Client]/WhatsApp/_chat.txt + /media
Process is muscle memory: open chat → export → save
Future context packs are 10 min not 5 hours
Archive grows by client over time