Agent matched 3 contacts wrong in one blast: identity maps beat name joins
petrusenko_max · x · 2026-11-03
The author's WhatsApp follow-up agent for an improv class matched Luma guests to CRM contacts by first name only, sending wrong follow-ups to 3 people in one blast — a name join doesn't error, it just silently returns someone.
His fix: a per-person identity map —
- Key on email(s) plus Instagram handle
- Accept a name match only when the full name is unique
- Ambiguous matches go to Notes for human review, never into an automated send
Takeaway: a fast join on the wrong key looks exactly like a right one; identity resolution in agents must be designed explicitly.
More from coding & agent
- Researcher proposes 'oops-benchmark' to measure how often agents accidentally break things — konstmish · 2026-11-03
- Engineer Builds Mom's Restaurant Terrace with Codex, Skipping €20K Quotes — paw_lean · 2026-11-03
- MACR: confidence-guided relay multi-agent framework cuts token overhead 6x — Xu Liu · 2026-11-03
- Tiny specialized models trained weekly: sarcasm detection in <50ms on CPU — iamrobotbear · 2026-11-03
- Developer's WhatsApp agent now clears its own STOPs with signal-based gate rules — petrusenko_max · 2026-11-03
- Dev open-sources faster-chrome-devtools-skill after analyzing 2,500 agent uses — simpsoka · 2026-11-03