SMS Opt-In & Opt-Out Flow

SMS is disabled by default. Only the person who owns a phone number can opt that number in — administrators cannot enable SMS on behalf of anyone else. Consent is captured per notification list, inside the signed-in OneSiteKit web app.

Web-based opt-in (no SMS keyword). A signed-in user enables alerts for the mobile number already on their OneSiteKit profile, picks a delivery schedule, and ticks an "I agree" box. There is no inbound opt-in keyword — users do not text a word to start. Opt-out is keyword-based: replying STOP to any message cancels, and HELP returns help.

Open Admin → Notifications (Email tab)

The Notifications screen lists the email distribution lists for each notification type — User Requests, Environment Alerts, Dewatering/Well reports, and so on. Recipients on a list are emailed automatically when the triggering event occurs. Every recipient row carries its own unchecked SMS Opt-in checkbox (arrowed below) and a Send Test button. A user only sees an active checkbox on their own rows; other people's are non-interactive.

SMS opt-in is granted per list — the User Requests list and the Environment Alerts list are opted in separately.

Click your own SMS Opt-in checkbox — the SMS Notifications window opens

The window confirms the mobile number pulled from the user's profile and asks them to choose a delivery Schedule. It opens on Off, which sends no SMS and shows no consent text — nothing happens until a sending schedule is chosen.

Default state — Schedule set to Off, no consent disclosure, no messages sent.

Choose a sending schedule — the consent disclosure appears

Selecting Always or Mon–Thu reveals the consent disclosure and an "I agree" checkbox. The disclosure reads, verbatim:

"By opting in you consent to receive OneSiteKit text message alerts (operational notifications for your organization) at the number above. Message frequency varies. Msg & data rates may apply. Reply STOP to cancel. HELP for help."

Left: Always — an SMS for every new alert. Right: Mon–Thu — alerts only on Monday–Thursday, Mountain Time. In both, Save stays disabled until "I agree" is ticked.

The agreement links to the Privacy Policy and Terms of Use

The checkbox label — "I agree to the Privacy Policy and Terms of Use" — links directly to onesitekit.com/privacy (which contains the full SMS program terms) and onesitekit.com/terms, so the user can review both before consenting.

Both the Privacy Policy and Terms of Use are linked from the consent line.

Tick "I agree" — Save activates — then save

Once the "I agree to the Privacy Policy and Terms of Use" box is checked, the Save button turns solid blue and becomes clickable. No messages are sent and no consent is recorded until Save is pressed.

The SMS Notifications modal with 'Always' selected and the 'I agree to the Privacy Policy and Terms of Use' checkbox now ticked. The Save button is now solid blue and active.

Consent given — the "I agree" box is checked and Save is now enabled.

Opted-in state — the row shows the active schedule

After saving, that list's row shows a filled blue checkbox labelled SMS Opt-in · Always (or the chosen schedule) alongside Send Test. Because consent is per list, the other lists stay opted out — in the example below, User Requests is opted in while Environment Alerts — Urgent still shows an unchecked SMS Opt-in.

Opt-in is per distribution list — User Requests is on (Always); Environment Alerts — Urgent remains off.

Consent summary: The user opens the SMS window for one of their own rows, selects a schedule, reads the consent disclosure, ticks "I agree to the Privacy Policy and Terms of Use," and clicks Save. Messages are sent only to the mobile number already on their OneSiteKit profile, and only for the lists they opted into. No phone numbers are collected from outside the platform.

How a user unsubscribes from SMS

Users can opt out at any time in two ways: (1) reply STOP to any SMS message, or (2) uncheck the SMS Opt-in checkbox for that list in Admin → Notifications. Either method immediately stops further messages.

Uncheck the SMS Opt-in checkbox — confirmation appears

Unchecking an active checkbox shows a confirmation that names the exact phone number being unsubscribed and the list it applies to. The user confirms with OK.

An 'SMS Unsubscribed' confirmation modal reading '(780) 908-8768 has unsubscribed and will no longer receive SMS messages from the User Requests list.' with a single OK button.

The confirmation states the number and the specific list being unsubscribed.

Opted-out state — the checkbox returns to unchecked

After confirming, the row reverts to an unchecked SMS Opt-in checkbox and no further texts are sent for that list. The user can opt back in at any time by repeating the opt-in flow above.

Back to the opted-out state — the SMS Opt-in checkbox is clear.

STOP reply: Users may also reply STOP to any message at any time. Twilio processes the keyword and no further messages are sent to that number; the in-app checkbox is updated to reflect the unsubscribed state.