- Design the next step-and the stopping point.
- Start where the data can support the promise.
- Flow 1: invite a lapsed shopper back.
- Flow 2: communicate actual pickup readiness.
- Flow 3: make the next visit useful.
- Write a flow specification before adding nodes.
- One contact plan across campaigns and flows.
- Eligibility is more than a trigger and a polite message.
- Test the paths that should not send.
- Separate the sequence activity from the business result.
- Automation-flow questions, answered.
- Build one sequence your team can explain.
Design the next step-and the stopping point.
Dispensary SMS automation flows connect a supported event or condition to a reviewed messaging sequence. Define who qualifies, when the next step is useful and what cancels it. A timer or customer record is not enough to establish permission, readiness or a reason to send.
This guide gives three practical sequence designs: winback, pickup readiness and second purchase. Configure and test the supported controls for your store; these diagrams are planning examples, not claims that every check runs automatically. For the wider channel and customer-journey framework, read dispensary marketing automation. For Blackleaf’s available workflow types, see dispensary SMS automations.
Blackleaf texting is available separately from Blackleaf POS. Confirm the event and fields from your supported existing system through POS texting and integrations.
Start where the data can support the promise.
Choose one customer situation with a reliable source, a staffed owner and a measurable next action. First establish whether the business, message purpose and route are supported. Review actual permission and current opt-outs before configuring a send.
- Winback: use dependable completed-purchase history and an inactivity rule that fits the store. Unknown history is not a lapsed customer.
- Pickup readiness: use the current fulfillment state, not a receipt import or elapsed time. Agree which system owns the notification.
- Second purchase: confirm that the initial purchase really is the first qualifying completed purchase within the available history.
Cart recovery additionally needs a supported cart event and usable identity; a product-page visit is not an abandoned cart. Birthday outreach needs an appropriate date, permission and verified benefit. Add either when the inputs and purpose are clear rather than assuming four flows must launch together. See cart recovery and birthday workflows.
Flow 1: invite a lapsed shopper back.
- 01Observe inactivity
Latest qualifying purchase passes the chosen lapse threshold.
- 02Check current state
Verify history, store, permission, suppression and other contact.
- 03Review one invitation
Confirm a relevant reason, real terms and a useful destination.
- 04End deliberately
A new qualifying purchase exits; non-response reaches a limit.
Hold or exit: New purchase, opt-out or lost eligibility ends affected outreach. Stale data, an open order, service issue or conflicting campaign requires review.
Example timing: a store tests a 60-day lapse threshold and one invitation. That number is illustrative, not a universal best practice. Choose it from observed purchase intervals and confirm whether activity is measured at one store or across the organization.
Save the source timestamp and qualifying transaction definition. Recheck current purchases just before the planned message; if the feed is behind, hold rather than telling a recent buyer they have been away. A return or canceled transaction may change the last qualifying purchase.
An optional follow-up must add useful information, such as a real benefit deadline. Recheck eligibility, contact conflicts and terms before it proceeds. Set a finite end and re-entry cooldown; do not endlessly recycle a static “inactive” label.
Measure: eligible customers, contacted customers, qualifying returns in a stated window, opt-outs and full costs. Attributed returns do not establish extra purchases caused by texting. Explore the winback workflow for audience and offer detail.
Flow 2: communicate actual pickup readiness.
- 01Receive the event
The store or authoritative system records a genuine ready state.
- 02Match the order
Check order, customer, location and latest version; reject repeats.
- 03Review the update
Use accurate instructions through the permitted notification setup.
- 04Reconcile the outcome
Track message state and actual pickup or cancellation separately.
Hold or exit: Canceled, collected or changed orders stop stale ready messages. Missing identity, location, current state or permission means hold.
A customer sync or completed-purchase feed may not contain fulfillment events. Confirm the actual event, update delay and event owner before planning around it. “Order received,” “ready,” “paid” and “collected” are different states.
One reviewed notice per genuine readiness event is a possible design; it is not a universal frequency rule. Before an optional reminder, check that the order is still ready, the pickup window is valid and another system has not already sent the same notice. A queued reminder must not outlive a cancellation or collection.
Repeated or out-of-order source events need a durable notification rule. A timeout can occur after a send was accepted, so reconcile the existing attempt before creating another. Never use a customer-service label to bypass a prohibited route.
Measure: source-event time, request time, final delivery evidence and actual collection separately. Do not count a delivered text as a recovered order. Read order alerts and assign replies to the shared inbox team.
Flow 3: make the next visit useful.
- 01Verify the first sale
Confirm a qualifying completed purchase and available history.
- 02Wait with a purpose
Choose a test interval that fits the visit and customer context.
- 03Recheck and review
A second purchase exits; review permission, contact and the offer.
- 04Send or hold
Use one reviewed invitation, then end or follow up deliberately.
Hold or exit: Second qualifying purchase, opt-out, loss of eligibility or sequence end exits. Open service issues, returns, stale stock or conflicting contact need review.
Example timing: review an invitation seven days after the first qualifying purchase. Seven days is a planning example, not a recommended interval for every shopper or product. Do not assume the customer has run out, wants the same item or needs a particular effect.
The first completed purchase in a new import may be the first visible record rather than the customer’s first-ever visit. Use the history coverage in the audience definition. A refund, identity correction or delayed transaction can change who still qualifies.
Give a relevant, factual reason to return. If an incentive is used, verify current sellable stock, location, price, dates, eligibility and margin. Review any changed creative or offer before launch; a saved draft is not approval.
Measure: qualifying second purchasers and time to second purchase within the same observation window, including returns, costs and comparison-group limits. For audience logic, read the segmentation guide.
Write a flow specification before adding nodes.
A reviewable specification lets staff, the integration owner and the messaging operator agree on what should happen. Confirm which decisions are enforced by software and which require a person.
| Decision | Record and test |
|---|---|
| Entry | Real source event or threshold crossing, stable event/customer ID, location, timestamp, history coverage and duplicate handling. |
| Eligibility | Actual permission, current suppression, supported business/use case/route, identity match and account restrictions. |
| Wait | Purpose of delay, source refresh time, store/customer time zone and permitted send window. A zero configured delay need not mean instant execution. |
| Message | Current version, verified facts, sender, template, destination, required review and approval, plus who handles replies. |
| Exit and re-entry | Qualifying purchase or status change, opt-out, sequence limit, cooldown and behavior for unknown or stale data. |
| Owner and outcome | Who can pause or change work, what happens to people already waiting, error escalation, reporting window, costs and qualifying result. |
For custom implementations, review the Blackleaf API developer guide. Do not infer an idempotency guarantee, instant event delivery or every trigger from an integration logo.
One contact plan across campaigns and flows.
Two independently eligible flows can still create an excessive customer experience. Review scheduled campaigns, lifecycle sequences, reminders and open service conversations together. Define priority, frequency limits and exclusions across the actual supported systems.
- Purchase during a wait: exit the relevant winback or second-purchase sequence; do not treat every purchase as an order-ready event.
- Customer reply: route the question to a staffed owner and pause affected promotion where appropriate. A reply does not necessarily end an unrelated order update.
- Opt-out or wrong-number report: follow the supported suppression process and prevent affected future outreach; do not override it to finish the sequence.
- Campaign conflict: select one useful contact or hold the lower-priority message. Confirm how the account actually enforces the rule.
AI can help prepare audience rules or copy through supported AI texting workflows. Review the fields, missing facts, current content and approval settings. Recurring Texting Agents prepare work on a schedule; that differs from a customer-event flow. Connected Blackleaf POS AI agents are in production in California. More states are rolling out soon.
Eligibility is more than a trigger and a polite message.
Marketing permission, current opt-outs, provider policy, sender registration, age controls and permitted content are different checks. A purchase, loyalty membership or saved phone number does not establish blanket permission for future campaigns.
For a specific provider example, Twilio prohibits cannabis/CBD business SMS and MMS in the United States and Canada regardless of message content. Neutral wording, an age gate, registration or a transactional label does not create an exception. This is a Twilio-specific restriction; confirm the permitted Blackleaf setup for your business and use case.
Review permission records, messaging requirements and message delivery evidence. Do not vary spelling, rotate senders or repeatedly retry a prohibited route to make an automation run.
Test the paths that should not send.
Use authorized test recipients and a permitted route. Record expected and observed results; a successful happy-path test does not validate the exit or failure paths.
| Test | Expected design outcome |
|---|---|
| Same event arrives twice | One intended action. Reconcile the durable event and existing attempt before retrying. |
| Purchase happens during a wait | The relevant acquisition/winback message exits once the qualifying new state is available. Measure source delay. |
| Opt-out before next step | Further affected outreach is suppressed through the supported process. |
| Data is missing or stale | Hold the action that depends on it; missing data is not a negative answer. |
| Another campaign is scheduled | Apply the agreed priority and contact limit; do not assume flows exclude one another automatically. |
| Offer expires or order cancels | Stop the obsolete message and review any necessary service correction. |
| Send result is uncertain | Keep the unknown attempt visible and reconcile message records before creating a new send. |
| Live sequence is revised | Account for customers waiting in the old version; prevent duplicate entry or unintended continuation. |
Agree who watches failures, replies and changes after launch. For active delivery issues, use the troubleshooting guide. A small test is not a delivery guarantee for the whole audience.
Separate the sequence activity from the business result.
Save the eligible audience, version, exclusions, observation window and intended result before launch. Follow entrants, held/exited customers, send attempts and final message states separately. Keep pending or unknown outcomes visible.
For a return-visit flow, report qualifying buyers and net sales under a stated attribution rule. For readiness, report actual collection or cancellation. Use explicit denominators: attempts, delivered messages, entrants and contacted customers answer different questions.
Include platform and message usage, setup or operating work, incentives and returns. Do not subtract discounts twice when they are already reflected in net sales. Attributed revenue alone is not profit or evidence of incremental lift. A suitable randomized holdout observed over the same period can help estimate natural returns; overlapping campaigns and small samples still limit the conclusion.
Use the SMS ROI guide and billing-unit guide. Keep, change or stop a flow based on measured usefulness rather than increasing its step count.
Automation-flow questions, answered.
What is a dispensary SMS automation flow?
It is a configured sequence that evaluates a supported customer event or condition, checks eligibility, waits when appropriate and performs a reviewed messaging action. A complete design also defines exits, re-entry, staff ownership and the outcome to measure.
Which flow should a dispensary build first?
Choose one useful customer situation with dependable data and an owner. A pickup update needs a real readiness event; a second-purchase or winback sequence needs reliable completed-purchase history and marketing permission. Do not begin with a long sequence just because templates exist.
Is a 60-day winback trigger right for every customer?
No. Sixty days is an illustrative test threshold, not a universal rule. Review the store’s purchase intervals, customer segment, returns, history coverage and cross-store activity. Missing or delayed history does not prove inactivity.
Does a purchase-history integration provide pickup-ready events?
Not necessarily. A connector can supply completed transactions without live fulfillment events. Confirm the event, stable order ID, current state, location, recipient and update timing for the exact source before enabling a readiness notification.
Should a purchase or reply stop every automation?
A qualifying purchase should end the relevant acquisition or winback sequence. A reply may require a staffed pause or handoff rather than ending every workflow. Define the event-specific rule and test how it is implemented. An opt-out or loss of eligibility must prevent further affected outreach.
How many reminders should the flow send?
Start with one useful message and a finite sequence. Add a follow-up only when it adds value, the person remains eligible and the overall contact plan allows it. Choose delays, limits and cooldowns from the store context; example intervals are not recommended universal cadence.
Do transactional labels or registration guarantee delivery?
No. Customer permission, business and use-case support, sender setup, content, destination and provider restrictions are separate checks. A service label, neutral wording, age gate or registration does not override a prohibited business or route.
Can AI decide who enters a flow and send it?
Supported AI tools can help prepare a rule or draft, but the source fields, eligibility, approvals and authorized sending actions still need review. An AI score does not prove current intent or permission. Blackleaf campaign preparation and connected POS AI agents in production in California are distinct workflows.
Do we need Blackleaf POS?
No Blackleaf POS switch is required for supported existing-system texting. Confirm the connector, authorized import or application event and its actual fields, identity match, history coverage and update timing. Not every connection supplies every trigger.
What should we test before activation?
Test a real qualifying event, duplicate or late event, missing data, purchase during a wait, opt-out, conflicting campaign, expired offer and uncertain send. Record the expected hold, exit or reviewed action and compare it with the observed result using authorized test recipients and a permitted route.
Does attributed revenue prove that automation created extra sales?
No. Attribution matches a purchase to a defined reporting rule and window. A suitable randomized holdout observed over the same period can help estimate natural returns. Include total costs, returns, discounts, overlapping campaigns and unknown delivery outcomes.
What happens when a live flow changes?
Record the version, stop new entry where appropriate and account for customers already waiting in the old sequence. Test the revised conditions and required approvals before restarting. Confirm whether pending work is canceled, retained or needs a supported migration; do not assume a duplicate flow moves customers automatically.
Build one sequence your team can explain.
Bring Blackleaf your current system, one customer situation, the source event and who will own the next action. Review the supported connection, eligibility, message, exits and measurement before activation.