The same text should not go to every customer
A modern texting strategy decides whether this customer should be contacted now, which behavior made the message relevant, what job the text must perform, which campaign mode should deliver it, and what evidence will determine the next decision.
The objective is not to eliminate large campaigns. It is to stop treating the entire opted-in audience as one customer with one need, one cadence, and one response.
Definition
Retail text messaging strategy is the operating system that decides which eligible customer should receive which type of text, through which campaign mode, at which behavioral or calendar moment, and at what frequency. It connects customer state, message purpose, timing, budget, suppression, deliverability, and outcome measurement.
The strategy is broader than campaigns. It includes one-time promotional campaigns, automated campaigns, order and account notifications, inbound messages, two-way conversations, carrier deliverability, tracked clicks, age-gate views, customer purchase behavior when available, and the operational work required to improve all of them.
Quick answer: begin with eligibility and customer behavior. Map that customer to a lifecycle group. Choose an automated, one-time, or scheduled campaign. Select the message purpose. Then choose the send time, apply suppression, and measure the result. The strategy level sets the maximum operating pace; it does not replace customer-level relevance.
Retail Text Blasting Died in 2024
2024 was the end of the broadcast-first era. It was not the year retailers stopped sending large campaigns. It was the point when a list-wide blast could no longer be treated as a complete messaging strategy.
The old model was simple: collect phone numbers, write one promotion, send it to everyone, and judge the result by total clicks or same-day revenue. That model ignored customer state. A first-time buyer, an unresolved support customer, a VIP, a 90-day lapsed shopper, and someone who purchased yesterday could all receive the same message.
The market moved in the opposite direction. Twilio’s 2024 customer-engagement research found that only 16% of brands strongly agreed they had the data needed to understand customers, even as consumers increasingly expected individualized experiences. In 2025, Attentive reported that 81% of surveyed consumers ignore irrelevant marketing messages. CTIA’s messaging principles continue to center the channel on wanted messages and consumer trust.
Audience first
Start with the largest available list, then search for one message broad enough to send to everyone.
Behavior first
Start with what changed for a customer, then determine whether any message is relevant now.
Every send needs a reason
The reason must be explainable as an event, lifecycle state, preference, local moment, service need, or measured opportunity.
Mass campaigns are not dead. A 4/20 announcement, store closure, major product launch, or Green Wednesday event may belong in a large one-time campaign. What died is the assumption that every campaign should begin with the whole list.
The Five Decisions in Every Send
A complete messaging decision has five parts. Skipping any one of them produces an incomplete plan.
Sets the program’s overall pace and required mix of service, lifecycle, educational, and promotional messaging.
Uses consent, purchase recency, order state, engagement, value, and conversation behavior to decide what is relevant for this person.
Chooses an event-triggered automation, a one-time campaign, or a schedule-based recurring campaign.
Defines the job of the text, such as order receipt, first-purchase guidance, rewards update, replenishment, product launch, win-back, or support reply.
Sends immediately when the customer creates the moment, or uses the roadmap’s planned day when the message is editorial or promotional.
The decision order matters. Eligibility and event-driven service messages come before marketing cadence. A pickup-ready update should not wait for Friday. A promotional product launch should not interrupt an unresolved support conversation. A completed purchase should immediately remove the customer from abandoned-cart and win-back programs.
Why This Matters for Dispensaries
Dispensaries usually do not have a single messaging problem. They have a coordination problem. A team may send a strong flash sale while forgetting win-back customers, allow an abandoned-cart automation to overlap with a blast, or increase frequency while carrier delivery is weakening. Those decisions are connected, even when different tools and teams manage them.
A useful strategy prevents four common failures:
- Under-messaging: eligible customers do not hear from the store often enough to build repeat behavior.
- Over-messaging: overlapping campaigns and automations create fatigue, opt-outs, complaints, or carrier filtering.
- Unbalanced messaging: promotional blasts crowd out order updates, educational messages, support, and lifecycle communication.
- Unmeasured messaging: the team sees send counts without knowing which customers, carriers, programs, and outcomes need attention.
Frequency only works when permission, expectation, delivery, and relevance remain healthy. Review opt-in and consent for dispensaries before increasing promotional cadence, and use the dispensary texting frequency guide when interpreting signs of fatigue.
The Four Messaging Strategies
The strategy is a ceiling for planned marketing cadence, not a quota for every contact. Growth is the recommended operating target for a mature retail program because it supports three useful weekly opportunities without making daily promotion the default. High Frequency is a deliberate contrast tier for unusually mature programs, not an automatic upgrade.
Essential
LightestHoliday, milestone, and occasional high-confidence sends.
Order and account messages, welcome, birthday, anniversary, rewards expiry, store-hour alerts, and a small number of major retail moments.
For new programs establishing consent and delivery discipline. Watch for a stale list and too few opportunities to learn.
Consistent
WeeklyOne planned active-customer touch each week.
Essential programs plus first-purchase guidance, replenishment, review requests, rewards, back-in-stock, and measured re-engagement.
For teams building a predictable habit. Do not turn every weekly slot into the same discount.
Growth
RecommendedUp to three planned active-customer touches each week, commonly Monday, Wednesday, and Friday.
Complete service and lifecycle coverage, education, new products, flash sales, VIP, win-back, dormant reactivation, holidays, and local moments.
For mature programs with cross-program frequency control. Watch collisions between campaigns and automations.
High Frequency
DailyAs often as daily, but only for contacts whose observed behavior supports it.
Growth coverage plus rapid inventory, event, loyalty, and conversational programs with customer-level send-time optimization.
For exceptional programs with proven demand, strong content operations, strict caps, holdouts, suppression, and carrier monitoring.
Frequency is earned one customer at a time. A customer may belong to a Growth program while receiving only one message this week because they purchased yesterday, have an unresolved conversation, recently ignored several sends, or have no relevant reason to hear from the retailer.
How Active Customers Are Defined
The active-customer setting determines the purchase-recency window used to size the main reachable audience. Available choices are all eligible customers or customers who purchased within the last 3, 6, 12, 18, or 24 months. Six months is the default because it balances recent purchase intent with a useful audience size.
Eligible customers must have a valid phone number and must not be opted out. If purchase history is unavailable, the planning system may temporarily use all otherwise eligible contacts, but it must label that fallback. Missing data should never masquerade as proof that every contact is active.
These lifecycle boundaries are configurable in Advanced settings. They are not claims about every dispensary’s natural purchase cycle. Use your own replenishment timing, product mix, and purchase data to refine them. For event data and purchase-history synchronization, review dispensary SMS integrations.
The Eleven Moments That Create a Reason to Text
Retailers do not need an endless list of campaigns. They need a complete taxonomy of moments. Every useful text belongs to one of these buckets, and every bucket has a different clock.
| Moment bucket | What creates it | Typical message jobs | Timing rule |
|---|---|---|---|
| 1. Permission moment | A person subscribes, changes preferences, or confirms consent | Opt-in confirmation, expectation setting, preference capture, welcome | Immediately after the verified action |
| 2. Order moment | An order is placed or its fulfillment state changes | Receipt, payment issue, substitution, pickup ready, dispatch, delay, cancellation | Immediately after the trusted status event |
| 3. Conversation moment | A customer replies, asks a question, or needs staff intervention | Acknowledgment, answer, handoff, resolution, reopened case | As soon as service coverage allows |
| 4. Intent moment | A cart is abandoned, a tracked experience is viewed, or a waitlist item becomes available | Checkout help, clarification, back-in-stock, waitlist release | From 15 minutes to 3 days, based on urgency and customer expectation |
| 5. Purchase moment | A first or repeat transaction completes | Thank-you, first-purchase guidance, rewards earned, care or product education | Receipt immediately; useful guidance after fulfillment |
| 6. Experience moment | The customer has had enough time to evaluate the product or service | Feedback, honest review, support check, referral | Usually 1 to 7 days after fulfillment, depending on the experience |
| 7. Product-cycle moment | The expected use or replenishment window approaches | Replenishment, relevant restock, category education | Learned from product category and individual purchase intervals |
| 8. Lifecycle moment | Purchase recency crosses an active, lapsing, win-back, or dormant boundary | Lapsing-soon reminder, win-back, reintroduction, preference reset | At the boundary, then at a controlled weekly or monthly pace |
| 9. Personal-calendar moment | A known birthday, signup anniversary, first-purchase anniversary, or loyalty milestone arrives | Recognition, birthday benefit, anniversary note, tier or purchase-count milestone | Lead-up when planning is useful; day-of when recognition is the value |
| 10. Retail-calendar moment | A holiday, store anniversary, local event, product release, or cultural occasion matters | Planning guide, hours, event details, curated offer, day-of reminder | Use a lead-up, event-day, and post-event sequence rather than repeated blasts |
| 11. No-send moment | The person is ineligible, capped, recently converted, already contacted, unresolved, or has no relevant reason | None | Suppress, wait, or reevaluate after the blocking state changes |
The clock is part of the message. “Pickup ready” loses value when delayed. A replenishment reminder becomes noise when sent too early. A birthday message feels automated when it arrives after the birthday. Timing is not a delivery setting applied after strategy; it is one of the reasons the text deserves to exist.
The Psychology of a Useful Retail Text
A text enters a private, high-attention channel. The customer evaluates it in seconds: Why me? Why now? What does this help me do? Strong messaging reduces that cognitive work instead of manufacturing pressure.
Recognition without surveillance
Use reliable behavior such as purchase recency, stated preferences, order status, and known product affinity. Do not reveal hidden inference or overstate what the retailer knows.
Respond while the context is alive
An event-triggered message works because the customer remembers the action. As the event gets older, the message needs more explanation and usually less urgency.
One text, one primary job
A receipt, review request, product launch, and win-back pitch should not compete inside one message. One clear purpose lowers cognitive load.
Let the customer retain control
Honest terms, recognizable identity, preference controls, and clear opt-out language protect trust. False scarcity and disguised conditions spend that trust.
Deliver value before asking
Fulfill the order, answer the question, or provide useful guidance before asking for a review, referral, or another purchase.
Vary the value, not just the wording
Rotating subject lines cannot rescue repetitive offers. Sustainable cadence alternates service, education, recognition, discovery, conversation, and promotion.
This is why personalization is not a token containing a first name. It is the choice to send a different message, at a different time, or no message at all because the customer is in a different state.
The Customer Behavior Decision Matrix
This matrix answers the operational question at the center of the strategy: given what this customer just did, or has not done, what should happen next? Use the first matching high-priority row. Then check lower-priority rows only if the customer remains eligible and the messages do not collide.
| Observed customer behavior | Contact type | Campaign type | Message type | When to send | Exit or suppression rule |
|---|---|---|---|---|---|
| Opted out, invalid number, missing required consent, or otherwise ineligible | Suppressed | None | None | Do not send | Remain suppressed until a valid eligibility state is lawfully established |
| Placed an order or the order status changed | Current customer with an active order | Event-triggered automation | Order received, payment, pickup ready, shipping, delivery, delay, or cancellation update | Immediately after the verified status event | Transactional purpose only; do not add an unrelated promotion without the appropriate consent |
| Sent an inbound message or is waiting on a reply | Active conversation | Two-way or support workflow | Direct answer, clarification, handoff, or resolution | As soon as staff coverage allows | Pause nonessential promotion while the issue is unresolved |
| Subscribed but has not purchased | New subscriber | Welcome automation | Welcome, preference capture, shopping guidance, or first-purchase information | Immediately, with one useful follow-up in 1 to 2 days if still eligible | Exit after first purchase, opt-out, or completion of the short welcome sequence |
| Completed a first purchase | First-time buyer | Post-purchase automation | Receipt, first-purchase heads-up, rewards enrollment, care guidance, or what to expect next | Receipt immediately; guidance after fulfillment or within 1 day | Do not send abandoned-cart or acquisition messages after conversion |
| Completed a purchase and the normal product-use window is approaching | Replenishment due | Lifecycle automation | Replenishment reminder, relevant restock, or product education | At the modeled replenishment interval, preferably on the next planned weekday | Exit after purchase; suppress when inventory or product fit is uncertain |
| Purchased recently and remains inside the active window | Recent active customer | Schedule-based campaign plus relevant automations | Education, rewards update, new product, restock, local event, VIP access, or bounded promotion | Use the selected strategy cadence; Growth begins with Monday, Wednesday, and Friday | Cap frequency across every campaign and automation, not per program |
| Has high value, repeated purchases, or a known affinity | VIP or high-value active customer | One-time campaign or targeted automation | Early access, relevant restock, service-led recognition, or exclusive event | Before broad release, often Wednesday or a verified inventory moment | Do not rely only on discounts; protect relevance and margin |
| Opened a tracked message or passed the age gate without purchasing | Engaged non-purchaser | Behavior-triggered follow-up or next planned campaign | Question resolution, product clarification, inventory reminder, or one clear next step | Within 1 to 3 days, unless a support or order event should take priority | Do not treat a view as proof of purchase intent; stop after purchase or opt-out |
| Started a cart but did not complete a purchase | Abandoned-cart customer | Abandoned-cart automation | Cart reminder, inventory warning when true, or checkout assistance | Shortly after abandonment, then at most one useful follow-up | Exit immediately after purchase; suppress when the cart is stale or inventory is unavailable |
| No purchase for 60 to 180 days under the default Growth settings | Re-engagement customer | Win-back automation | Relevant reason to return, preference check, new category, or bounded win-back offer | Up to weekly while eligible, using a planned day such as Wednesday | Exit after purchase, reply, opt-out, or the configured re-engagement window |
| No purchase for more than 180 days under the default Growth settings | Dormant customer | Long-term reactivation automation | Brand reintroduction, preference reset, major store update, or high-confidence value proposition | Monthly, preferably on the 1st, 2nd, 15th, or 16th | Use low frequency; stop if response, consent, or deliverability signals are weak |
| Recently purchased and enough time has passed to ask for feedback | Fulfilled customer | Receipt and review automation | Honest feedback or Google review request | After the customer has received the product and had time to evaluate the experience | No review gating; do not ask before fulfillment or during an unresolved issue |
Priority rule: eligibility and suppression come first, then order and support events, then lifecycle automations, then scheduled campaigns. A lower-priority marketing send should never displace a necessary service message or ignore a completed conversion.
Message Types and Their Jobs
The message type should describe the job the text must accomplish. It is not merely the campaign name.
| Message type | Customer question it answers | Best campaign mode | Primary measure |
|---|---|---|---|
| Order receipt and status | Did you receive my order, and what happens next? | Event-triggered automation | Delivery, fewer support requests, successful fulfillment |
| First-purchase guidance | How does pickup, delivery, rewards, or the next visit work? | Post-purchase automation | Second purchase, rewards enrollment, fewer questions |
| Welcome | Why should I stay subscribed, and what can I expect? | Welcome automation | First purchase, preference capture, low opt-out rate |
| Rewards update | What have I earned, and what useful action can I take? | Scheduled or event-triggered automation | Reward use, return visit, delivered reach |
| Replenishment | Might I be running low on something I already use? | Lifecycle automation | Repeat purchase near the expected use cycle |
| New product or restock | Is something relevant to my preferences now available? | Targeted one-time campaign | Qualified visits, clicks, age-gate views, purchases |
| Education | Can you help me make a more confident shopping decision? | Schedule-based campaign | Replies, views, category exploration, later purchase |
| Flash sale | What time-bounded value is available right now? | One-time campaign | Delivered reach, visits, purchases, opt-outs |
| Win-back | What has changed, or why is a return visit relevant to me? | Lifecycle automation | Reactivated purchasers and opt-out rate |
| Review and feedback | How can I share an honest experience? | Post-purchase automation | Completed feedback and honest reviews |
| Support reply | Did a person understand and resolve my question? | Two-way conversation | Response time and resolution |
Best Days for Each Message Type
There are two kinds of send timing. Event time is created by the customer or order and should usually be handled immediately. Planning time is selected by the team for editorial, lifecycle, and promotional messages. The current Growth roadmap begins with Monday, Wednesday, and Friday, adds relevant holidays, and recognizes activation dates on the 1st, 2nd, 15th, and 16th.
| Day or trigger | Recommended message jobs | Best-fit contact types | Reason |
|---|---|---|---|
| Immediately after an event | Order receipt, status change, pickup ready, account security, opt-in confirmation, support reply | Customers who created the event | Accuracy and speed matter more than the promotional calendar |
| Monday | Weekly orientation, rewards update, education, replenishment, practical planning | Recent active and replenishment-due customers | Starts the week with utility rather than urgency |
| Wednesday | Product discovery, education, VIP preview, win-back, local event preview | Active, VIP, and re-engagement customers | Creates a useful midweek touch and time to act before the weekend |
| Friday | Weekend plan, flash sale, pickup reminder, local event, time-bounded promotion | Eligible recent customers and high-intent groups | Matches near-term shopping intent when the offer and inventory are real |
| 1st or 2nd | Monthly customer activation, rewards status, new-month education, major release | Active customers and selected dormant cohorts | Provides a clear monthly planning anchor |
| 15th or 16th | Mid-month activation, replenishment, VIP event, second monthly dormant test | Active, replenishment-due, VIP, or carefully selected dormant customers | Provides a second calendar anchor without inventing a trigger |
| Relevant holiday or local event | Holiday hours, event details, curated education, or a clear event offer | Local eligible customers | The calendar itself supplies context, but only when the message is genuinely relevant |
| 1 to 3 days after engagement | Product clarification, next-step reminder, or response to a known question | Age-gate viewers, clickers, and engaged non-purchasers | Uses a recent intent signal without pretending the action was a conversion |
| After fulfillment and product experience | Honest review, feedback, education, or care guidance | Fulfilled first-time and returning customers | The customer must receive value before the request |
These are roadmap defaults, not universal claims that a weekday always performs best. The system should learn from delivery, opt-outs, replies, age-gate views, clicks, and purchases by contact type and message type. Keep the winning day only when the observed result supports it.
Three Campaign Modes
Every retail campaign belongs to one of three operating modes:
One-time campaigns
Calendar-led or event-led sends such as flash sales, product launches, VIP access, holidays, educational messages, referral requests, and local store events.
Automated campaigns
Messages sent from a trigger or lifecycle condition, including welcome, order updates, abandoned cart, replenishment, receipt and review, re-engagement, and dormant-customer programs.
Schedule-based campaigns
Recurring editorial slots such as Monday education, Wednesday discovery, Friday weekend planning, monthly rewards, and controlled dormant-audience tests.
Automated does not mean unattended. Every automated campaign needs an entry condition, audience rule, consent basis, suppression rule, stop condition, goal, and owner. Use the dispensary SMS automation guide to build flows that exit after a purchase, reply, pickup, or opt-out.
The Complete Retail SMS Automation Catalog
A mature messaging program automates moments, not noise. The catalog below covers the recurring jobs most retailers and dispensaries should evaluate. A business does not need every program on day one, but it should make an explicit decision about each one.
Permission, onboarding, and identity
| Automation | Trigger | Message job | Exit or suppression |
|---|---|---|---|
| Opt-in confirmation | Verified subscription | Confirm enrollment, identity, expected content, and how to stop | Send once; never treat an unverified number as subscribed |
| Welcome and orientation | New eligible subscriber | Explain value, store basics, and the next useful action | Exit after first purchase or short sequence completion |
| Preference capture | After welcome or preference reset | Ask what categories, locations, and message types are useful | Do not repeatedly ask after a preference is known |
| First-purchase path | Subscriber has not purchased | Remove uncertainty about shopping, pickup, delivery, or rewards | Exit immediately after first purchase |
| Age-gate completion | Verified passage through an age-gated experience | Continue the specific shopping journey when permission supports it | Do not infer a purchase; exit on conversion or stale intent |
Order, account, and service
| Automation | Trigger | Message job | Exit or suppression |
|---|---|---|---|
| Order received | Order created | Confirm receipt and the expected next step | Superseded by the next verified order state |
| Payment problem | Payment failure or action required | Explain the issue and safe correction path | Exit after payment or cancellation |
| Order accepted or processing | Merchant accepts order | Set an accurate fulfillment expectation | Exit when ready, dispatched, or canceled |
| Substitution or out-of-stock | Selected item cannot be fulfilled | Request a decision or explain the approved substitute | Pause promotion until the order issue is resolved |
| Pickup reminder | Pickup window approaches | Prevent a missed pickup and clarify requirements | Exit after pickup, cancellation, or expiry |
| Pickup ready | Order is verified ready | Tell the customer exactly where and how to collect it | Exit after pickup |
| Delivery dispatched and ETA | Delivery begins or ETA changes | Reduce uncertainty and missed handoffs | Exit after delivery |
| Delay, cancellation, or closure | Service disruption | State what changed, what the customer should do, and where to get help | Follow with resolution only when verified |
| Digital receipt | Transaction completed | Document purchase and provide support context | One per transaction |
| Account and security alert | Verified account event | Protect access or confirm a consequential change | Transactional purpose only |
Intent, recovery, and product availability
| Automation | Trigger | Message job | Exit or suppression |
|---|---|---|---|
| Abandoned cart | Checkout starts but purchase does not complete | Restore the cart, answer a likely obstacle, or offer help | Exit on purchase; stop when inventory or intent is stale |
| Incomplete order help | Form or validation failure | Explain the exact correction without contradictory errors | Exit when resolved or customer declines help |
| Tracked-view follow-up | Known message experience viewed without purchase | Clarify the product, offer, store, or next step | Limit to one useful follow-up; exit on purchase |
| Back in stock | Requested or relevant item returns | Notify the smallest high-confidence audience | Stop when inventory becomes unavailable |
| Waitlist release | Reserved availability opens | Give the customer a fair, time-bounded opportunity | Exit after claim, expiry, or inventory depletion |
| Price or offer watch | Customer explicitly requests an alert | Notify when the stated condition is true | Exit after alert, preference removal, or expiry |
Post-purchase, loyalty, and personal milestones
| Automation | Trigger | Message job | Exit or suppression |
|---|---|---|---|
| First-purchase guidance | First fulfilled order | Explain what happens next, rewards, care, or useful product context | Send once; suppress during unresolved service issues |
| Product education or care | Relevant product purchased | Help the customer use, store, or understand the purchase | Only when the content matches the product and jurisdiction |
| Experience check | Enough time has passed after fulfillment | Ask whether help is needed | Route problems to support before review requests |
| Honest review request | Completed, issue-free experience | Invite an honest review without filtering sentiment | No review gating; send once per defined interval |
| Referral invitation | Qualified positive experience or loyalty threshold | Explain a permitted referral program clearly | Suppress when rules, consent, or customer state do not support it |
| Rewards earned or balance | Points change or planned balance update | Make earned value visible and explain a useful next action | Do not invent urgency |
| Tier upgrade | Loyalty tier changes | Recognize the milestone and explain benefits | One per tier event |
| Points expiry | Real expiry approaches | Prevent surprise loss with clear timing and terms | Exit after use or expiry; never use false scarcity |
| Birthday | Known birthday and valid permission | Recognize the customer with a relevant benefit or message | Use an annual cap and respect local promotional rules |
| Signup anniversary | Subscription anniversary | Recognize the relationship or summarize useful value | Annual; skip when recent experience is poor |
| First-purchase anniversary | Anniversary of first transaction | Recognize loyalty with relevant history or benefit | Annual; do not expose sensitive purchase detail |
| Purchase-count milestone | Meaningful verified threshold | Thank and recognize the customer | Use sparse milestones, not every transaction |
| VIP early access | Qualified loyalty or affinity rule | Offer access before a broad release | Inventory and eligibility must be real |
Lifecycle and conversation
| Automation | Trigger | Message job | Exit or suppression |
|---|---|---|---|
| Replenishment | Individual or category purchase interval approaches | Help the customer restock at the right time | Exit on purchase; suppress when the estimate is weak |
| Lapsing-soon | Customer nears the normal repurchase boundary | Provide a relevant reason to return before the relationship cools | Exit on purchase or active engagement |
| Win-back | Default: 60 to 180 days without purchase | Explain what is newly relevant, not merely “we miss you” | Weekly at most; exit on purchase, reply, or window end |
| Dormant reintroduction | Default: more than 180 days without purchase | Reintroduce the retailer, preferences, or meaningful change | Monthly at most; sunset weak cohorts |
| Preference reset | Long inactivity or repeated low engagement | Ask what, if anything, remains useful | Suppress marketing when no preference or signal remains |
| Inbound acknowledgment | Customer message received | Confirm receipt and set a response expectation | Superseded by staff response |
| Staff handoff | Automation cannot responsibly resolve request | Move the conversation to a person with context | Pause nonessential marketing until resolution |
| Resolution and follow-up | Case resolved | Confirm outcome and provide a path back if needed | Do not request promotion or review until value is restored |
The Dispensary Messaging Calendar
A holiday is not a single send date. It is a planning window with different customer jobs before, during, and after the event. Headset’s 4/20 reporting and its analysis of Green Wednesday show that major cannabis occasions produce distinct demand patterns. The practical lesson is to prepare audiences, inventory, operations, and content before the peak instead of treating the day as permission for a list-wide blast.
| Moment | Planning window | Best message jobs | Audience and operating note |
|---|---|---|---|
| New Year’s Eve and New Year’s Day | 3 to 7 days before; hours reminder day-of; service follow-up after | Store hours, celebration planning, pickup cutoff, responsible-use education, loyalty reset | Local eligible customers. Separate operational information from promotion. |
| Valentine’s Day | 5 to 10 days before; one final planning reminder | Gift planning where permitted, shared-experience education, curated products | Use stated interests and local rules. Do not infer relationship status. |
| St. Patrick’s Day | 3 to 7 days before | Local event planning, store hours, relevant category story | Use only when locally meaningful. Avoid novelty-for-novelty’s-sake. |
| 4/20 early planning | 3 to 4 weeks before | Preference capture, VIP invitation, educational guide, calendar announcement | Past event shoppers, VIPs, active customers, and new subscribers receive different preparation. |
| 4/20 lead-up | 7 to 10 days before | Event details, inventory preview, product education, ordering plan, offer terms | Segment by affinity and shopping mode. Reserve broad reach for the clearest announcement. |
| 4/20 final preparation | 2 to 3 days before | Hours, pickup or delivery cutoff, parking, menu availability, event logistics | Utility should reduce customer uncertainty and staff load. |
| 4/20 day-of | One controlled day-of window | Open-now details, verified availability, live service update, real last-call deadline | Suppress customers who already purchased when another message adds no value. |
| 4/20 follow-through | 1 to 7 days after | Receipt, first-time-buyer guidance, replenishment enrollment, honest feedback, service recovery | Headset has reported a greater share of sales from new and visiting customers around 4/20, making post-event onboarding especially important. |
| Memorial Day weekend | 5 to 10 days before; hours day-of | Weekend planning, local event information, travel or outdoor context where relevant | Match product and message claims to jurisdiction and retailer policy. |
| Pride season and local community events | Aligned with actual participation | Authentic event support, hours, partnership, community information | Do not use identity as a targeting inference or a superficial promotional costume. |
| July 4 | 5 to 10 days before; hours and cutoff reminder | Holiday planning, store hours, pickup deadline, responsible-use education | Avoid unverified safety or health claims. |
| 7/10 Oil Day | 5 to 10 days before | Concentrate education, product discovery, category-specific event | Target only customers whose stated preference or purchase history makes it relevant. |
| Labor Day weekend | 5 to 10 days before | Weekend planning, seasonal transition, hours, local event | Use the same pre-event suppression discipline as other holiday weekends. |
| Halloween | 7 to 10 days before; one day-of operational message if needed | Event invitation, seasonal product story, store hours | Keep the creative readable and the offer conditions plain. |
| Green Wednesday early lead-up | 7 to 10 days before Thanksgiving | Shopping plan, inventory preview, preorder education, loyalty or VIP access | Use purchase affinity and preferred location to reduce broad, duplicative promotion. |
| Green Wednesday final reminder | Monday or Tuesday before; day-of only when useful | Hours, pickup cutoff, verified offer, inventory update | Headset has documented Green Wednesday as a significant cannabis shopping day. Protect deliverability before the peak. |
| Thanksgiving | Before the holiday; day-of only for verified operations | Closure, reduced hours, pickup status, support availability | Service communication takes priority over promotion. |
| Black Friday and Cyber Monday | Preview before; distinct day-of message only when the offer differs | Retail event, online ordering, limited inventory, digital experience | Do not send three versions of the same offer across Green Wednesday, Black Friday, and Cyber Monday. |
| December holidays | Early planning, shipping or pickup cutoff, final hours | Gift planning where permitted, loyalty, store hours, last pickup, year-end education | Use the customer’s known shopping mode and avoid assuming which holiday they celebrate. |
| Store anniversary and local milestones | 1 to 3 weeks before; recognition day-of | Customer appreciation, history, event invitation, loyalty recognition | Often more credible than a generic national holiday because the relationship is specific. |
A holiday plan is a sequence of customer jobs. Early messages help people plan. Late messages clarify logistics. Day-of messages resolve immediacy. Post-event automations convert one-time traffic into an ongoing relationship. Sending the same discount four times is not a calendar strategy.
How Cadence Progress Is Calculated
Cadence progress compares actual outbound messages in the selected reporting period with the strategy’s target message volume for that same period. It is a pacing measure, not a quality score.
For Growth and High Frequency, the target combines separate lifecycle groups. Recent customers use the primary weekly cadence. Re-engagement customers use the configured weekly cadence. Dormant customers use the configured monthly cadence. For Essential and Consistent, the calculation uses the selected active-customer audience and the strategy’s primary cadence.
More than 100 percent means the volume target was exceeded. It does not automatically mean performance improved. Check delivery, opt-outs, replies, customer frequency, and purchase outcomes before deciding to keep the higher pace.
Reporting Period and Planning Window
The reporting period controls the historical performance window. Use the same duration as a forward planning window so the review and decision cycle remain consistent.
Look backward
Today, 7 days, 28 days, 3 months, or a custom range determines which message and outcome records are summarized.
Interpret the gap
Compare actual volume, delivery, engagement, customer frequency, budget, and attribution with the selected strategy.
Look forward
The operating plan turns the selected duration into upcoming send dates and adds improvements discovered by analysis.
The Growth calendar starts with Monday, Wednesday, and Friday sends, common U.S. retail holidays, and activation dates on the 1st, 2nd, 15th, and 16th. These are planning anchors. Local events, inventory, state rules, brand moments, suppression, and customer behavior should refine the final calendar.
Budget and Investment
Suggested budget estimates what the selected strategy would cost during the selected time frame. It uses the target message count and the blended message rate. The blended rate accounts for the observed SMS and MMS mix when available.
A user-defined budget can be entered as daily, weekly, monthly, or annual. The planning model should convert that amount into the selected reporting period before calculating coverage and funded message volume. For example, a monthly budget is prorated across a 7-day view and expanded across a 3-month view.
Budget is a guardrail, not a command to spend. If deliverability weakens, opt-outs rise, or content becomes repetitive, the right action may be to improve the program before funding more sends.
Attribution and Potential Gain
A trustworthy measurement system separates observed attribution from modeled attribution. This distinction matters because a purchase after a text is evidence of sequence, not automatic proof that the text caused the purchase.
Contact’s latest delivered message occurred in the reporting period.
A tracked click or age-gate view may occur, but neither is required.
The latest transaction occurs on or after delivery and before the period ends.
Purchasers are divided by unique delivered contacts.
The rate and average ticket inform a directional opportunity.
When contact and transaction data are available, measure unique contacts whose latest delivered-message timestamp falls within the period and whose next known transaction occurs on or after that delivery. A verified age-gate view can be treated as a separate intent signal. Purchase timing can then be grouped into same day, 1 to 3 days, 4 to 7 days, and 8 or more days.
When no observed delivered-contact cohort exists, the default reach model assumes 3 purchases per 100 delivered texts and uses a $50 average-ticket fallback unless synced sales data or a configured value is available. An age-gate view can receive a higher configured purchase-rate assumption because it is a stronger human-intent signal than delivery alone.
| Attribution option | How it works | When to use it |
|---|---|---|
| Reach based | Uses the observed delivered-contact rate when available. Otherwise starts with 3 purchases per 100 delivered texts and a stronger age-gate assumption. | Default planning model |
| Conservative reach | Uses half the observed rate, or a 1.5 per 100 delivered fallback with a lower age-gate assumption. | Budget planning that needs a wider margin of safety |
| Engagement weighted | Uses observed rates when available, or a lower delivery baseline with more weight on age-gate intent. | Programs with reliable tracked landing-page activity |
| Observed point-of-sale | Prioritizes the delivered-contact cohort and available point-of-sale attribution. | Accounts with dependable contact and transaction sync |
| Custom | Uses the purchases-per-100, age-gate purchase rate, and average-ticket assumptions entered by the user. | Teams with an approved internal measurement model |
If purchasing information is unavailable, observed purchase sections should remain hidden. Modeled potential gain can still be used for planning when its assumptions are shown clearly, but it should never be presented as guaranteed revenue or causal proof.
The Six Views a Messaging Team Must Maintain
Is the overall channel healthy?
Summarizes outbound and inbound activity, delivery, failures, opt-outs, source mix, cadence pacing, budget, and cross-channel trends.
Which programs are working?
Combines one-time and automated campaigns, then compares audience, delivery, engagement, failures, cost, content, and program coverage.
Where is reach weakening?
Uses messages that were actually sent to compare carrier volume, delivered messages, failed messages, and carrier-specific delivery rates.
Who is being reached and how often?
Measures unique customers texted, delivered reach, frequency distribution, failures, engagement, purchases after delivery, purchase timing, and value tiers.
Is the message earning action?
Reviews tracked clicks, age-gate views, representative message content, readability, personalization, offer clarity, trust, and calls to action.
What should the team do next?
Combines the base strategy calendar with dated operational and creative recommendations.
How to Read Messaging Performance
Metrics That Matter
| Metric | Definition | What it helps answer | Important caution |
|---|---|---|---|
| Outbound messages | SMS and MMS sent across one-time campaigns, automated campaigns, and one-to-one messaging | How much messaging activity occurred? | Volume alone is not performance |
| Delivery rate | Delivered messages divided by outbound messages | How much intended reach became carrier-confirmed delivery? | Investigate by carrier, source, and program |
| Failure rate | Failed messages divided by outbound messages | Where are numbers, providers, content, or carrier paths underperforming? | Read provider responses and timestamps |
| Tracked click rate | Tracked link clicks divided by delivered messages | Did the message earn a measurable action? | A purchase can occur without a click |
| Age-gate views | Customers who passed the age gate after opening a tracked message URL | How much high-intent human activity occurred? | A view is intent, not a completed purchase |
| Inbound messages | Customer replies received during the period | Is messaging creating conversation and support demand? | Staff coverage affects the value of replies |
| Opt-out rate | Opt-outs divided by outbound volume | Is cadence or relevance creating fatigue? | Monitor by source and message type |
| Customers texted | Unique contacts receiving messaging activity | Is volume reaching more people or repeatedly reaching the same people? | Use frequency distribution with this metric |
| Purchases per 100 delivered contacts | Observed purchasers divided by unique contacts whose latest delivered text occurred in the period | How often did purchase follow delivered reach? | Sequence does not prove causation |
| Suggested budget | Target message volume multiplied by the blended message rate | What investment supports the selected cadence? | It is period-specific and estimate-based |
| Potential gain | Estimated revenue minus planned message spend | What directional opportunity does the model imply? | Assumptions must remain visible |
When delivery weakens, use SMS deliverability troubleshooting for dispensaries before changing creative or increasing frequency. A carrier-specific decline can make a good campaign appear ineffective.
The Decision Rules an AI or Marketer Should Follow
A planner should not jump from a customer record directly to message copy. It should resolve the following rules in order and retain the reason for every decision.
Confirm phone validity, opt-out state, applicable consent and use case, age-gating requirements, location rules, and any account-level suppression.
Handle order status, safety, account, and direct-reply events before considering lifecycle or promotional messaging.
Choose the most specific current state: new subscriber, active order, first-time buyer, replenishment due, recent active, VIP, engaged non-purchaser, re-engagement, dormant, or active conversation.
Choose one primary purpose that directly answers the customer’s current situation. Do not combine an order update, a win-back offer, and a review request in one text.
Use automation when behavior or an event creates the moment. Use one-time campaigns for inventory, launches, holidays, flash sales, and local events. Use schedule-based campaigns for recurring editorial cadence.
Use event time for service and behavior triggers. Otherwise choose the next strategy day that fits the message type and does not violate a frequency cap.
Inspect all scheduled campaigns, automated campaigns, replies, and recent sends for the customer. Keep the higher-priority message and move, merge, or suppress the lower-priority one.
State the value clearly, use personalization only when reliable, include one primary action, preserve required disclosures and opt-out language, and verify offer, link, inventory, timing, and capitalization.
Attach a measurable goal and stop condition before sending. Purchase, fulfillment, reply, resolution, opt-out, invalid number, or expired relevance should end the matching sequence.
Compare delivery, failure, opt-out, reply, click, age-gate view, and purchase timing by contact type, message type, campaign type, day, and carrier. Change one controllable variable at a time.
Never infer sensitive traits or fabricate customer facts. Use explicit customer behavior and configured business rules. If required data is missing, return a proposed baseline with lower confidence and request human review.
A Machine-Readable Messaging Decision Contract
When this article is supplied to an AI with a customer record and a planning window, require a structured answer. This makes the reasoning inspectable and easier to validate before any message is scheduled.
{
"eligibility": {
"canText": true,
"consentBasis": "configured marketing or transactional basis",
"suppressionReasons": []
},
"contactType": "recent-active",
"behaviorEvidence": [
"last purchase was 24 days ago",
"no unresolved conversation",
"no order currently in progress"
],
"strategy": {
"type": "growth",
"maximumPlannedCadence": "3 touches per week"
},
"decision": {
"campaignType": "schedule-based",
"program": "product education",
"messageType": "education",
"sendAt": "YYYY-MM-DDTHH:MM:SS-07:00",
"dayReason": "next eligible Wednesday in the roadmap",
"goal": "earn a qualified reply or age-gate view",
"messageDraft": "[human-reviewed SMS draft]"
},
"controls": {
"frequencyCheck": "passed",
"collisionCheck": "passed",
"exitConditions": ["purchase", "reply", "opt-out", "expired relevance"]
},
"measurement": {
"primary": "delivered reach",
"secondary": ["reply", "tracked click", "age-gate view", "purchase after delivery"],
"confidence": "medium"
},
"humanReviewRequired": true
}
The AI should return no-send when eligibility fails, when no relevant message exists, when frequency or collision controls fail, or when the available data cannot support a responsible choice. The article is a decision framework, not authorization to send automatically.
Why AI Is the Right Operating Layer
The modern problem is not writing more copy. It is resolving a different strategy for every eligible customer across consent, order state, purchase recency, product affinity, recent sends, replies, tracked intent, inventory, store location, carrier health, calendar moments, budget, and staff coverage. Those variables create more combinations than a marketing calendar or a fixed automation tree can responsibly manage by hand.
AI is a strong fit because it can turn that complexity into repeated customer-level decisions. It can classify current state, explain why a message is or is not relevant, resolve collisions, choose a campaign mode, draft content for one message job, select an eligible day, and learn from outcomes. It is most valuable as an operating layer between business rules and human approval, not as an unrestricted copy generator.
Read the current state
Summarize recent purchases, messages, replies, order activity, product patterns, preferences, and the planning calendar without exposing unnecessary raw records.
Choose or decline the next action
Return a message job, audience reason, timing reason, campaign mode, frequency decision, exit condition, and confidence, or return no-send.
Update the customer strategy
Compare delivery, reply, click, age-gate view, purchase timing, opt-out, and silence by contact state, message job, day, and carrier.
A compact analysis can use aggregates, representative message samples, carrier performance, customer-frequency groups, and completed outcomes instead of sending an expensive customer-level dataset. A useful analysis returns:
- A short summary of the largest opportunity.
- Three to five specific improvements tied to delivery, reach, frequency, engagement, or revenue.
- A directional gain estimate constrained by the configured attribution assumptions.
- Dated roadmap items with a program, audience, goal, message draft or operational instruction, and reason.
Deterministic controls must surround the model. Eligibility, opt-out, consent, frequency caps, required transactional events, and hard suppression should be resolved before AI judgment. The model should never infer sensitive traits, fabricate inventory or offers, or send because it cannot find a better idea. A human should review local rules, terms, links, age-gating, and message accuracy before scheduling consequential campaigns.
Step-by-Step Implementation
- Confirm permission and sender identity. Audit consent capture, opt-out handling, brand registration, campaign registration, and sending numbers. Start with 10DLC for dispensaries.
- Choose the reporting period. Use Today for active operations, 7 days for weekly diagnostics, 28 days for monthly planning, 3 months for trend review, or Custom for a defined business period.
- Select the strategy. Use Essential, Consistent, Growth, or High Frequency based on operating maturity, not ambition alone.
- Define an active customer. Choose All or a 3, 6, 12, 18, or 24-month purchase window. Confirm purchase history is syncing before interpreting the audience count.
- Configure lifecycle boundaries. Set when recent customers become re-engagement customers and when they become dormant. Match the definitions to normal repurchase timing.
- Set budget and attribution assumptions. Enter the budget period, validate message rates, use synced average ticket when available, and document whether attribution is observed or modeled.
- Build the evergreen program catalog. Separate one-time campaigns from automated campaigns. Give each program an audience, trigger or date, purpose, suppression rule, stop condition, and metric.
- Review Messaging, Campaigns, Carriers, Customers, and Engagement. Diagnose delivery before blaming copy. Diagnose frequency before increasing volume.
- Analyze the clearest performance gap. Review the recommendation, validate the evidence, and add only useful actions to the operating plan.
- Operate the forward plan. Assign an owner to each send, confirm inventory and terms, test the message and link, then compare the next period against the same metrics.
Practical Examples
First purchase completed today
Contact type: first-time buyer. Campaign: post-purchase automation. Message: receipt immediately, then first-purchase guidance after fulfillment. Day: event time, not the next promotional day. Exit: remove from welcome and abandoned-cart sequences.
Purchased 24 days ago and viewed a product message yesterday
Contact type: recent active, engaged non-purchaser for this visit. Campaign: behavior-aware scheduled follow-up. Message: relevant clarification or inventory next step. Day: within 1 to 3 days, preferably the next eligible Wednesday under Growth. Exit: purchase, reply, or frequency conflict.
No purchase for 92 days
Contact type: re-engagement. Campaign: win-back automation. Message: a genuine reason to return, not a generic “we miss you.” Day: one planned weekly touch, such as Wednesday. Exit: purchase, reply, opt-out, or day 180.
No purchase for 230 days
Contact type: dormant. Campaign: long-term reactivation automation. Message: brand reintroduction or a meaningful store change. Day: one monthly activation date, such as the 1st or 15th. Exit: weak response, delivery concern, purchase, or opt-out.
Order delayed while a Friday flash sale is scheduled
Contact type: active order. Campaign: order-status automation. Message: accurate delay update and next step. Day: immediately. Collision: suppress the flash-sale message until the order issue is resolved.
Active customer already received three texts this week
Contact type: recent active at the Growth cap. Decision: no additional promotional send. Necessary order or account notifications may still send under their proper purpose. Move the next eligible marketing message to the following strategy window.
Performance can override the roadmap. If one carrier is materially underperforming, if opt-outs are rising, or if a contact group is receiving too many messages, reduce or pause the affected marketing volume before adding new sends.
Common Mistakes
| Mistake | Why it fails | Better operating rule |
|---|---|---|
| Treating Growth as three weekly blasts | Repetitive promotion creates overlap and fatigue | Distribute volume across service, lifecycle, education, launch, and promotion |
| Counting transactional consent as marketing consent | Message purpose may exceed the permission collected | Keep consent records and message intent aligned |
| Increasing volume when delivery falls | More sends can amplify filtering and waste | Diagnose carrier, provider, content, registration, and list quality first |
| Using clicks as the only outcome | Customers can purchase without clicking | Read clicks, age-gate views, replies, and post-delivery purchase timing together |
| Calling modeled revenue observed revenue | It overstates confidence and weakens trust | Show the rate, average ticket, source, and assumptions |
| Ignoring unique-customer frequency | Total volume can hide repeated sends to the same people | Review customers texted and the frequency distribution |
| Leaving automations without exit conditions | Customers continue receiving irrelevant messages after conversion | Exit on purchase, reply, pickup, opt-out, or another completed goal |
| Review gating | It creates deceptive feedback collection and platform risk | Invite honest reviews from eligible customers without filtering by sentiment |
| Using number replacement to evade filtering | It avoids the cause and can worsen trust signals | Correct consent, registration, content, sender behavior, and list quality |
FAQ
- Question: Which messaging strategy should most dispensaries choose?
- Answer: Growth is the recommended target for teams that can operate one-time and automated campaigns, manage suppression, monitor carriers, and produce varied content. A newer program may be better served by Essential or Consistent until those controls are reliable.
- Question: Does Growth mean every active customer receives three promotional texts each week?
- Answer: No. Growth is a total operating cadence supported by campaigns, automated campaigns, service messages, lifecycle programs, and suppression. The same customer should not receive every available send.
- Question: What happens if no active customers are found?
- Answer: First confirm purchase data is available and current. A planning system may temporarily use all otherwise eligible contacts, but it must label that fallback and should not claim the entire list is behaviorally active.
- Question: Are automations separate from campaigns?
- Answer: Automations are automated campaigns. The Campaigns report combines one-time and automated programs while identifying how each program runs.
- Question: Which automated texts should every retailer consider?
- Answer: Start with permission confirmation, welcome, order and account updates, first-purchase guidance, abandoned-cart recovery, replenishment, rewards, honest review requests, birthday and anniversary recognition, lapsing-soon, win-back, dormant reintroduction, and conversation handoff. Activate only the programs supported by reliable data, consent, and an explicit exit rule.
- Question: How should the system decide what to text one specific customer?
- Answer: Verify eligibility, resolve any active order or conversation, assign the most specific contact type from observed behavior, choose one relevant message job, select automation or one-time delivery, choose event time or the next eligible strategy day, then run frequency, collision, exit, and content checks.
- Question: What should be sent on Monday, Wednesday, and Friday under Growth?
- Answer: Use Monday for utility such as rewards, education, or replenishment; Wednesday for discovery, VIP access, education, or win-back; and Friday for weekend plans, local events, or a bounded flash sale. These are starting assignments that should change when observed performance supports a better plan.
- Question: When should the system decide not to send?
- Answer: Do not send when the customer is ineligible, the message lacks a relevant purpose, the frequency cap is reached, a higher-priority order or support message conflicts, the program’s exit condition occurred, or the available data cannot support a responsible decision.
- Question: Why are order notifications included in a messaging strategy?
- Answer: Messaging performance is not only promotional. Order and account notifications build trust, reduce support demand, and shape how customers perceive the entire channel.
- Question: How is the suggested budget calculated?
- Answer: The strategy target message count is multiplied by the blended message rate for the selected period. A configured daily, weekly, monthly, or annual budget is converted into that same period for coverage comparison.
- Question: What does purchases per 100 delivered contacts mean?
- Answer: It is the number of unique contacts who purchased on or after their latest delivered text in the period, divided by the unique delivered-contact cohort, multiplied by 100. It describes an observed sequence and does not prove that the text caused the purchase.
- Question: Why does the model count purchases that did not have a tracked click?
- Answer: A text can influence a store visit, search, direct navigation, or later purchase without a tracked click. Clicks and age-gate views are useful intent signals, but they are not the only plausible path from message to purchase.
- Question: What is the default attribution assumption when purchase data is unavailable?
- Answer: A planning model may start with 3 purchases per 100 delivered texts and a $50 average-ticket fallback unless the team configures another value. The result must be labeled as modeled, and observed purchase sections should remain hidden when no observed cohort exists.
- Question: Should a dispensary use High Frequency as a growth shortcut?
- Answer: No. Daily messaging requires excellent consent, segmentation, content, suppression, sender reputation, and monitoring. If opt-outs, complaints, failures, or engagement weaken, reduce frequency and fix the system.
- Question: How should a dispensary plan for 4/20 and Green Wednesday?
- Answer: Treat each as a campaign window. Use early lead-up for preference capture, education, VIP access, and planning; the final days for hours, ordering, and verified availability; day-of for one useful operational or time-sensitive message; and post-event for first-time-buyer guidance, feedback, and lifecycle enrollment.
- Question: Why use AI for messaging strategy?
- Answer: The correct decision varies by customer state, recent behavior, order status, purchase recency, product pattern, prior frequency, calendar, carrier health, inventory, and local operations. AI can evaluate those combinations consistently, explain the decision, generate a draft, and return no-send, while deterministic eligibility and human review remain in control.
- Question: What should happen when one carrier underperforms?
- Answer: Compare sent, delivered, failed, provider response, message content, links, sender identity, registration, and timing for that carrier. Use controlled tests after correcting the likely cause. Do not rotate numbers to evade carrier controls.
- Question: How should the forward plan be used?
- Answer: Treat it as the operating plan for the next period. Confirm each date, audience, goal, campaign type, content, suppression rule, owner, and expected metric before scheduling.
- Question: Should an AI receive the entire customer database?
- Answer: No. Use the minimum necessary customer state for individual decisions and compact aggregates for program analysis. Minimize data, restrict access, log the reasoning, and review both the data-handling design and the final recommendation.
- Question: Is this guide legal advice?
- Answer: No. It is an educational operating framework. Consult qualified counsel for federal, state, local, carrier, and cannabis-specific requirements that apply to your business.
Sources and Further Reading
- CTIA Messaging Principles and Best Practices: industry guidance focused on wanted messages, consumer trust, consent, and opt-out handling.
- The Campaign Registry overview for brands and campaign service providers: explains the role of brands, providers, and registration in the 10DLC ecosystem.
- FCC guidance on unwanted calls and texts: consumer-protection context and complaint information.
- Twilio 2024 State of Customer Engagement: research on the gap between customer expectations and brands’ ability to use customer data effectively.
- Twilio 2025 State of Customer Engagement: research on relevance, trust, timing, and the consequences of impersonal engagement.
- Attentive 2025 consumer personalization study: research on consumers ignoring irrelevant messages and expecting brands to learn from shopping behavior.
- Klaviyo 2024 SMS Consumer Report: consumer research on messaging frequency, timing, and expectations.
- Headset 4/20 cannabis retail analysis: current reporting on 4/20 shopping behavior, category mix, and discounts.
- Headset Green Wednesday analysis: historical context for the day-before-Thanksgiving cannabis retail occasion.
- Headset cannabis holiday demand analysis: context for Green Wednesday, Black Friday, and other holiday demand patterns.
- Opt-In and Consent for Dispensary SMS Marketing: practical consent collection, storage, and opt-out guidance.
- SMS Deliverability Troubleshooting for Dispensaries: a diagnostic process for blocks, filtering, low reach, and carrier-specific problems.
- Dispensary Mass Texting: Strategy, Frequency, and Compliance Tips: how to balance frequency, value, and trust.
Further Reading and Implementation Resources
- Dispensary text marketing strategy, segmentation, and automations
- SMS automation flows for dispensaries
- Two-way SMS for dispensaries
- Cannabis texting glossary
- Blackleaf Learn
Final operating principle: the goal is not simply to send more texts. The goal is to deliver more useful messages to more eligible customers at a sustainable frequency, learn from the response, and make the next message better.