Start with the outcome you can actually verify.
Dispensary SMS deliverability concerns whether permitted messages reach their destinations and what the delivery evidence shows. A saved campaign, accepted request, delivery receipt, click, and purchase are different outcomes. Diagnose the missing step before changing the message or sending again.
No platform can promise every text will reach every customer. Provider policy, sender setup, audience eligibility, network conditions, recipient availability, content, and reporting limitations all matter. Registration, age controls, or a connected POS do not guarantee delivery.
This page explains the evidence and the first decisions. For an active issue, continue with the troubleshooting guide. For blocking specifically, see carrier filtering.
Check whether the route permits the business and message.
Confirm the actual provider, sender type, country, business category, and message purpose before treating an error as a copywriting problem. Legal operation, customer permission, sender registration, and provider policy are separate checks.
For a concrete example, Twilio prohibits cannabis/CBD businesses from SMS and MMS in the United States and Canada regardless of message content. This is a Twilio-specific restriction, not a statement that every provider has identical policy or that another route is automatically eligible.
Removing a cannabis term, using an age-gated link, changing SMS to MMS, or labeling a text “transactional” does not override a prohibited business or use case. Confirm the proposed route with your provider and review messaging requirements. Registration or verification requirements depend on the sender and route; do not assume all business texting uses 10DLC.
Read delivery events separately from customer actions.
Scroll the table horizontally on smaller screens. Keyboard users can focus its region and use the arrow keys.
| Event or observation | What to confirm | What it does not establish |
|---|---|---|
| Prepared or scheduled | A draft or future send exists. | No message has necessarily been submitted. |
| Accepted or queued | A provider accepted the request or is waiting to dispatch it. | It has not necessarily reached the network or customer. |
| Sent | Check the provider’s definition; it can mean upstream carrier acceptance. | Not a delivery receipt, read receipt, or purchase. |
| Delivered | A positive delivery receipt was reported; its coverage depends on the route. | Not proof the person read or acted on the text. |
| Failed or undelivered | Check the actual code, source, timestamp, and finality. | Not automatically content filtering. |
| Filtered or blocked | A provider or carrier restriction was reported. | The visible wording alone may not explain the cause. |
| Pending or unknown | No conclusive final outcome is available yet. | Do not silently count it as delivered or failed. |
| Click, reply, or opt-out | A separate link event, inbound message, or withdrawal was recorded. | A click is not necessarily a unique human shopper; an opt-out is a suppression decision. |
| Matched purchase | A transaction matched the reporting rule and window. | Not proof the text caused an additional sale. |
Status names vary by provider. For example, Twilio’s status definitions distinguish upstream acceptance from a positive delivery receipt. Use the actual definitions and timestamps for your route. Ordinary SMS/MMS does not supply a universal read receipt or a dependable “open rate.”
Follow the first missing piece of evidence.
A diagnostic decision path, not an automatic diagnosis. Start at the first question that matches the campaign.
- Was anything submitted?
If there is no message record or request ID, inspect the campaign state, schedule/time zone, eligible audience, approval, and source trigger. A draft or skipped recipient is not a carrier failure.
- Is there a failure or restriction?
Read the exact code and provider explanation. Separate unsupported use cases, account or sender configuration, recipient problems, rate limits, and explicit filtering. Hold affected work until the cause and permitted remedy are clear.
- Is the outcome still pending?
Check queue age, timestamps, provider reporting delay, and any incident. Reconcile the existing message record before retrying; a missing receipt can otherwise become a duplicate text.
- Is delivery reported, but response is weak?
Check link availability and tracking, audience relevance, offer accuracy, timing, store readiness, and measurement. Weak clicks or sales do not by themselves prove a delivery failure.
As a provider-specific example, Twilio error 30007 identifies filtering by Twilio or a carrier. It is not a universal code for every Blackleaf route. A concentration of failures on one carrier is a clue to investigate, not proof of one cause.
Review the program before another send.
- Eligibility: retain the actual permission evidence and current suppression for the proposed message. A purchase or loyalty profile alone does not establish marketing permission.
- Source freshness: verify customer/store matching, order state, and purchase or stock inputs. Hold messages that depend on stale or missing facts.
- Sender and route: confirm active account, sender, registration or verification where required, permitted use case, capacity, and geography.
- Content and destination: identify the sender clearly, verify the offer and terms, test the link, and keep the message aligned with its purpose. Do not disguise the business or rotate numbers to evade restrictions.
- Audience and timing: remove excluded and recently contacted recipients, review local timing, and confirm expected volume. Use the route’s supported sending limits rather than inventing a universal safe volume.
- Controlled test: when the route and use case are permitted, use an approved test audience and compare message IDs, receipts, and the linked experience. A successful test does not guarantee a full campaign’s outcome.
- Replies and failures: name the person who monitors results and customer questions. Apply opt-outs across sending workflows and escalate unresolved restrictions.
Use message drafts as starting points for review, not preapproved wording. Read order alerts for event freshness and integration checks for source dependencies.
Keep the denominator and reporting window visible.
Define whether you count recipients, message attempts, or billable SMS segments. Those units are not interchangeable. Separate SMS and MMS, stores, campaigns, sender identities, and available carrier/error breakdowns when comparing outcomes.
At an agreed cutoff, a campaign has 1,000 message attempts: 880 reported delivered, 50 failed/undelivered, and 70 pending/unknown. Report all three categories.
Reported delivered / attempted: 880 ÷ 1,000 = 88%.
Delivered / known final outcomes: 880 ÷ (880 + 50) ≈ 94.6%.
The second percentage excludes the 70 unresolved attempts. Calling it the campaign’s overall delivery rate without that disclosure would hide missing evidence. Reconcile later receipts without counting one message twice.
For clicks, identify unique versus total events and any bot or link-scanner exclusions the tool supports. For opt-outs, state the cohort and denominator. For purchases, state the identity match, attribution window, returns, and overlapping campaign rules. Use a suitable comparison before claiming incremental sales.
Include platform, service, usage, registration, integration, and offer costs where relevant. See the benchmarking framework, SMS ROI guide, and current pricing. No universal delivery percentage predicts your store’s result.
Use the workspace to prepare, review, and follow through.
Blackleaf brings SMS/MMS campaigns, messaging workflows, and customer replies together. Review the status and error evidence available for your account and ask the team to clarify how the route reports pending, failed, and delivered outcomes.
For an issue, collect the campaign and message IDs, timestamps/time zone, sender, reported status/code, affected volume, recent changes, and a few representative examples. Share private recipient details only through the authorized support channel when needed. Do not publish customer numbers in a public troubleshooting post.
Texting can complement supported existing POS systems; adopting Blackleaf POS is not required. POS data can supply context, but a connector is not evidence of delivery or permission. AI drafting can help prepare content for review; it cannot guarantee policy eligibility, delivery, or customer intent.
Deliverability questions, answered.
Does Blackleaf guarantee every text will be delivered?
No. Provider and carrier policy, sender setup, audience eligibility, recipient conditions, content, and network or reporting limitations affect outcomes. Review the actual route and delivery evidence rather than expecting a full-list guarantee.
Does sent mean delivered?
Not necessarily. A sent status can mean upstream carrier acceptance. Delivered usually reflects a positive receipt under the provider’s definitions. Confirm the actual route’s status meanings.
Does delivered mean the customer read the SMS?
No. A delivery receipt does not prove reading, intent, a click, or a purchase. Ordinary SMS/MMS has no universal read receipt or dependable open-rate measurement.
Is every undelivered text blocked by a content filter?
No. Recipient availability, invalid destinations, account or sender issues, limits, and technical failures can also produce unsuccessful outcomes. Start with the actual code and its provider-specific explanation.
Does registration or an age gate guarantee cannabis SMS eligibility?
No. Sender registration, age controls, permission, provider policy, and permitted content are separate checks. For example, Twilio forbids cannabis/CBD business SMS/MMS in the United States and Canada regardless of wording.
Will MMS or different spelling fix a blocked campaign?
Not necessarily. Changing format or wording does not resolve a prohibited business or route, missing permission, account restriction, or sender problem. Identify the cause and permitted remedy before another send.
What should we do with pending or unknown statuses?
Keep them separate, record the reporting cutoff, and reconcile the existing message IDs and later receipts. Do not automatically count them as delivered or failed, or blindly retry them as new messages.
What is a good dispensary SMS delivery rate?
There is no universal target established here. Compare the same unit, denominator, time window, channel, and route, including unknown outcomes. A small test or vendor headline does not predict a full campaign.
What if delivery is high but sales are low?
Review tracking, audience relevance, offer and stock accuracy, timing, store operations, and the attribution method. Weak sales alone do not establish a delivery problem, and matched sales do not prove incremental lift.
What information helps diagnose a problem?
Collect campaign/message IDs, timestamps and time zone, sender, status/error codes, affected volume, recent changes, and representative examples. Use authorized support channels for private recipient data.
Do we need to replace our POS to improve texting?
No Blackleaf POS switch is required for supported existing-system texting. Confirm the source data, message workflow, route, permission, and reporting for the job you want to improve.
Review the next campaign with the evidence in hand.
Bring your current systems, message purpose, audience source, and any delivery records. Blackleaf can help review the proposed workflow and the questions to resolve before activation.