1. Get clear permission first
Before promotional or recurring SMS messages are sent, the customer should knowingly opt in. The sign-up flow should clearly identify Rewards RUS and/or the participating business, describe the type of messages, and provide links to the applicable Terms and Privacy Policy. Consent should not be a condition of purchasing goods or services.
Keep records of the consent method, date/time, phone number, disclosure shown, and the program the customer joined. Do not add people to marketing lists from purchased, rented, or scraped phone-number lists.
2. Explain what customers can expect
Messages may include food truck location and schedule updates, daily specials, weekly promotions, monthly offers, loyalty-related notices, and other messages described during opt-in. Message frequency varies based on merchant activity and customer settings. Standard message and data rates may apply.
3. Make opt-out easy
Customers should be able to revoke marketing consent at any time. Support the standard keyword STOP and honor opt-out requests promptly across the relevant messaging program. A confirmation message may be sent to confirm the opt-out; do not continue marketing messages unless the customer opts in again.
Customers can reply HELP for assistance. Provide a monitored support contact or other clear help path. Common keywords and carrier handling can vary by messaging provider, so verify the implementation with your SMS service.
4. Use recognizable, useful messages
Identify the business or program in the message where practical. Keep content relevant to the consent the customer gave. Avoid misleading claims, excessive frequency, deceptive links, or messages outside the program's stated purpose. Protect phone numbers and message logs with appropriate access controls.
5. Follow carrier and legal requirements
In the United States, application-to-person messaging may be subject to carrier policies and registration requirements, including A2P 10DLC for applicable traffic, along with applicable federal and state laws and industry guidance. Requirements depend on the sender type, use case, and provider. Registration is not a substitute for valid consent.
6. Sample opt-in disclosure
Use this as a starting point only. Adapt the disclosure to the actual sender, message types, technology, opt-in method, and applicable provider requirements. Do not publish a consent flow that promises functionality the system does not support.
7. Sample message
8. Manage complaints and privacy
Provide a way to contact the program operator, investigate complaints, and correct consent or suppression records. Do not sell or share SMS consent data for third-party marketing. Explain any service-provider processing in the Privacy Policy and ensure vendors are appropriately configured.
Important note
This page is general educational information, not legal advice or a certification of compliance. Before launching SMS, review current FCC rules, carrier requirements, your SMS provider's policies, and advice from qualified counsel. Update this page whenever the actual program or messaging practices change.