The 'Book my demo' form on the public site writes a record built for messaging-compliance review, not just a lead row. The consent wording is stored word-for-word alongside the submission, because the site copy will change and the record must keep meaning what it meant on the day it was signed. It is public by necessity, rate limited by IP, and never echoes back what it stored.
Also called: book a demo · opt in record · TCPA consent · A2P compliance · proof of consent
- 1A logged-out visitor submits the form
- 2The record captures the person, the verbatim consent wording shown on the page, the page URL, the timestamp and the IP
- 3The submission is rate limited by IP
- 4The response never echoes stored content back
The demo form on the public site looked like it worked and stored nothing at all — the confirmation text on the page itself admitted it was not wired up. That was worse than a lost lead. The texting programme filed with the mobile carriers named that same form as the place people agree to be contacted, so a reviewer following the trail would have found a form that demonstrably captured no agreement, putting the whole registration at risk. The form now creates a consent record — who agreed, to what exact wording, from which page, when, and from what address — and it stores the wording word for word rather than pointing at it, because site copy changes and the record has to keep meaning what it meant the day it was signed.
- Messaging-compliance review requires provable, dated, verbatim opt-in evidence
- Changing site copy destroys the meaning of a referenced consent
- A prototype form silently captured nothing
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 →