TCPA and A2P 10DLC for lawn care texting: compliance without killing your program

Will TCPA and A2P 10DLC rules kill your texting program? No. Texting compliance is simpler than the acronyms make it look, and a compliant program texts almost everything a lawn care company actually wants to send. The rules boil down to four habits we build into every program we run: get consent and keep proof, honor opt-outs instantly and everywhere, send at civilized hours, and register your traffic with the carriers. None of that requires a lawyer on retainer or a gutted marketing calendar. What it requires is doing the setup once, properly, instead of inheriting whatever your last three tools half-configured. One framing note before we start: this is practical operator guidance, not legal advice; the statutes have edges, state laws add wrinkles, and a real attorney should review your specific program.

What does the TCPA actually require?

The Telephone Consumer Protection Act is a 1991 federal law that, as applied to modern texting, comes down to consent: you need the recipient's permission to send automated texts to their mobile number, and the required strength of that permission scales with what you are sending. Informational messages tied to an existing relationship: appointment reminders, service notifications, billing notices: ride on ordinary consent, the number the customer gave you in the course of doing business. Marketing messages: promotions, upsells, win-backs: need prior express written consent: an affirmative, documented opt-in that names your company, says texts are coming, and was not buried as a condition of purchase. "Written" includes electronic: a checkbox on your quote form or a keyword opt-in qualifies. The practical implications: keep records of when and how each number opted in, because in any dispute the burden of proof is functionally yours; and stop texting numbers you scraped, bought, or inherited from a decade-old spreadsheet with no consent trail. Those lists are where the trouble lives.

What is A2P 10DLC, and why did my texts stop delivering?

Separate from the law, there is the carriers. A2P 10DLC (application-to-person, ten-digit long code) is the US carriers' registration system for business texting from regular local numbers. You register your business (brand) and describe your message types (campaigns), and in exchange your traffic gets legitimate throughput. Unregistered or misdescribed traffic gets filtered: messages silently dropped, no bounce, no error, just customers who never got the reminder. If your delivery rates sagged in the last couple of years, this is the usual culprit, not the phone gods. The registration itself is bureaucratic but shallow: legal business name and EIN matching your registration paperwork, a truthful description of your use cases, sample messages. Your texting platform files it for you; what they cannot fix is fiction, so describe what you actually send. Registration is simply the price of admission to the channel now, and it is worth every minute. Budget a couple of weeks of lead time before a new number can carry full volume.

Where do you capture consent?

The programs that stay clean capture consent at every intake door, with language written once and reused:

• The quote and checkout flow: an unticked marketing-consent checkbox next to the phone field, with plain wording about what and roughly how often you send.
• Phone sales: a scripted line ("we send service updates and occasional offers by text: OK to use this number?") with the answer recorded on the customer record.
• Door-to-door and paper agreements: the same wording printed above the signature.
• Keyword opt-ins: "text LAWN to our number" campaigns are self-documenting consent.

The operational rule that makes all of this real: consent must live as a field on the customer record, synced wherever sends happen, not as a memory in your CSR's head. And every message footer in a marketing sequence carries the exit: "Reply STOP to opt out."

Is each message transactional or marketing?

Walk your automation list once and label each sequence, because the label determines the consent it needs and the rules it follows. Visit reminders, post-service summaries, and payment notices on an open balance are informational; the machinery in our AR collections sequences is a good example of traffic that rides on the existing relationship. Upsell offers, prepay promotions, review asks framed with incentives, and win-back campaigns are marketing, full stop, and enroll only written-consent numbers. The tempting gray zone is the hybrid message: a service summary with a promo bolted on. Classify hybrids as marketing: the promotional fragment poisons the informational privilege. This is one more argument for a discipline we push elsewhere for pure deliverability and trust reasons: keep operational and promotional streams separate, a theme running through our whole email and SMS playbook.

How do you handle opt-outs and quiet hours?

Opt-out handling is the least forgivable place to fail, because software does it perfectly and free. STOP, and its siblings (UNSUBSCRIBE, CANCEL, QUIT, END), must halt sends immediately, trigger one confirmation message, and propagate everywhere: your texting platform, your CRM layer, and back against the customer record so no other tool resurrects the number. The classic failure is architectural: a customer opts out in one system while three others keep sending, which is why opt-out sync belongs on your integration requirements list, not your wish list. There is no architecture excuse here: we can connect RealGreen's customer records to pretty much any texting platform with an API, a Zapier connection, or a native integration, so a stranded opt-out is a wiring choice, not a limitation. And if you run a shared reply inbox, its software should be handling STOP before a human ever sees it (we cover that division of labor in the two-way inbox post). Quiet hours: federal rules bracket telemarketing to 8am-9pm local to the recipient, several states tighten that window, and decency tightens it further. Configure sends for mid-morning through early evening, in the customer's time zone, and you will never think about this paragraph again.

What do violations actually cost?

The TCPA carries statutory damages of $500 per violation, up to $1,500 where willful, and "per violation" means per text, which is how a sloppy 4,000-message campaign becomes a seven-figure theoretical exposure and a very real five-or-six-figure settlement. The plaintiffs' bar runs this as a volume practice: professional litigants keep clean records of texts received after opting out. Realistically, a residential lawn company's risk concentrates in three behaviors: texting purchased or consent-free lists, broken opt-out plumbing, and marketing to numbers that only ever consented to service updates. Avoid those three and your residual exposure is small; carrier filtering will punish sloppiness long before a courtroom does. If wiring consent fields, opt-out sync, and registration across your stack is not how you want to spend a month, that is the sort of infrastructure a managed email and SMS program exists to carry for you.

The takeaway: compliance is four habits, not forty: provable consent at every door, instant opt-outs synced everywhere, civilized hours, and honest carrier registration. Set them up once and your texting program gets safer and delivers better at the same time.

Five steps to a compliant program

1. Inventory every automation and label it informational or marketing; reclassify hybrids as marketing or strip the promo.
2. Add written-consent capture to every intake path and store consent as a synced field on the customer record.
3. Verify your A2P 10DLC brand and campaign registrations match what you actually send.
4. Test the opt-out path end to end: reply STOP, confirm the halt propagates to every system, and document it.
5. Set send windows to the customer's local daytime, then have an attorney sanity-check the program annually.