The six-field form that passes TCPA, Rule 4.2, and the firm's own intake script.
Representation check gated before step three. Consent artifact timestamped with IP, user agent, and the exact language version. Pushes to the CRM in two seconds.
In the package.
- Three-step intake with autosave and resume
- Rule 4.2 representation check gate before the final step
- Third-party certified TCPA consent artifact per submission
- Hidden source fields for channel, campaign, and keyword attribution
- Direct push to Clio Grow, Lawmatics, Captorra, Lead Docket, HubSpot, Zapier
- Weekly compliance log export (CSV), seven-year retention
The form is where the firm's exposure begins. Treat it like evidence.
A good form stops you from buying your own TCPA class action.
Vacated FCC one-to-one consent dropped the floor for the whole lead-gen industry. Our module operates above the floor on purpose: one disclosure, one checkbox, one firm. No partner lists, no cross-sell, no third-party-marketing fine print.
Rule 4.2 is a form problem before it is a conduct problem.
Asking 'are you currently represented' as a dropdown, with the question in plain English and the answer bound to the artifact, is the only clean record. We gate step three on 'no.' If a person later says yes, the record shows the question was asked at the moment they completed intake.
Attribution is a form problem too.
Six hidden fields in the module capture GCLID, FBCLID, UTM campaign, source, and keyword. The CRM lands on each row with every one of these pre-filled, which is how you report Cost per Signed Case by channel without the firm's bookkeeper calling you.
Questions firms ask before they sign.
Does the form generate a TCPA consent artifact?
Yes. For every submission, a JSON artifact is written containing the timestamp, IP, user agent, page URL, and the exact wording of the consent block the person saw. The artifact is stored in a WORM-mode bucket, retrievable by submission ID. We retain for seven years and can produce one in under five minutes on request.
What happens if the person says they are already represented?
The form blocks step three and shows a short message explaining that we will not take their information. This is the Rule 4.2 safeguard. The attempt is logged, the artifact is not generated, and no record is pushed to the CRM.
Can we customize the fields?
Yes, within reason. We will not add fields that are prohibited at intake under your state's advertising rules (specific case-value estimates, for example). Beyond that, add or remove fields as the firm's intake script requires.
Does it work on the firm's existing website?
Yes. The module ships as a vanilla JS bundle (28KB gzipped) with a CSS override layer that matches your brand tokens. It drops into any CMS or static site. The practice website build uses this module by default.
What CRMs does it push to?
Clio Grow, Lawmatics, Captorra, Lead Docket, HubSpot, Pipedrive, and Salesforce out of the box. Anything else, we push by webhook into Zapier.
Can the form run on a Facebook or Google ad lead form instead?
Those platforms do have on-platform lead forms, and they convert well, but the TCPA artifact they generate is thinner than what we store on our form. For a firm carrying its own TCPA exposure, the on-site form is the safer choice.
Firms buying this usually bundle these.
See the full growth-services catalog or the attorney lane overview.
Pick a plan, start the first of next month.
À la carte starts the first of next month. Bundled into Core, Pro, Elite, or Enterprise, it starts the day the tier does. Prepaid balance, week to week, no term lockup.