ResponseFlow SMS Consent & Opt-In Flow

ResponseFlow overview

ResponseFlow provides web chat and request forms for small businesses so they can capture service requests, organize lead details, and follow up with customers.

SMS is used only for operational and service-related communication, such as request follow-up, appointment updates, missed-call follow-up, service reminders, and account notifications. Messages are not promotional marketing blasts.

Customer-facing SMS remains disabled until A2P approval is complete and proper consent has been collected.

Reviewer Verification: Exact Opt-In Paths

ResponseFlow uses the following SMS opt-in paths only. SMS consent is optional, not required to submit a request, and customer-facing SMS remains disabled until A2P approval and proper setup.

Path 1: Business owner opt-in

• Business owners may opt in during ResponseFlow account/setup configuration to receive operational lead alerts and reminders from ResponseFlow.
• The business owner's phone number is separate from SMS consent.
• Consent is optional.
• They may use ResponseFlow without SMS.
• Messages identify ResponseFlow and include STOP/HELP instructions.

Path 2: Customer website/widget opt-in

• A customer opens a ResponseFlow-powered website widget.
• The customer enters request details and mobile number.
• The SMS checkbox is unchecked by default.
• The customer must actively check the box to consent.
• If the customer does not check the box, the request can still be submitted.
• Consent wording includes message frequency, message/data rates, STOP, HELP, Terms, and Privacy.

Path 3: Customer hosted page opt-in

• A customer opens a public hosted page such as /t/{tenant_slug} or /p/{tenant_slug}.
• The same optional unchecked SMS consent checkbox is shown after phone number entry.
• Consent is not required to submit the request.
• The request can still be completed without SMS.

Path 4: Missed-call link path, when enabled after approval

• After A2P approval and tenant setup, a missed-call text may direct the customer to a ResponseFlow hosted request page.
• Any additional SMS consent on that hosted page follows the same optional unchecked checkbox flow.
• Customer-facing SMS remains disabled until approval.

Not currently used

• No SMS keyword opt-in is currently used.
• No paper form opt-in is currently used.
• No verbal opt-in is currently used.
• No in-store/offline opt-in is currently used.
• No QR-code-only SMS opt-in is currently used unless the QR code opens the hosted request page described above.

End-user website, widget, and hosted page opt-in path

1. The end user opens a participating business's public ResponseFlow hosted page or website widget.
2. The end user starts a request.
3. The end user provides request details.
4. The end user may provide a phone number.
5. After phone number collection, ResponseFlow shows a separate optional SMS consent prompt.
6. Consent is not preselected.
7. Consent is not required.
8. The user can choose yes, no, skip, or decline and still submit the request.
9. Providing a phone number alone does not create SMS consent.
10. Consent is recorded only when the user clearly opts in.

Consent checkbox wording

The checkbox is unchecked by default. The customer must actively check it to consent. Terms and Privacy links are shown near the consent wording.

Business owner and account user opt-in path

Business owners and authorized account users may separately opt in to operational ResponseFlow notifications during account setup or tenant notification setup. Owner SMS consent is optional and is not required to create a workspace or use ResponseFlow. Business owners can use email-only notifications.

Required disclosures

• SMS consent is optional.
• Checkbox is unchecked by default.
• Message frequency varies.
• Message and data rates may apply.
• Reply STOP to opt out.
• Reply HELP for help.
• Consent is not required to submit a request or use ResponseFlow.
• Providing a phone number alone does not create SMS consent.
• Terms and Conditions link: https://responseflow.app/terms
• Privacy Policy link: https://responseflow.app/privacy
• Mobile opt-in information is not sold, rented, or shared with third parties or affiliates for marketing/promotional purposes.

Sample messages

Owner messages are operational lead alerts and reminders for business owners who opted in. Customer-facing examples are used only after A2P approval, tenant setup, and proper consent collection.

Business owner examples

Customer examples after A2P approval and setup

Reviewer verification steps

• Open the public evidence page: https://responseflow.app/sms-consent
• Open a public hosted example page if safe and available: https://app.responseflow.app/t/test-pressure
• Start the request/chat flow.
• Enter a phone number when prompted.
• Verify that SMS consent is shown separately.
• Verify that the consent wording says Optional.
• Verify that consent is not required and the user can decline/skip and still continue.
• Verify Terms and Privacy links are visible/reachable.

If a hosted example page would create real production leads or email side effects, reviewers can use the static proof panels below as public visual evidence of the flow and exact consent wording.

Opt-in flow preview

These panels are static HTML/CSS previews of the end-user flow and consent prompt. They are not browser screenshots.

Contact and legal links

JLT Hotshot LLC d/b/a ResponseFlow

support@responseflow.app

Terms | Privacy