Dev shares 8 identity-mapping rules after his WhatsApp agent matched the wrong person 3 times
petrusenko_max · x · 2026-11-04
After his WhatsApp agent matched event guests to the CRM by first name alone — and got the wrong person 3 times — developer @petrusenkomax shared the identity map he now uses.
Key rules:
- Key people by email, not name; merge multiple emails under one row
- Use IG handles as a second key
- Full names only count as a match if unique in crm.csv; two possible matches = no match, routed to human Notes
- Manual overrides (rsvp, greetas, bucket, weekof) beat the agent
- Hand-followed people get marked so the agent never re-plans them
- One follow-up per person per week
His core warning: a wrong match looks exactly like a right one in the plan — you only notice when the message lands with someone else.
More from coding & agent
- Building a personal MCP book pipeline: discover, download, auto-translate to Kindle — vista8 · 2026-11-04
- Building an AI-powered find-download-translate-Kindle pipeline with MCP tools — vista8 · 2026-11-04
- GitHub Octoverse 2026 Ranks NousResearch's Hermes Agent #1 in Open-Source Engagement — Teknium · 2026-11-04
- Autonomous launches Lamp, a $699 open-source desktop companion robot with customizable skills — dee_hw · 2026-11-04
- $500 Claude plan burns a week of credits every 36 hours, user complains — StephanSturges · 2026-11-04
- FireFlash coding agent hits 46.2% on Terminal-Bench 4.0 at 30x lower cost — VioletNPeng · 2026-11-04