SMS Consent Reference

1. Overview

This page documents how Loop captures SMS consent from consumers across all channels. Loop never broadcasts marketing SMS and never sends unsolicited messages.

Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes, including lead generators.

This reference is published as a complement to our Privacy Policy and Terms of Service to make the consent flow inspectable for carrier compliance review.

2. Consent Capture Mechanism

The consent flow follows the same pattern across every channel:

1. A consumer initiates a transactional action via Loop’s AI agent (booking, callback, demo, payment, account question, or similar request).
2. The AI agent offers SMS continuation with full disclosures — sender identification, opt-out instructions (Reply STOP), the standard rate disclaimer (Msg & data rates may apply), and links to our Privacy Policy and Terms of Service.
3. The consumer voluntarily provides their phone number in response, which constitutes express written consent under TCPA and CTIA principles.
4. A consent record is stored at the moment the phone number is received (see Section 6).
5. SMS is sent only in response to that consumer-initiated action. Loop does not initiate marketing or promotional outbound SMS.

3. Consent Flow Screenshots

The screenshots below illustrate the four-step consent flow exactly as a consumer experiences it.

4. AI Prompt Language

The AI agent uses the following exact language when offering SMS continuation. The prompt incorporates every disclosure required by TCPA, CTIA, and the messaging carrier:

Happy to text you the [confirmation/details]. Just share your phone number and I'll send it over. Reply STOP anytime to opt out. Msg & data rates may apply. Terms: https://loophq.dev/legal/terms | Privacy: https://loophq.dev/legal/privacy

The bracketed token ([confirmation/details]) is replaced at runtime with the specific transactional purpose identified by the agent (booking confirmation, appointment reminder, demo details, payment receipt, account alert, or follow-up to a request the consumer initiated).

5. Channels

The same consent capture pattern operates uniformly across every channel where Loop is deployed:

• Loop website chat widget at loophq.dev
• Facebook Messenger (when activated by the operating business)
• Instagram DM (when introduced)
• Other AI agent surfaces Loop deploys in the future

No matter the channel of origin, SMS continuation always follows the same consumer-initiated, voluntarily-provided, fully-disclosed pattern.

6. Consent Records Stored

For every consent captured, Loop retains a record sufficient to demonstrate the consent on request. The record includes:

• Phone number (E.164 format)
• Consent timestamp (UTC)
• IP address at time of consent
• Originating channel (e.g., loophq.dev widget, Facebook Messenger)
• The verbatim AI prompt text presented to the consumer
• The verbatim consumer reply that established consent

Retention follows the data retention terms of our Privacy Policy.

7. Compliance Basis

The consent flow described above conforms to:

• CTIA Messaging Principles and Best Practices, Section 5.1.2 (consumer-initiated consent), specifically mechanisms 1 (entering phone through website) and 5 (signing up at a point-of-service location). The current version of the Messaging Principles, along with the official PDF and supplementary materials, is published by CTIA.
• Telephone Consumer Protection Act (TCPA) express written consent standard for transactional messaging that is responsive to a consumer-initiated action
• Twilio Messaging Policy for A2P 10DLC consent collection

8. Linked References

• Privacy Policy — data collection, retention, and processor framework
• Terms of Service — SMS, Voice, and A2P 10DLC Compliance section
• Usage Policy — messaging acceptable use
• Sub-Processors — messaging carrier disclosure