The best contact-enrichment vendor you'll ever use is the bottom three lines of the emails already sitting in your inbox. Roughly 82% of business email contains a signature with at least a name and title — job titles, direct phone numbers, LinkedIn URLs, company websites, all volunteered by the sender, all sitting unparsed while teams pay data vendors for stale versions of the same fields.
Two cookbook pages make the case for treating an inbox as a CRM data feed: the CRM integration overview maps the sync patterns, and the signature enrichment recipe shows the extraction itself. Run the pipeline against an Agent Account — a beta feature giving your app a mailbox it owns outright — and every message that lands at sales@ or partnerships@ becomes a structured enrichment event, no human forwarding required.
Regex beats an LLM here, and it's not close
Counterintuitive in 2026, but the recipe's argument holds: signatures aren't unstructured prose. They're predictably structured — 3 to 6 lines, separated from the body by -- per RFC 3676, drawing from a small set of field types. A regex catches more than 95% of well-formed signatures, runs in microseconds, costs nothing per message, and produces the same output every time. The LLM fallback is justified only for the last few percent, and the recipe's advice is to skip it for version one.
