The bridge from the marketing site to the pipeline. A demo request creates a lead card under the agency organisation in the new-lead stage, tagged with source 'Website — demo request', next step 'Call them', and an external source marker. An existing active card for the same email is reused. A short booking reference is minted and appended to the next step so the card and the acknowledgement email can be matched.
Also called: form to CRM · lead capture to pipeline · website enquiry
- 1After the consent record is safely written, the pipeline card is created best-effort.
- 2An existing active card for that email is found first and reused, so a second enquiry does not create a duplicate.
- 3The card records source, external source, entered-stage and last-action timestamps.
- 4A booking code is minted for the owner on the roster and written onto the card as 'Call them — ref XXXX'.
- 5The booking link is kept on the card rather than pushed at the prospect.
The comment states the position: "A demo request IS the top of our funnel. Land it as a New lead under the Leads 2 Build org so it shows on /platform/pipeline with the rest." The booking-link decision is deliberate and argued: "WE CALL THEM (Keith 08-21). The booking link is still minted and kept ON THE CARD so whoever picks the lead up can send it if a time needs arranging — but it is deliberately NOT pushed at the prospect… Someone who asked for a demo and is immediately handed a different next step is being managed; the call is where we earn the right to steer."
- Marketing enquiries never reached the sales board.
- Repeat enquiries created duplicate cards.
- A booking could not be matched to the enquiry that produced it.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →