How Agency Command HQ captures messaging consent.

This public page documents the standard used for website/application SMS consent so campaign reviewers and users can see the disclosure without signing into the CRM.

Consent standard

SMS consent is presented separately from required Terms or account actions.
The SMS checkbox is optional and unchecked by default.
A user can decline SMS consent and still complete the primary non-messaging action.
The disclosure identifies the messaging program/sender, purpose, frequency, rates notice, STOP, HELP, Terms, and Privacy.
Proof of consent should retain the date/time, method, disclosure version, mobile number, and relevant source context.

Important: The actual campaign registration must list every consent method that is truly used. This page demonstrates the website/application consent standard; it does not create consent by itself.

Typical message categories

Account setup and security notices, requested appointment/follow-up messages, application or service-related updates, and other operational or conversational messages within the scope disclosed at opt-in.

Consent-flow example

Mobile messaging preference

This example is intentionally not connected to a messaging system.

Mobile number

I agree to receive recurring text messages from Agency Command HQ (or the authorized agency identified in the message) related to requested appointments, follow-up, account/service notifications, and other communications described at the time I opt in. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. Consent is not a condition of purchase or account access. See SMS Terms and Privacy Policy.

Continue without SMS

Consent record

What the production system should retain.

Consent is only useful if the sender can later prove what the recipient agreed to and when.

Who & where

Recipient mobile number, authenticated or matched identity where available, agency/sender, form or workflow source.

What & when

Timestamp, consent status, messaging purpose/program, and the exact disclosure/version shown at opt-in.

Lifecycle

Opt-out timestamp and source, consent refresh where required, and audit history without silently re-enabling a recipient.