Smart Lead Capture
A form submission is persisted before a single notification goes out, so a failed email or Telegram call can never lose the lead.
Problem
Leads arrived through a form and fanned out to email, Telegram and WhatsApp notifications. When one of those services hiccuped, the lead itself sometimes went missing — nobody had a record, just a failed notification in a log nobody read.
Before
Notifications and record-keeping had no defined order; a downstream failure could mean the lead was never stored anywhere.
After
The lead is written to the sheet first, unconditionally. Every notification after that is a convenience, not a dependency.
Interactive workflow
Click through the actual node graph
Ordering is the design decision
There's only one hard requirement in a lead-capture flow: the lead must exist somewhere durable. Everything else — the auto-reply, the Slack-style pings, the WhatsApp nudge — is there to speed up follow-up, not to guarantee it happened. So the sheet write is step one, before any external call that could fail, rate-limit, or time out.
What each notification is for
The auto-reply email sets expectations with the lead immediately. The owner alert, Telegram alert and WhatsApp alert (via Twilio) are three different channels aimed at the same goal — make sure a real person sees the lead fast — because relying on a single channel means a muted phone or a full inbox becomes a missed lead.
Impact
Zero lost leads regardless of which downstream notifier is having a bad day.