Lead Intake Automation

Where leads actually get lost

• — The form emails a person instead of writing to a system, and the email is read on a phone and never actioned.
• — The submission lands in a tool nobody opens daily.
• — The lead arrives with no owner, so everyone assumes someone else has it.
• — A retry or a double-click creates two records and both are half-worked.
• — A failed integration fails silently — the form says thank you and nothing was written anywhere.

The properties of an intake path that holds

• — Durable first: the submission is written to storage the business controls before any notification is attempted.
• — Idempotent: a retry, refresh or webhook redelivery cannot create a second record.
• — Journaled: every sync attempt records success or the exact error, so a silent failure is impossible.
• — Universally routed: every submission lands in one inbound pipeline, then is copied into the pipeline for its type.
• — Attributed: page, campaign and UTM parameters are captured at the moment of submission.

One universal inbound pipeline

Multiple forms should not mean multiple disconnected systems. The pattern that survives growth is a single inbound table every submission enters — regardless of whether it came from a seller, a buyer, a wholesaler or a vendor — with a type column and a linked identifier pointing at the specialised record.

That single table becomes the daily review surface. If it is empty, nothing came in. If a row has no linked record, the routing broke and you can see it.

Testing intake like it matters

Intake should be tested the same way payments are tested: submit real, clearly labelled test records through the live form, confirm they appear in every destination, confirm resubmission does not duplicate them, then delete them. Reading the code is not a test.