Book a demo

The demo form stores a legally-shaped consent record, lands the enquiry on the sales pipeline as a new lead, mints a booking reference for whoever picks it up, and sends the prospect an acknowledgement.

What it is

A public, rate-limited endpoint behind every demo CTA on the marketing site and the blog. It validates the email, writes a consent record with the verbatim wording that was on screen, creates or reuses a pipeline lead under the agency organisation, mints a short booking reference onto that card, sends a branded acknowledgement, and notifies the team internally — with every step after the consent record best-effort so nothing can cost the lead.

Also called: contact form · demo request · lead form · get a demo

See it
Book a demo
New lead 2
Marlin Hoover
$46k
Delia Yoder
$30k
Contacted 2
Sutter Kline
$26k
Ronan Petsch
$61k
Ivy Brubaker
$46k
Estimate 2
Ivy Brubaker
$55k
Gideon Alt
$35k
Sold 2
Marlin Hoover
$62k
Delia Yoder
$45k
Sutter Kline
$51k
The form beside the resulting pipeline card, with the consent record's stored wording shown underneath. Sample data — no customer information appears here.
How it works
  1. 1IP rate limiting allows ten submissions a minute — generous enough for a real burst, tight enough to stop a script flooding the table.
  2. 2The email is validated; everything else is optional and length-clamped.
  3. 3The consent record is written first, because it is the part that must not be lost.
  4. 4A pipeline card is created — or an existing active one for that email reused — with source 'Website — demo request' and next step 'Call them'.
  5. 5A short booking reference is minted and written onto the card so the email and the card can be matched without a name search.
  6. 6The acknowledgement and the internal notification are both fired without blocking the response.
Why we built it

The route records exactly what was wrong (L2B-3XKDRZ): "the form was a prototype whose submit handler only set local state. Nothing was stored, nobody was notified, and the success screen admitted on the page that it wasn't wired up — while the A2P campaign we filed with Twilio named that same form as the opt-in mechanism for our demo/sales-follow-up messaging program. A carrier vetter following the message flow would have found a form that demonstrably captured nothing." So the job "is not 'save a lead'. It is to create the CONSENT RECORD that TCPA/CTIA and A2P 10DLC review require."

The problem
  • The form captured nothing while being cited as the opt-in mechanism in a carrier filing.
  • Enquiries never reached the sales pipeline.
  • Nobody could match an enquiry email to a pipeline card without searching by name.
Sound familiar?
What you get
Every enquiry becomes a consent record and a pipeline card
The lead carries a reference that matches the acknowledgement email
Nothing downstream can lose the enquiry — the record is written first
What's inside
Book a demo without leaving the article
Any demo button on a marketing page opens the real form right there — it never dumps the reader back on the homepage.
The consent record
Who consented, to what exact wording, from which page, when, and from what IP — stored verbatim, because the site copy will change and the record has to keep meaning what it meant on the day.
A demo request becomes a lead
Every demo request lands as a New lead on the sales board with its source, its next step and a booking reference — and a repeat request from the same email reuses the existing card instead of creating a second one.
The acknowledgement email
The prospect gets a branded acknowledgement carrying their reference and no scheduling ask, while the team gets an internal notification with the enquiry and both consent flags.

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 →