Legal · Kontracks

SMS Consent Disclosure

The literal opt-in language used by every Tenant Business on the Kontracks platform. Provided for The Campaign Registry (TCR), Telnyx, and the U.S. wireless carriers as the verifiable reference for the 10DLC brand and campaign each Tenant Business registers in their own legal name.

Overview

Kontracks is a multi‑tenant CRM SaaS platform operated by LWR Technologies, Inc. Each Tenant Business (U.S. roofing, siding, and decking contractors) using the platform registers their own 10DLC brand and campaign with The Campaign Registry (TCR) in the Tenant's own legal name. Kontracks operates the technical pipeline; the Tenant is the registered sender of their own messages and the brand the carriers see.

Recipients opt in to receive SMS through one of the two methods documented below. Every consent record is stored on Kontracks servers with a timestamp, the literal consent text shown, the source (web form ID or proposal ID), and the recipient's IP address. Records are producible on demand in the event of a carrier audit.

Method 1 — Online intake form (Web-to-Lead)

Each Tenant Business operates one or more public intake forms hosted on the Kontracks platform at URLs of the form app.kontracks.com/embed/form/<form‑id> or embedded as an iframe / inline component on the Tenant Business's own website. The form asks for the recipient's name, contact info, and details about the work they're requesting. The final step shows the consent checkbox (un-checked by default).

Literal consent text shown next to the SMS opt-in checkbox
  • The checkbox is NOT pre‑checked.
  • Submission of the intake form is NOT conditioned on the SMS consent checkbox being ticked — the carriers prohibit "forced opt-in" (a required phone field plus a required consent checkbox). A visitor can submit the form and become a lead without consenting to SMS; in that case the platform records the lead but suppresses all SMS to that number.
  • On submit, the platform records timestamp, IP, form ID, the visitor's consent flag (true / false), and the literal consent text version that was shown.
  • Sample verifiable URL (HyTech Roofing demo form): app.kontracks.com/embed/form/hytech-demo

Method 2 — E-signed proposal

When a recipient signs a Tenant Business's proposal via the Kontracks e-signature flow at app.kontracks.com/p/<token>, the final acceptance modal displays a separate, optional SMS opt-in checkbox alongside (not above) the contract agreement checkbox. The two are independent: the recipient may sign the proposal with or without ticking the SMS box.

Literal consent text shown next to the optional SMS opt-in checkbox in the acceptance modal
Checkbox is unchecked by default. Submit button is gated only on the contract-agreement checkbox, never on this SMS box. If left unticked, the platform marks the recipient as non-consenting and suppresses all SMS to that number (proposal acceptance and SMS opt-in are decoupled, per carrier requirements).
  • Optional SMS-consent checkbox appears on every Kontracks e-signed proposal, rendered in the final acceptance modal below the "I agree" contract checkbox.
  • On submit, if the SMS box was ticked, the platform recordssmsConsentGiven=true, the literal consent text version, the timestamp, and the proposal token alongside the signature record. If unticked, the platform records smsConsentGiven=false and the proposal still completes normally.
  • Sample verifiable proposal link (HyTech Roofing demo proposal, redacted): app.kontracks.com/p/demo

What every message includes

Every SMS sent through the Kontracks platform, regardless of opt-in method, contains:

  • The Tenant Business name as the lead identifier (e.g. "HyTech Roofing:" prefix) — the Tenant is the registered TCR brand, not Kontracks
  • The specific transactional content (e.g. "Hi Sarah, our crew is on the way — ETA 25 min.")
  • "Reply STOP to opt out, HELP for help" on every outbound message in the conversation, not just the first. Every transactional template in the Kontracks send pipeline includes this trailer.

Opt-out handling

The Kontracks platform automatically processes the following stop keywords (case-insensitive) sent to any tenant number: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. On receipt, the platform:

  • Flags the contact as opted out within seconds (database commit) and stores an audit record on the contact's tenant
  • Sends a single confirmation reply (exact text): "You are unsubscribed. No more messages will be sent. Reply START to opt back in."
  • Refuses to deliver any further SMS to that number from the tenant in question — both manual sends from reps and automated cron messages are blocked at the send-pipeline layer (src/lib/sms.ts) before any Telnyx call is made

Recipients may re-subscribe at any time by replying START. On receipt, the platform sends: "You are re-subscribed and will receive messages again. Reply STOP at any time to opt out."

HELP keyword handling

Recipients can reply HELP (or INFO) at any time to receive an auto-reply identifying the Tenant Business (the registered brand) and providing contact info (exact text):

{Tenant Business}: Reply STOP to unsubscribe. Call {Tenant Phone}. Msg & data rates may apply.

The Tenant Business name and phone are pulled live from the tenant's Company Settings at reply time, so the HELP response always identifies the registered brand the recipient gave consent to — not Kontracks.

Record retention

Consent records — including timestamp, source, literal consent text, and recipient identifier — are retained for a minimum of seven (7) years after the consent is captured or revoked, in accordance with the TCPA statute of limitations and FCC 10DLC carrier-audit requirements.

Contact

Privacy questions: privacy@kontracks.com.
Carrier-compliance audit requests: legal@kontracks.com.