Registered business name
Use the business entity associated with the applicable tax records and messaging account rather than an informal variation.
10DLC for cannabis is the registration framework used when dispensaries and other businesses send application-to-person SMS or MMS to United States recipients through local ten-digit long-code phone numbers.
Registration connects the verified business, its declared messaging use case, customer opt-in process, representative messages, and the phone numbers used to send that traffic. It does not replace customer consent, cannabis advertising review, age controls, opt-out enforcement, or other legal and operational requirements.
10DLC stands for ten-digit long code, the standard local phone-number format used for registered application-to-person messaging in the United States.
A2P 10DLC registration tells the messaging ecosystem which business is sending, what kinds of messages it plans to send, and how recipients enter and leave the program.
For a dispensary, the registered campaign may cover marketing promotions, loyalty messages, customer support, order notifications, account alerts, or an approved combination of use cases.
Registration is tied to local long-code traffic. Toll-free numbers, short codes, and other sender types use different verification or registration systems.
10DLC for dispensaries is the process of verifying the cannabis business, registering its messaging campaign, documenting the customer opt-in and opt-out flow, submitting representative messages, and associating approved local phone numbers with the declared use case.
Provide accurate legal, tax, address, website, contact, and business information.
Register the business that is responsible for the customer messaging program.
Describe the messages, customer relationship, opt-in method, frequency, links, and examples.
Connect the local phone numbers or messaging service used for the approved campaign.
Keep the real traffic, audiences, content, links, and customer controls aligned with registration.
The determining factors are the destination, sender type, and whether the traffic is application-to-person business messaging.
| Messaging situation | 10DLC registration | Explanation |
|---|---|---|
| Business SMS or MMS to U.S. recipients from a local ten-digit number | Generally required | The sender is using a U.S. long-code route for application-to-person business traffic. |
| Low-volume promotional messages from a local number | Generally required | Low volume does not by itself remove the registration requirement. It may affect the available registration type. |
| Order notifications from a local number | Generally required | Transactional traffic is still application-to-person business messaging when sent over a long-code route. |
| Customer-care messaging from a local number | Generally required | The campaign should accurately describe the customer-care or conversational use case. |
| Traffic sent from a verified toll-free number | Uses a different system | Toll-free messaging follows toll-free verification rather than A2P 10DLC registration. |
| Traffic sent from an approved short code | Uses a different system | Short codes use their own application, approval, and carrier-review process. |
| Messages sent only outside the United States | Depends on destination rules | U.S. A2P 10DLC applies to relevant U.S.-bound long-code traffic. Other countries maintain their own sender requirements. |
The registration requirement is not limited to recurring promotions or campaigns above a particular volume. A dispensary using local long-code numbers for U.S.-bound application-to-person traffic should verify that its brand, campaign, and sending numbers are fully registered.
The information should match the legal and operating entity responsible for the messaging program.
Use the business entity associated with the applicable tax records and messaging account rather than an informal variation.
Submit the identifier exactly as registered with the relevant government authority.
Address information should be accurate and consistent with the entity and supporting records.
The website should identify the brand or dispensary and contain relevant contact, privacy, and program information.
Use current contact information for a person authorized to represent the organization.
Registration options may vary according to tax-ID status, organization type, messaging provider, and expected traffic.
A multi-location operator may have one legal entity, several licensed entities, a management organization, separate franchisees, or distinct brands. The registration structure should accurately reflect who sends the messages and who controls the customer relationship.
A campaign is not one scheduled text blast. It is the registered messaging use case associated with the sender and phone numbers.
| Campaign field | What it should explain | Common registration problem |
|---|---|---|
| Use case | Whether the traffic is marketing, account notification, customer care, delivery, mixed, or another supported category. | The selected category does not match the live traffic. |
| Campaign description | Who sends, who receives, why the messages are sent, and what customer relationship exists. | The description is vague, generic, or avoids the actual cannabis use case. |
| Message flow | How customers provide permission, receive confirmation, obtain help, and withdraw consent. | The submitted flow does not match the real POS, website, keyword, or paper signup. |
| Sample messages | Representative sender identity, purpose, cannabis context, links, offers, frequency, and opt-out behavior. | The examples are materially cleaner or different from production messages. |
| Message frequency | How often customers may reasonably receive recurring messages. | The disclosure and real campaign cadence do not match. |
| HELP and STOP | How customers receive support and stop future covered messages. | The responses are missing, inaccurate, promotional, or disconnected from suppression. |
| Links | The branded domains and destinations commonly included in messages. | Messages later use unrelated shorteners, redirects, or unreviewed domains. |
Registration reviewers need to understand how a recipient knowingly joins the messaging program.
Numbers collected for identification, receipts, order pickup, loyalty lookup, account access, or customer service may not support recurring marketing. The registration should reflect a customer action and disclosure appropriate to the actual message program.
Samples should be transparent about the sender, purpose, customer experience, and types of messages that will be delivered.
| Use case | Representative structure | Registration consideration |
|---|---|---|
| Promotional campaign | [Dispensary]: [Approved campaign or offer]. View details and eligibility: [Branded Link]. Reply STOP to opt out. | The campaign registration should disclose marketing traffic, cannabis context, frequency, links, and opt-in method. |
| Order confirmation | [Dispensary]: We received order [Order Number]. We will text again when it is ready. Reply HELP for support. | Keep the content tied to the transaction unless the customer separately consented to marketing. |
| Order-ready notification | [Dispensary]: Order [Order Number] is ready for pickup at [Location]. View pickup details: [Link]. | The registered use case, sender, store, and message flow should support order notifications. |
| Loyalty message | [Dispensary]: You unlocked [Reward]. View your rewards account and eligibility: [Link]. Reply STOP to opt out. | Registration and customer consent should support recurring loyalty or marketing messages. |
| Customer care | [Dispensary]: Thanks for contacting us. A team member is reviewing your question and will reply here. | Do not use customer-care traffic as an undeclared route for unrelated promotions. |
Samples that remove the brand, products, promotional purpose, links, recurring nature, or other important context may fail to represent the live program accurately.
The registration moves through provider, registry, and potentially carrier review before the campaign becomes active.
The provider submits the business, brand, campaign, opt-in, examples, and associated details to the applicable registration systems.
Business details may be compared with authoritative records. Inaccurate names, tax information, addresses, or contacts can delay the process.
Reviewers evaluate the campaign description, use case, message flow, opt-in, examples, links, frequency, and customer controls.
The provider may request screenshots, working links, revised disclosures, better samples, clearer descriptions, or corrections to business information.
Once approved, the campaign can be associated with the applicable messaging service and local phone numbers.
The business may begin sending approved traffic after the provider confirms that the campaign and phone numbers are fully registered.
Review times can vary by provider, submission volume, business type, use case, completeness, and whether additional carrier review is required. Submit registration before the messaging program must go live.
Most problems come from inaccurate business data, incomplete customer disclosures, inaccessible signup flows, or registration that does not match the real traffic.
The entity name, EIN, address, website, or contact information is inaccurate or inconsistent.
The submission does not clearly explain the dispensary, customer relationship, message types, and use case.
The signup page is inaccessible, incomplete, behind a login, or missing the required program disclosures.
The submitted messages omit the cannabis context, links, recurring nature, sender, or promotional purpose.
Required links are broken, generic, incomplete, or unrelated to the messaging program.
Promotional traffic is described as customer care, or mixed traffic is registered as a narrow transactional campaign.
The signup or linked experience does not show the age or customer controls used by the dispensary.
The business may satisfy registration requirements while remaining prohibited by the provider’s acceptable-use policy.
The campaign may be approved while the local number remains outside the associated messaging service or sender pool.
Registration allows the messaging ecosystem to identify the sender and use case. Live traffic continues to be evaluated.
| Post-approval signal | How it can affect delivery |
|---|---|
| Use-case alignment | Traffic that differs from the registered campaign may be filtered, limited, or suspended. |
| Consent quality | Unexpected messages can increase opt-outs, negative replies, complaints, and filtering. |
| Sender reputation | Repeated failures, complaints, low-quality traffic, and policy problems can affect future campaigns. |
| Message volume | Sudden spikes, throughput limits, and abrupt traffic changes may produce throttling or blocking. |
| Links and domains | Inconsistent, redirected, shared, or low-trust links may contribute to filtering. |
| Message content | Misleading, repetitive, unsupported, or spam-like content can increase delivery risk. |
| Customer complaints | Spam reports and statements that customers did not subscribe are important negative signals. |
| Provider policy | A platform can suspend traffic that violates its rules even when the campaign remains registered. |
A campaign can become outdated as stores, brands, numbers, links, consent flows, vendors, and message programs change.
Confirm that the brand, campaign, messaging service, and sending numbers remain approved and correctly associated.
Verify that the live signup method still matches the submitted disclosure, links, confirmation, frequency, and sender identity.
Compare actual campaigns and automations with the registered use case and representative examples.
Track opt-outs, complaints, negative replies, delivery errors, filtering, and customers who do not recognize the sender.
Review the registration when ownership, legal entities, websites, brands, stores, numbers, providers, or campaign purposes change.
Use appropriate campaigns and routes when transactional, marketing, customer-care, or other traffic cannot be represented accurately together.
Blackleaf helps dispensaries organize business information, document customer opt-in, prepare campaign descriptions and representative messages, associate sending numbers, monitor registration status, enforce customer suppression, and keep production traffic aligned with the approved use case.
10DLC for cannabis is the registration process used when dispensaries and other businesses send application-to-person SMS or MMS to U.S. recipients using local ten-digit long-code phone numbers.
A dispensary sending application-to-person business messages to U.S. recipients through local ten-digit long-code numbers generally needs an approved brand, campaign, and registered sending numbers.
No. Low-volume, transactional, customer-care, loyalty, and promotional business traffic can still require registration when it is sent to U.S. recipients through long-code numbers.
Not necessarily. The correct structure depends on the legal entities, brands, licenses, customer relationships, messaging provider, stores, and who is responsible for sending the traffic.
The brand identifies the business responsible for messaging. The campaign describes the message use case, customer relationship, opt-in process, samples, frequency, and customer controls.
Common requirements include legal business information, tax identification, address, website, contacts, campaign use case, description, customer opt-in flow, representative messages, frequency, HELP and STOP handling, and sending numbers.
Registration does not convert every stored phone number into valid promotional consent. The dispensary should preserve evidence showing how each eligible customer agreed to receive the registered messages.
Review time varies by provider, submission volume, use case, registration type, completeness, and whether additional review is required. Businesses should register before the planned launch date.
Common causes include inaccurate business information, vague campaign descriptions, missing disclosures, inaccessible opt-in pages, weak message samples, broken policy links, unsupported use cases, and traffic that does not match the selected campaign type.
No. Approved messages can still be filtered because of complaints, consent quality, sender reputation, volume, links, content, campaign mismatch, or provider policy.
No. Registration does not replace TCPA analysis, customer consent, state cannabis advertising requirements, age controls, privacy, opt-out enforcement, or legal review.
That depends on the supported campaign type and provider rules. The registration must accurately represent all traffic. Separate campaigns may be appropriate when the purposes, consent, customer expectations, or operational requirements differ.
U.S.-bound messages may be blocked or rejected until the number is associated with an approved campaign and supported messaging route.
No. Toll-free messaging uses a separate verification system. Short codes also use a different application and approval process.
Use accurate business data, show the real customer opt-in, submit representative cannabis messages, associate every local sender, and keep production traffic aligned with the approved use case.