Inbound lead router and enricher

Leads arrive through a website form, a LinkedIn message, a forwarded email, and a phone note in someone's phone. Half get logged a day late, a quarter never get logged, and nobody can tell you which source actually converts.

1. 01

   Normalize the payload

   Every source is mapped into one internal lead schema before anything else runs, so downstream nodes never branch on source shape.

2. 02

   Deduplicate

   Match on email, then domain plus surname. An existing contact updates rather than creating a second record.

3. 03

   Enrich

   Company size, sector, country, and tech signals from a lookup provider, cached for thirty days so you never pay twice for the same domain.

4. 04

   Score

   Weighted rules on company size, sector fit, budget language in the message, and page path they came from.

5. 05

   Assign and notify

   Round robin inside the matching territory, Slack ping to the owner, task created with a due time.

6. 06

   Acknowledge

   Templated reply from the owner's address within ninety seconds, personalized on first name and the specific thing they asked about.

• Idempotency key on the source message id, so a replayed webhook cannot create a duplicate
• Enrichment failures degrade to unenriched rather than dropping the lead
• Dead letter queue with a Slack alert if the CRM write fails
• Rate limit backoff on the enrichment provider with a daily spend ceiling