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.

What it is

Two independent consents — transactional SMS about the demo, and optional promotional messaging — each stored with the full text that was rendered on the page, plus the page URL, the IP and the user agent. Consent is only recorded when a phone number was actually given, because there is nothing to evidence otherwise.

Also called: TCPA consent · A2P 10DLC opt-in · SMS permission · text message consent

See it
The consent record
Area
Platform & Admin
Group
Compliance
System
Marketing Site
Solves
3 named problems
01The consent text is posted FROM THE PAGE, so the record reflects what was actually rendered rather than a server-side copy.
02Each consent is stored only when its box was ticked AND a phone number was supplied.
03Page URL, forwarded IP and user agent are captured alongside.
A stored consent row: email, phone, both consent flags, and the full verbatim text of each, with page URL and timestamp. Sample data — no customer information appears here.
How it works
  1. 1The consent text is posted FROM THE PAGE, so the record reflects what was actually rendered rather than a server-side copy.
  2. 2Each consent is stored only when its box was ticked AND a phone number was supplied.
  3. 3Page URL, forwarded IP and user agent are captured alongside.
  4. 4The same wording is used on the marketing site and in the blog modal, because it has to match what was filed.
  5. 5The endpoint never echoes back what it stored.
Why we built it

Two sentences from the route carry it: "The wording is stored verbatim rather than referenced, because the site copy will change and the record has to keep meaning what it meant on the day it was signed." And on scope: "Only stored for a box that was genuinely ticked — an unticked box has no consent to evidence." The blog modal repeats the exact strings for the same reason — "that text is the A2P consent record; it has to match what we filed."

The problem
  • Consent referenced live site copy that changes underneath it.
  • Ticked boxes without a phone number produced meaningless records.
  • A second form with different wording would break the filed message flow.
Sound familiar?
What you get
A consent record that still means what it meant on the day it was signed
Transactional and promotional consent tracked separately
The same wording everywhere it is asked for

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 →