Same lead, same business, two versions of the next nine hours. One is what happens today. The other is what happens when the first twelve steps don't need a person awake.
An autoresponder replies to everyone with the same sentence, including the duplicate who already has an owner, and including the one worth eleven times the others.
The flow in the right-hand column does six things an autoresponder can't: it checks whether this person is already in the CRM, enriches what's missing, scores them, routes to the right owner, offers a slot from a real calendar, and writes the whole thing back. The reply is the last step, not the only one.
A flow that fires is easy. A flow that tells you it didn't fire is the part people skip — and it's the reason "we set up Zapier once" usually ends with somebody checking the inbox manually again.
A token expires. The flow stops. No error reaches a human, and the leads simply stop arriving. We alert on absence — no lead in 6 hours during business hours is itself the alarm.
A retry fires twice and the same person gets two messages twenty seconds apart. Every run is keyed, so a repeat is recognised and dropped rather than sent.
Routing rules drift as the team changes. Unroutable leads go to a queue with a reason, never to a default person who quietly ignores them.
"Did we contact this person?" needs an answer six months later. Each run is appended with its inputs, so the record survives the person who built it.
Website form, ad lead form, WhatsApp, inbox, phone. No migration and no new CRM — the flow reads what exists.
It runs on n8n in your own workspace. If we stop working together it keeps running, and you can open every node.
Synthetic lead, synthetic timings, illustrative figures. The conversion assumption is an input on this page, not a claim — set it to your own and the maths follows.