What SMS opt-in means
SMS opt-in is the documented permission a customer gives a business to send text messages to their mobile number. Keep the sender, message purpose, disclosure, customer action and timestamp together, then check whether that permission is still current. A phone number or subscribed flag alone is not the complete record.
This guide is for dispensary owners, marketing managers, compliance officers, and technical teams implementing SMS programs. Use it when launching a texting program, auditing existing consent flows, registering for A2P messaging, or investigating elevated opt-outs or filtering events.
For broader context, review cannabis texting overview, cannabis SMS compliance, and 10DLC registration for dispensaries.
For a field-by-field record and example event history, use the consent and withdrawal record guide. Review its dated source notes alongside the current rules and provider requirements for your program.
What Blackleaf requires before texting
Blackleaf requires explicit recipient consent and age confirmation before any text, including service and support messages. In the message flow, the intended recipient selects the birthday on file; never disclose the saved birthday. These are Blackleaf requirements, not universal legal or carrier rules.
Explore Blackleaf Texting for dispensary campaigns and customer conversations. Texting is available with supported existing POS systems without a POS switch. Confirm the connection, sending route and permitted use case for your setup.
Key Takeaways
Consent must be clear, specific, and documented with timestamp and source.
Opt-in scope must match the type of messages you send.
Keep the disclosure, affirmative action, sender, purpose and timestamp together.
Apply current withdrawals to every affected campaign, automation and manual send.
Registration frameworks such as 10DLC require accurate description of opt-in flow.
An import or purchase does not create permission or restore withdrawn consent.
Step-by-Step Process
Define message categories: transactional, support, loyalty, marketing. Separate flows before collecting consent.
Create clear disclosure language stating who is texting, what type of messages, and how to opt out. Align this with compliance standards.
Capture the actual disclosure and customer action from the signup channel, such as a website form, POS checkout, QR code or keyword flow. Record its sender, purpose, source and time. When a customer replaces their number, exclude the old number from future sends to that customer and preserve its permission and withdrawal history. Verify consent for the replacement number and complete the recipient checks before texting it.
Store proof including timestamp, source URL or store location, and disclosure version. For imported records, keep the original consent time separate from when the record was loaded. Use the consent migration checks to reconcile older opt-ins with later withdrawals. When checkout or loyalty enrollment offers a separate Texting checkbox, rehearse leaving it unchecked with a new test profile. Confirm the completed checkout or enrollment keeps that profile out of the promotional SMS audience. If your signup uses a separate confirmation step, also rehearse stopping after the form is submitted. Check that the saved profile stays out of the promotional SMS audience until confirmation is recorded.
Confirm that standard keywords and clear plain-language withdrawal requests reach a responsible owner and the supported suppression process.
Register your messaging campaign accurately under 10DLC, describing your exact opt-in process.
Before launching order alerts or mass texting, confirm that the sending route permits your business and actual use case. Consent and registration do not override provider restrictions. Apply Blackleaf consent, age and intended-recipient birthday checks to either message type.
Checklist
Clear disclosure language visible before submission
Explicit acknowledgment action such as checkbox or keyword confirmation
For Blackleaf, explicit recipient consent and age confirmation before any text, including service and support
Intended-recipient birthday selection in the message flow; never disclose the saved birthday
Sending route permits the business and actual message use case
Timestamped record stored securely
Documented opt-out instructions in every marketing message
Affected sending paths checked after a withdrawal; unresolved work held
Alignment between declared campaign purpose and actual content
Segmentation rules that match consent scope
Comparison
Compare what each signup method actually records, including the disclosure, customer action, sender, purpose and time.
| Method | Consent evidence and fit |
|---|---|
| Website Form with Checkbox | Can document a clear customer action for ecommerce or loyalty signup. Preserve the disclosure, timestamp and source. |
| POS Digital Signup | Captures the signup in store. Preserve the disclosure, device or store context and timestamp; a purchase alone is not permission. |
| Keyword Text-In | Provides a customer action trail for signage or events. Document the keyword, disclosure and confirmation flow. |
| Printed QR signup | Scan the code on the sign at each store. Confirm it opens the intended form with the correct sender and disclosure, then verify that the form saves the customer’s choice and timestamp. |
| Imported Lists | Validate each number’s consent record and permitted scope before use. An import is not a new opt-in and does not restore withdrawn consent. |
Troubleshooting
| Symptom | Checks and next step |
|---|---|
| High STOP rate after campaign | Check for a consent-scope or frequency mismatch. Review the disclosure, audience and send frequency before continuing. |
| Carrier filtering increases | Pause sends and inspect the actual error, consent proof, list source and route policy. Review deliverability; do not assume consent alone resolves filtering. |
| Signup started, confirmation missing | If the signup flow requires a second confirmation, keep the record out of promotional texting until you can verify that step for the right sender and message purpose. A sent confirmation request does not complete the signup. See the consent audit cases. |
| Customer claims no consent | Stop messaging that recipient while reviewing the consent record and opt-out state. A staff assumption or past purchase is not proof. |
| Customer asks to opt back in | Keep suppression in place while you verify a new opt-in for the intended sender and message purpose through the supported signup process. Keep both the withdrawal record and the new opt-in evidence. Before resuming, check that the sending system reflects the verified choice and that the recipient qualifies for the intended audience. |
| Wrong number or possible reassignment | Hold affected texts while you check whether the number still belongs to the intended recipient. Apply any withdrawal through the supported suppression process. Before resuming, verify the current recipient’s explicit consent and age. |
| Campaign registration rejected | Check the actual rejection reason, business eligibility and submitted opt-in flow. Correct genuine errors; do not disguise an unsupported business or use case. |
| Transactional messages blocked | Inspect the route policy, rejection reason and registered use case. Service wording does not create an exception to a provider prohibition. Review the provider and route requirements, then confirm the recipient checks before resuming. |
FAQ
Question: Is verbal consent enough for cannabis SMS?
Answer: Do not treat an undocumented verbal agreement as a complete permission record. Keep the actual disclosure, customer action, sender, message purpose and timestamp, and review the requirements for the program. Blackleaf’s recipient and age checks still apply.
Question: Do I need a checkbox for website opt-in?
Answer: A clear acknowledgment action improves proof quality and reduces ambiguity about what the customer agreed to receive.
Question: What must disclosure include?
Answer: Who is sending messages, what types of messages, frequency expectations where possible, and clear opt-out instructions.
Question: Can I text past customers automatically?
Answer: A past purchase or stored POS phone number does not automatically authorize marketing. Verify the recipient’s documented permission and its scope. Blackleaf also requires age confirmation and intended-recipient birthday selection in the message flow; never disclose the saved birthday.
Question: Do Blackleaf recipient checks apply to service and support texts?
Answer: Yes. Explicit recipient consent and age confirmation are required before any Blackleaf text, including service and support. In the message flow, the intended recipient selects the birthday on file. Never disclose the saved birthday. These company requirements do not replace separate legal, carrier or sending-route review.
Question: Why does opt-in affect deliverability?
Answer: Permission is one review input, alongside sender, content, route and provider policy. Clear records help staff investigate complaints and failures; they do not guarantee delivery or prove the cause of filtering.
Question: How should I handle STOP replies?
Answer: Honor STOP and other clear withdrawal requests through the supported suppression process. Hold affected outreach while resolving scope, and check pending campaigns, automations, staff tools and connected systems using that permission. An old import or new purchase must not silently restore eligibility.
Question: Can I combine transactional and promotional messages?
Answer: Review the actual combined content, purpose, permission and provider rules. A transactional label does not remove promotional content or create an exception for a prohibited business or use case. Blackleaf recipient checks still apply.
Question: What happens if my opt-in language changes?
Answer: Keep the exact disclosure each subscriber saw and the date and action that recorded their choice. If the new disclosure adds a sender or changes the message purpose, check whether the original permission covers that use. Hold affected texts while permission is unclear. Use the consent evidence checklist to compare the original record with the proposed use.
Common Mistakes
Pre-checking consent boxes
Failing to document timestamp and source
Sending marketing texts under transactional consent
Missing clear withdrawal requests outside standard keywords
Scaling campaigns before verifying list hygiene
Metrics to monitor
Opt-in completion rate: For each signup source, divide the number of distinct people who completed every required step by the number who started. Count each person once. Set a time limit for completion and let it elapse for everyone in the starting group. Keep pending confirmations out of the completion count. Compare sources only when you can measure starts the same way. See the signup placement and measurement examples.
STOP Rate: Review withdrawal counts with the audience, period and denominator; a rate alone does not explain the cause.
Complaint Rate: Track recorded complaints for a defined audience and period, then investigate the source and permission evidence.
Delivery Rate: Separate provider acceptance, reported delivery, failure and unknown outcomes; these do not show customer action.
Revenue per Subscriber: Define the audience, period, costs and attribution method before comparing results; associated revenue is not proof of incremental lift.
Use segmentation and smart routing within the reviewed permission scope. Audience and route settings do not create permission or override applicable suppression and provider restrictions.
SMS opt-in glossary
| Term | Meaning |
|---|---|
| Opt-In | Customer permission to receive text messages. |
| Express Written Consent | Where required, the agreement and its evidence must meet the applicable written-consent standard. A generic platform flag is not the agreement. |
| Opt-Out | Customer request to stop receiving messages. |
| Suppression List | Database of numbers that must not receive messages. |
| Consent Scope | The category of messages a customer agreed to receive. |
| Double Opt-In | Two-step confirmation of subscription to verify intent. |
| Campaign Registration | Declaration of message purpose under A2P frameworks. |
| List Hygiene | Maintaining accurate, consent-based subscriber records. |
Sources and further reading
Twilio’s cannabis/CBD restriction is a provider-specific example: Twilio prohibits cannabis and CBD businesses from SMS and MMS in the United States and Canada, regardless of message content. Confirm the policy for the actual provider and route; an opt-in or 10DLC registration is not an exception.
CTIA Messaging Principles and Best Practices: Industry framework for consent, opt-out handling, and acceptable messaging behavior: https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf
Federal consent and withdrawal rules: review the current 47 CFR §64.1200 and applicable orders for the actual program.
The Campaign Registry overview for A2P 10DLC registration and consent declarations: https://www.campaignregistry.com/
FTC Telemarketing Sales Rule compliance overview: https://www.ftc.gov/business-guidance/resources/complying-telemarketing-sales-rule