SMS Program & Consent
Last updated: 2026-07-02
Revenue Recovery Engine (“RRE”, “we”, “us”) is a multi-tenant SaaS platform operated by SmartFlow Digital LLC (West Virginia LLC, EIN 42-2806160, registered at 110 Main Street, Beckley, WV 25801). This page explains how recipients consent to receive SMS communications sent through our platform and how those communications are governed.
Who sends the messages
RRE provides messaging infrastructure to small US service businesses (HVAC, plumbing, roofing, electrical, auto repair, etc.). When an SMS goes out through our platform, it is sent on behalf of one of those businesses (the “Service Provider”) to one of that Service Provider’s existing or prospective customers (the “Recipient”). The Recipient is in a prior relationship with the Service Provider, not with RRE.
How Recipients opt in
Service Providers collect two separate categories of consent from Recipients, in line with FCC 47 CFR §64.1200 (as amended December 2023) and CTIA Messaging Principles & Best Practices. Marketing consent is collected through its own distinct opt-in mechanism, never bundled with consent for transactional messages:
- Transactional / operational consent — required to receive service-related messages (missed-call text-back, speed-to-lead response to the Recipient’s own form submission, appointment confirmations and reminders). This is the consent required for the Service Provider to respond to or service a request the Recipient initiated.
- Marketing / promotional consent — a separate, optional, unchecked-by-default opt-in that allows the Service Provider to send promotional or reactivation SMS (periodic check-ins, special offers, return-customer campaigns). Declining this consent does not block transactional messaging.
The primary opt-in method is a web form on the Service Provider’s website (a lead-capture, contact, quote-request, or booking form). The opt-in workflow is:
- The Recipient enters their mobile phone number on the form.
- The Recipient sees two separate, unchecked-by-default consent checkboxes with the TCPA-compliant disclosure language shown below — a required transactional checkbox and an optional marketing checkbox. Nothing is pre-checked and the two consents are never combined into one checkbox.
- The Recipient affirmatively checks the transactional box (and, if they choose, the separate marketing box), then submits the form. Consent is not a condition of purchase.
- The consent, the category (or categories) selected, and a timestamp are recorded. Declining the marketing box never blocks transactional messages.
Where a Recipient instead opts in offline — for example, verbally during a prior service call, or on a paper intake form at the Service Provider’s place of business — the Service Provider documents the same two distinct consent categories using equivalent language, with marketing always kept separate and optional. The web-form disclosure below is the uniform standard every Service Provider is contractually required to mirror at any capture point.
Sample disclosure language
Service Providers are contractually required (via our Terms of Service and onboarding attestation) to display TCPA-compliant disclosure language adjacent to every consent-capture point. Below is an example of the disclosure language a Service Provider uses on their web form:
Example consent capture (Service Provider’s website):
See the Service Provider’s Privacy Policy and Terms.
Mockup — actual forms appear on each Service Provider’s own website. The two-checkbox consent mechanism and the unchecked-by-default marketing checkbox are uniform across Service Providers per our onboarding contract; the visual styling varies.
What Recipients receive
Messages sent through our platform fall into two groups, each governed by its own consent category:
Transactional / operational (requires transactional consent)
- Missed-call text-back — If the Recipient called the Service Provider and was not answered, the platform sends an automated text from the Service Provider’s business number acknowledging the call and inviting the Recipient to text back with details. This is a service response to the Recipient’s own inbound call.
- Speed-to-lead response — If the Recipient submitted a form or sent an inbound text, the platform sends an automated, personalized response within seconds. This is a direct reply to the Recipient’s own outbound contact.
- Appointment confirmations & reminders — Booking confirmations and one reminder ~24 hours before the appointment.
Marketing / promotional (requires separate marketing consent)
- Reactivation — Periodic check-in messages to previously-engaged Recipients on the Service Provider’s existing CRM list. Sent only to Recipients who gave the Service Provider explicit marketing consent through the separate, optional promotional-messages checkbox shown above — never via bundled consent. Recipients who declined the marketing checkbox at intake never receive these messages, even if they consented to transactional SMS.
Message frequency
- Capped at 1 message per 24 hours per recipient, enforced at the platform level by
lib/compliance/preflight.ts. - Quiet hours: no messages sent between 8pm and 9am local recipient time, regardless of Service Provider configuration.
- Reactivation cadence: 30-60 days total duration, typically one message per week to non-responding Recipients.
How Recipients opt out (STOP keyword)
Recipients can opt out of further SMS at any time by replying with any of the following keywords (case-insensitive):
- STOP, UNSUBSCRIBE, END, QUIT
Opt-outs are processed within seconds. The Recipient receives a confirmation reply identifying the Service Provider:
“You will no longer receive messages from [Service Provider]. Reply START to opt back in.”
The opt-out is platform-wide: no further messages are sent to that phone number from any campaign on the Service Provider’s account, including reactivation, speed-to-lead, missed-call text-back, and reminders. Opt-outs are immutable and timestamped in our compliance log.
How to get help (HELP keyword)
Recipients can reply HELP or INFO to any message to receive a response identifying the Service Provider plus contact information:
“For help, contact [Service Provider] at [phone]. Reply STOP to opt out, START to opt back in.”
Rates, carriers, and limitations
- Message and data rates may apply per the Recipient’s carrier plan.
- Carrier support: messages are delivered via Twilio over US carrier networks (AT&T, T-Mobile, Verizon, US Cellular and their MVNOs).
- We do not guarantee delivery; carriers may block messages flagged as spam or due to A2P compliance issues outside our control.
Service Provider attestation
Before a Service Provider can send any message through our platform, they complete platform onboarding which requires affirmative attestation that:
- They have collected prior express written transactional consent from every Recipient on their list for any service-related SMS, under TCPA, CTIA, and CASL rules.
- They have collected separately prior express written marketing consent from every Recipient they intend to message via reactivation or other promotional campaigns — never bundled with transactional consent, never via a pre-checked or required checkbox.
- They will only enroll Recipients with explicit marketing consent in reactivation campaigns; Recipients who consented only to transactional SMS are excluded from promotional sends at the platform level.
Both attestations are logged with a timestamp at signup. Service Providers must produce consent records (separately for each category) on demand if requested by carriers, regulators, or by RRE.
Prohibited content (SHAFT)
Service Providers attest at onboarding that they do not sell or market sex/dating, hate, alcohol, firearms, tobacco, cannabis, gambling, or payday loans (collectively, “SHAFT”-category content prohibited by US carriers on A2P SMS). Accounts found to be violating this restriction are immediately suspended.
Privacy and Terms
Privacy Policy (www.smartflow.tools/privacy) · Terms of Service (www.smartflow.tools/terms)
Contact
Questions about our SMS program, the consent records held by a Service Provider, or how to verify a specific message: email support@smartflow.tools.