The text-message program disclosure, including how to stop receiving messages.

SMS / Text Message Program Disclosure

Effective date: August 1, 2026 Published at: https://lawndominators.com/business/sms-terms — publicly reachable without a login, which is the URL carriers check during 10DLC campaign vetting.

Part A — The public-facing disclosure

This is the text intended for the public web page and for the 10DLC campaign registration form. It is written to be read by a homeowner.

Lawn Dominators SMS Terms

Program name: Lawn Dominators Service Notifications

Who sends these messages. Lawn Dominators LLC sends these text messages on behalf of the independent lawn-care company that services your property. The message will name that company. Lawn Dominators LLC operates the software and the phone number; the lawn-care company is the one you have a service relationship with.

What the program is for. Transactional messages about lawn service at your property: appointment scheduling and rescheduling, crew arrival notices, service completion notices, invoices and payment links, and summaries of what the crew found in your yard.

How you sign up. You are added to this program only when the lawn-care company that services your property records that you gave them permission — for example, when you agreed verbally at signup, agreed through their customer portal, or texted them to opt in. We do not add anyone from a purchased list, and having a phone number on file does not by itself sign you up.

Message frequency. Message frequency varies with your service schedule. This program sends one automated text when a visit at your property is completed, so a weekly service is about 4 to 5 messages a month and a monthly service is about one. You will not receive more automated texts than you have completed visits, and in practice no more than about 10 messages per month.

This is a transactional program, not a marketing one. These texts are about service at your property — scheduling, arrival, completion, and billing. We do not send promotional texts through this program.

Message and data rates may apply. Standard message and data rates from your mobile carrier may apply. Lawn Dominators does not charge you for these messages.

Carriers are not liable. Wireless carriers are not liable for delayed or undelivered messages.

To stop. Reply STOP to any message to stop receiving texts. You may also reply STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT. You will receive one confirmation, and then no further messages. Replying START or UNSTOP resumes them.

For help. Reply HELP for help, or contact:

The lawn-care company that services your property — they are the fastest route for anything about your service or your account.
Lawn Dominators LLC: support@lawndominators.com

Supported carriers. Messages are delivered over the major U.S. wireless carriers — including AT&T, T-Mobile, Verizon Wireless, U.S. Cellular, and their prepaid brands such as Cricket, Boost, and Metro by T-Mobile — through our messaging provider, Telnyx.

Privacy. See our Privacy Policy at https://lawndominators.com/business/privacy. We do not sell or share mobile phone numbers or SMS consent with third parties or affiliates for marketing purposes. Phone numbers are shared only with our messaging provider (Telnyx) for the purpose of delivering these messages.

Terms. See our Terms of Service at https://lawndominators.com/business/terms.

Part B — Consent language for the operator to use

This is the language a lawn-care business must present to a homeowner before recording SMS consent in the app. It exists because the app requires the operator to record where a consent came from, and that record is only worth something if the homeowner was actually shown a disclosure.

At signup (verbal, paper, or web form)

By providing your mobile number, you agree to receive text messages from [Company Name], sent through Lawn Dominators, about your lawn service — scheduling, arrival, completion, and invoices. Consent is not a condition of purchase. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. See [link to SMS Terms] and [link to Privacy Policy].

"Consent is not a condition of purchase" must stay in. A homeowner must be able to receive lawn service without agreeing to texts.

Marketing texts are a separate, higher bar

The app tracks marketing consent (marketingSmsConsent) separately from service-message consent (smsConsentStatus), and they are not interchangeable. Under the TCPA, promotional texts to a mobile number require prior express written consent — a signed (including electronically signed) agreement that clearly discloses the sender, that the messages are marketing, that automated technology may be used, and that consent is not a condition of purchase.

Do not turn on marketing consent from a verbal "sure, text me." That is enough for service messages. It is not enough for promotions.

Part C — What the software actually does

A precise description of the sending system, published so that carriers, operators, and anyone auditing this program can check it. Every statement below was verified against the application source code.

Sending

Automated texts go out through Telnyx (https://api.telnyx.com/v2/messages), pinned to a specific messaging profile so delivery always uses this campaign's 10DLC configuration. (supabase/functions/_shared/telnyxSms.ts)
Every organization sends from one shared Lawn Dominators number (+1-447-525-8758), not from a number of their own. Per-organization provisioning is explicitly out of scope today. (Module comment in telnyxSms.ts.) This matters for registration: the 10DLC campaign belongs to Lawn Dominators LLC, and the brand/campaign vetting describes Lawn Dominators as the sender acting for its business customers. Because one number serves many independent businesses, the campaign is registered on that basis rather than as a single-business campaign, and the message names the lawn-care company on whose behalf it was sent.
Emails go through Resend, from notifications@notify.lawndominators.com. (supabase/functions/_shared/resendEmail.ts, supabase/functions/_shared/businessInvoiceEmail.ts)

What actually sends automatically today

Only one automated text is live: the completed-visit invoice text, sent when an organization's billing automation deliveryChannel is set to sms. Every other message kind (schedule, reschedule, arrival, diagnostic summary) is composed by a human and sent from the device's own Messages app or share sheet. (autoSendCompletionInvoiceSms in supabase/functions/business-worker/index.ts; CustomerMessageChannel in src/business/customerMessaging.ts.)

This is why the stated message frequency in Part A is one text per completed visit, rather than a figure derived from the six message templates the app defines. Automated sending is additionally capped at 100 texts per organization per rolling hour — an abuse ceiling far above any real crew's completion volume, and one that fails closed if the limiter is unreachable. (BUSINESS_INVOICE_SMS_RATE_LIMIT_PER_WINDOW and BUSINESS_INVOICE_SMS_RATE_LIMIT_WINDOW_SECONDS in supabase/functions/_shared/messagingRateLimit.ts.)

Opt-out disclosure on every message

Every automated invoice text ends with "Reply STOP to opt out." — on every send, not just the first. This follows CTIA's Messaging Principles and Best Practices, which expect a standardized opt-out mechanism to remain continuously available for commercial texts. (OPT_OUT_LINE in supabase/functions/_shared/businessInvoiceSms.ts.)

Opt-out handling

Inbound messages arrive at a Telnyx webhook whose Ed25519 signature is verified; unsigned requests get a 403. Verified live in production. (supabase/functions/_shared/telnyxWebhook.ts, supabase/functions/telnyx-webhook/index.ts.)
Recognized opt-out keywords match Telnyx's own profile defaults exactly, so the app's stored consent state can never drift out of step with the carrier-level block Telnyx has already applied: STOP, STOPALL, STOP ALL, UNSUBSCRIBE, CANCEL, END, QUIT. Opt-in: START, UNSTOP. Help: HELP.
Matching ignores case, punctuation, and extra whitespace, per CTIA §5.1.3, which says a valid opt-out must not be defeated by "de minimis variances."
Matching is exact, not substring. "Please don't stop coming, the yard looks great" does not opt anyone out. CTIA warns against wording that can cause unintentional opt-out. Free-text opt-out requests are logged for a human rather than guessed at.

Operator obligation: because free-text requests are not automated, an operator must monitor replies and honor a plainly worded opt-out ("stop texting me please") manually. Ignoring one is a TCPA exposure.
Inbound replies are not yet surfaced in the app's communication history. Keyword opt-outs (STOP and the rest of the list above) are still honored automatically at both the carrier and the app level. What an operator cannot yet see in the app is a reply worded some other way. Until that view ships, operators are directed to monitor replies through the messaging account and honor a plainly worded opt-out by hand, and Lawn Dominators will act on any opt-out sent to support@lawndominators.com.

Consent enforcement

Consent is re-read from the database on the server immediately before every automated send, never trusted from anything captured earlier. A customer who opted out between scheduling and completion, or who was never asked, does not get the text. (autoSendCompletionInvoiceSms — "a real, server-side, current-as-of-right-now consent recheck".)
Recording consent requires a source (verbal-at-signup, customer-portal, imported, text-message-reply, or manual-office-entry). An office user cannot flip a consent switch with no evidence trail. (CUSTOMER_CONSENT_SOURCES in src/business/customerMessaging.ts.)
A phone number on file never implies permission to text. Consent is a separate, explicit field. (Comment on BusinessCustomer.phone in src/business/domain.ts.)

Data minimization

The messaging send ledger stores only IDs and a SHA-256 hash of the recipient number — never the raw number, never the message body, never the customer's name — specifically so the table cannot be browsed as a directory of phone numbers. (supabase/migrations/20260807120000_business_sms_rate_limit_and_send_ledger.sql.)

Part D — What this disclosure cannot protect against

Be clear-eyed about this. Publishing a good SMS disclosure reduces risk. It does not eliminate it.

TCPA statutory damages cannot be disclaimed. $500 per message, $1,500 per message if willful or knowing, with no cap and a private right of action. A contract between Lawn Dominators and an operator does not bind the homeowner who received the text.
The operator's consent record is the weakest link. If an operator ticks "verbal at signup" for a customer who never agreed, the text goes out, and the exposure is real — for the operator, and plausibly for Lawn Dominators as the entity whose number sent it. The app makes recording consent deliberate; it cannot make it truthful.
A shared sending number aggregates risk. One operator's bad consent practice can get the number blocked or the 10DLC campaign suspended, which stops messaging for every operator on the platform.
State mini-TCPA laws are stricter than federal law in several states (Florida, Oklahoma, Washington, Maryland among them), with their own consent standards, time-of-day restrictions, and damages. This program does not model them state by state, so an operator sending into one of those states carries that state's standard, not the federal floor.
Quiet hours. The TCPA restricts telephone solicitations to 8:00 a.m. – 9:00 p.m. in the recipient's local time. Transactional service messages are treated differently from solicitations, but the safe practice is to avoid sending outside that window. There is no time-of-day guard in the automated send path today. The completed-visit invoice text fires whenever a crew marks a visit complete, whatever the hour, so an operator who closes out a job late at night will send a text late at night. Operators should close visits during normal hours.

Sources

CTIA, Messaging Principles and Best Practices (May 2023), §5.1.3: https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf
Telnyx, Advanced Opt-in/Opt-out: https://developers.telnyx.com/docs/messaging/messages/advanced-opt-in-out
Telephone Consumer Protection Act, 47 U.S.C. § 227; FCC implementing rules at 47 CFR § 64.1200.