SMS Opt-In Overview

Program summary

This page documents how users opt in to SMS from CristOS, for review by Twilio and carriers. CristOS SMS messages are operational — project and account coordination — not promotional marketing.

CristOS is pre-launch. SMS will not be enabled until A2P approval is complete and users provide explicit consent in the app.

Program name

CristOS SMS Notifications

Sender

CristOS Dev, LLC

Use case

Operational / account & project coordination (not marketing)

Opt-in type

Explicit, optional, unchecked by default, separate from account creation

Message frequency

Message frequency varies.

Cost

Message and data rates may apply.

Opt out / help

Reply STOP to opt out. Reply HELP for help.

CristOS App SMS Opt-In Flow

The SMS consent flow appears inside CristOS signup or the account/settings area. The mock panel below shows the consent control reviewers would see in the app.

• Users enter or confirm a mobile number.
• Phone number collection alone is not SMS consent.
• SMS consent is captured through a separate checkbox/toggle that is unchecked by default.
• The user must actively select the checkbox/toggle to opt in.
• SMS consent is optional and not required to create an account or use CristOS.
• Users can opt out by replying STOP or by turning off SMS in app settings.
• Users can reply HELP for help.
• The consent control links to the Privacy Policy and SMS Terms.

Reviewer walkthrough

This is a real sequence:

1. User signs up or opens account settings. A user creates a CristOS account or opens the account/settings area in the app. Account creation collects first name, last name, email, password, phone number, and ZIP code (company and role optional). None of these steps enroll the user in SMS.
2. User enters or confirms a mobile number. Collecting a phone number is not treated as SMS consent — consent is captured separately in the next step.
3. User sees a separate, unchecked SMS consent control. Below the number, the user sees an unchecked checkbox with the disclosure below.
4. User actively opts in. The user must actively tap the checkbox to enable it and then save. If the box is left unchecked, no SMS consent is recorded and the user keeps full access to CristOS.
5. Consent is recorded. When the user opts in, CristOS records the consent timestamp, the phone number, the consent source, the disclosure version, and the policy URLs (/privacy and /sms-terms) as a verifiable record of opt-in.
6. Opt out anytime. The user can opt out at any time by replying STOP to any message or by turning off SMS in app settings. Replying HELP returns help information.

Consent disclosure (verbatim)

The required elements appear together with the consent control: Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is not required to create an account or use CristOS.

Sample messages

Examples of the operational messages a consenting user may receive:

Data handling

See the Privacy Policy for full details and the SMS Terms for program terms.