How to Get TCPA-Compliant SMS Consent Without Killing Your Form Conversions

Most contractors handle SMS consent one of two ways. Either there's no consent language anywhere and texts go out to whoever filled out the form, or someone's lawyer handed over three paragraphs of legalese that now sits above the Submit button, and form completions dropped.

Both are fixable. Compliant consent is a single line of text and one unchecked box. The problem is almost never the length of the disclosure — it's that it's written like a contract instead of a sentence.

Quick note before anything else: I'm not a lawyer and this isn't legal advice. The TCPA carries real per-message penalties and plaintiff firms actively look for violations in home services. Have your own counsel review whatever you end up using. What follows is the practical structure most compliant setups share.

What "express written consent" actually requires

For marketing texts, you need prior express written consent. Boiled down, the person has to affirmatively agree to receive marketing messages by text at the number they gave you, and they can't be forced to agree in order to get a quote.

That produces four practical rules:

1. The box starts unchecked. A pre-checked box isn't consent, it's an assumption. Same goes for "by submitting this form you agree to receive texts" buried in fine print — that's implied, not express.
2. It's a separate box from your terms and privacy policy. Bundling SMS consent into a general "I agree to the Terms" checkbox is one of the most common mistakes, and it's the easiest one to attack later. Two boxes, or one terms box and one optional SMS box.
3. It can't be a condition of service. Your form has to submit successfully with the SMS box unchecked. If your validation blocks submission, you've created the exact problem the rule exists to prevent.
4. The disclosure names who is texting, what kind of messages, that rates may apply, and how to stop.

That last point is where forms get bloated. You don't need a wall of text. You need one compact sentence and a link-free reference to your policies.

Copy-paste wording for a website quote form

Put the checkbox directly under the phone number field, not at the bottom of the form. People are already thinking about their phone number at that moment, so the ask feels connected instead of tacked on. Label it clearly and keep the disclosure to one line underneath in smaller type.

Checkbox label:

Text me about my quote and occasional offers from [Company Name].

Disclosure beneath it:

Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe, HELP for help. Consent is not a condition of purchase. See our Privacy Policy and Terms.

That's it. Two lines. It doesn't tank conversions because it isn't asking for anything scary — and because it's optional, people who don't want texts just leave it alone and finish the form.

One thing worth separating out: transactional messages about the job they requested ("our tech is 20 minutes out," "here's your estimate") sit differently than marketing blasts. Many contractors word their checkbox to cover both, then keep a second internal flag for who agreed to marketing. If you only ever plan to send appointment logistics, your language should say that and nothing more. If you plan to send promotions later, say so now — you cannot retroactively upgrade transactional consent into marketing consent.

Phone intake script

When someone calls in, you're collecting the number verbally, so the consent has to be verbal too — and it has to be documented. Add this to your intake script after you take the phone number:

"Is it alright if we text you at that number with updates about this job and occasional offers? You can reply STOP anytime, and it won't affect your service either way."

Then log the answer in the lead record. Not "customer said yes" three days later from memory — a yes/no field on the intake form, filled in during the call. If your phone system records calls, note that recordings exist for that date. If your CRM lets you stamp who took the call, use it.

In-person estimate sheet

Same structure as the web form, on paper or tablet. A checkbox next to the phone line on the estimate or work authorization, with the disclosure printed underneath in readable type — not four-point font at the bottom of the page. Have the tech leave it blank if the homeowner doesn't check it themselves. A tech checking boxes on the customer's behalf to "save time" is how a whole batch of consents becomes worthless.

If you use paper, scan it. The signed sheet is your evidence, and it's useless in a filing cabinet in the shop while the claim is being handled by someone else.

Leads from Google Local Services, Angi, and similar sources

This is where people get burned. A lead marketplace passing you a phone number is not the same as that homeowner giving you consent to text.

Some platforms do collect SMS consent on your behalf, some collect consent only for the platform, and some collect none at all. Read your specific agreement and the actual consumer-facing language the platform shows. If the platform didn't disclose your company name and marketing texts, assume you don't have marketing consent from that lead.

What you can generally do with those leads is respond to the inquiry they submitted — they asked for a quote from a provider and you're the provider. Treat that as transactional and keep it about the job. If you want them on a text list, ask for consent in that first exchange or on the estimate sheet.

What to log so a claim is defensible

The consent isn't the asset. The record of the consent is the asset. For every lead with SMS consent, store:

• Date and time, with timezone
• IP address (for web forms)
• The phone number as entered
• The exact disclosure wording shown at that moment — not a link to your current page, the literal text
• Which checkbox was checked, and that it was unchecked by default
• Source: web form, phone intake, estimate sheet, event booth
• Any later opt-out, with timestamp

That fourth item trips up almost everyone. If you reword your form in March, a February consent has to be provable against the February wording. Version your disclosure text and store the version ID with each record, or snapshot the full string. When a demand letter shows up, the difference between "here is exactly what they saw and when" and "we think it said something like this" is the whole case.

Which old leads can you text, and which get email only

If you're going back through a cold list, sort it into three buckets.

Text-eligible: documented express written consent, with a record of the wording. Age alone doesn't void consent, but a very old consent for a number that may have been reassigned is a real risk — reassigned-number databases exist for this reason, and scrubbing is worth it before any large send.

Email only: no consent record, consent bundled into a general terms checkbox, consent that only covered transactional messages, or leads imported from a marketplace or purchased list. Also anyone who ever replied STOP — that opt-out is permanent unless they opt back in themselves.

Don't contact: do-not-contact requests, disputes, and anything where you can't identify the source at all.

In practice, that means most contractors reactivating a two-year-old lead list should start with email for the bulk of it and text only the slice with clean records. That's not a limitation so much as a sequencing decision — email re-engagement can earn you a fresh, documented SMS opt-in from people who are actually interested, which is a better list than the one you were tempted to blast.

If you're staring at a few thousand old leads and trying to work out who you can message and how, that sorting problem is most of the work. RescueLead handles re-engagement campaigns over email and SMS, including keeping consent status and opt-outs straight per lead, so the compliant path and the easy path end up being the same one.