Use a dispensary SMS template to answer a real customer need: what changed, what they should do next and how to get help. Choose the message purpose first, then confirm permission, current data and the permitted sending setup.
Below are nine selectable drafts with audience rules, timing and exclusions. Oak & Pine is a fictional store. These are writing examples, not approved campaigns or customer results.
Choose a template · See the opt-out example · Explore Blackleaf texting
Blackleaf requirements: Obtain explicit recipient consent and confirm age before texting, including service and support messages. In the message flow, verify the intended recipient by having them select the birthday already on file; never reveal the saved birthday. These company requirements are separate from legal and provider review. See the age-verification guide for details.
Check the business, recipient market, message purpose, consent evidence, current suppression, text, media and linked destination with the actual provider and route. Marketing permission and order-notification permission are different. Neutral wording or an age-gated landing page does not turn a promotion into a service update or bypass a prohibition.
For a concrete example, Twilio’s US and Canada policy prohibits cannabis and CBD product businesses from using its SMS/MMS service regardless of message content, including 2FA. These drafts are not a suggestion to use a prohibited service. Review messaging requirements and opt-in records for the full program.
Choose an image and paste the final message to inspect text size, line breaks and image legibility together. This is an illustrative browser preview, not a live Blackleaf inbox or an exact rendering from a messaging app.
Enable JavaScript to use the preview. The message templates below remain available.
No image selected.
Illustrative layout · nothing is sent
Choose an image or load the illustrative flyer.
Preview adjusts to the space available on your screen.
Whole image shown without cropping.
Review at the smallest width: can you read the headline, hours or offer terms without zooming? Keep essential information in the message text as well as the image. Check long personalized values and links; review the actual mobile destination separately.
Square crop is a visual stress test and can hide edges. Carrier compression, supported file types, GIF playback, app layout and accessibility settings can change the received result. Check your supported route and use authorized device tests before launch. The preview does not approve content or verify consent, delivery, file eligibility or billing.
Select a draft below and copy it. On a keyboard, focus the text box, select all and copy. The boxes are read-only; make your edits in your campaign draft. Replace all bracketed fields and the store name.
Keep a “reply here” instruction only when replies reach a monitored team. Use the required sender and opt-out wording for your supported program; provider-controlled notices may not allow freeform changes.
Audience: Customers with an active order who agreed to order notifications.
Send timing: Once after the connected source confirms pickup-ready status. Confirm the event and its delay; a purchase-history sync is not a ready event.
Exclude: Canceled or already collected orders; duplicate ready events; suppressed numbers.
Audience: Customers waiting for a confirmed order.
Send timing: When a meaningful delay is confirmed; update again only if the status changes.
Exclude: Completed or canceled orders, stale delay estimates, suppressed numbers and customers already notified of the same change.
Audience: Customers who booked a consultation or service and agreed to reminders.
Send timing: At the reminder interval disclosed during booking.
Exclude: Canceled appointments, duplicate bookings and customers who withdrew permission.
Audience: Customers affected by a scheduled visit or active order; marketing subscribers only where the program permits this update.
Send timing: Once after confirming the new hours.
Exclude: Unaffected locations and customers already informed through the same text program.
Audience: Customers who completed a visit and have permission for this follow-up.
Send timing: After enough time to evaluate the visit; apply a repeat-request limit.
Exclude: Recent requests, open support cases and contacts without appropriate permission. Do not gate public-review invitations by a customer’s rating.
Audience: Rewards members who agreed to the relevant text program.
Send timing: Only after confirming the current balance, account match and permitted message purpose; a points balance is not marketing permission.
Exclude: Missing or stale balances, closed accounts and customers without the appropriate subscription.
Audience: Marketing subscribers with a verified profile birthday and permission for birthday messages.
Send timing: Once near the birthday, according to the chosen program schedule.
Exclude: Missing birthdays, duplicate records and anyone at the marketing frequency limit.
Audience: Marketing subscribers whose lapse window fits the store’s normal purchase cycle.
Send timing: After the lapse threshold; stop the flow when a new visit occurs.
Exclude: Recent buyers, open service cases, opted-out contacts and conflicting outreach. Recheck the latest purchase before a delayed step.
Audience: A customer whose withdrawal has been recorded and whose configured opt-out flow permits a confirmation.
Send timing: Use the provider’s configured response after suppression is recorded. If it already sends a confirmation, do not add a duplicate campaign.
Exclude: Promotions, requests to reconsider and additional follow-up. The confirmation must match the actual subscription scope and system state.
Use automation planning, order-alert workflows and the POS-to-texting connection checklist. Blackleaf texting is available separately from Blackleaf POS; confirm the data your supported connection actually supplies.
For an API integration, these writing drafts are not saved API templates. Follow the API send workflow and current operation reference to create and review a template, inspect its returned acceptance result, and retain a usable identifier. Use that identifier as templateId for a send in the same workspace and messaging environment. Editing this browser preview does not update a stored template; review changed wording or media and select the accepted template deliberately. The preview’s image-picker limits do not establish API media eligibility or production approval.
A link should lead to the exact account, order, appointment or permitted content described in the message. Review redirects and the final page on a phone. Do not hide a promotion behind a vague “account update” or imply that a generic menu is a personal order-status page.
If you adapt a draft for a permitted offer, confirm its price basis, eligible items, store, dates, time zone, exclusions, stock and redemption conditions. Do not say “reserved,” “back in stock” or “your balance” unless the underlying fact is current. An age gate is a separate control, not approval for the text or offer.
Keep the final message concise. Encoding, personalization, links and required footer text can change the segment count. Twilio’s technical character-limit reference explains why Unicode and long messages use different segment sizes; it is a technical reference, not permission to send cannabis traffic through Twilio. Review Blackleaf texting costs for your actual plan.
Choose one intended outcome for each draft: a completed pickup, rescheduled appointment, useful reply or qualifying return visit. Track failed sends, duplicates, opt-outs, wrong fields and support issues alongside that outcome.
A delivery status does not prove the customer read the text. An attributed purchase does not prove the message caused an extra sale. Use stated matching rules and equal observation windows; a suitable randomized holdout can help assess natural returns. Avoid withholding essential order or safety information for a marketing experiment.
For deeper diagnosis, use the delivery troubleshooting guide. A reach drop needs investigation of the actual error and route; rewriting copy alone may not resolve it.
It is a reusable message draft for a defined customer situation, such as an order update, appointment reminder or permitted follow-up. A usable template includes the audience, required event or data, timing and exclusions. The draft does not establish permission to send.
Yes. Select a draft, copy it, and replace the fictional store name and every bracketed field. Check the final personalized message, destination, sender, reply handling and segment count. If your provider requires a fixed notice or approved template, use that required format instead.
No. They are illustrative writing examples. Blackleaf requires explicit recipient consent and age confirmation before texting, with intended-recipient birthday selection in the message flow; never reveal the saved birthday. Separately review business eligibility, message purpose, content, destination, provider policy and the actual sending route. Neutral wording, an age gate or campaign registration does not override a prohibited use case.
An illustrative instruction is: “Reply STOP to opt out.” Use the wording required by your program and provider, and make sure the withdrawal actually updates suppression. Adding this sentence does not prove consent or make an otherwise prohibited message permissible.
State the actual outcome and subscription scope plainly, without an offer. For example: “You are unsubscribed from [Program Name]. No more texts will be sent for this subscription.” Use the configured opt-out flow after suppression is recorded; do not issue a duplicate confirmation campaign.
The actual purpose and content matter. A status update for an existing order differs from a message that adds a discount or encourages another purchase. Confirm applicable permission and provider support for the business and use case. An operational label does not create an exception to a provider prohibition.
Yes. A greeting, points reminder or invitation to return can serve a marketing purpose even without a stated offer. A stored birthday, loyalty membership or points balance is not proof of permission for that message.
Keep it as short as the customer’s task allows, with clear identity and one useful next step. Encoding, final names, links and required footer text affect the segment count. Preview the expanded message with your actual sending setup; a 160-character rule alone is not enough for every message or sender type.
No. Blackleaf texting is available separately from Blackleaf POS. Confirm the supported connector or authorized data method, customer match, available fields and update timing. A connector does not prove that every order or loyalty event is available.
AI can help draft variations using the context you provide, but a generated price, balance, stock claim or customer preference needs verification. Use known data, preserve required wording and review the final audience, message and destination before sending. A generated draft is not an approved campaign.
No. A delivery status is separate from a read, useful reply, pickup or purchase. Define the intended outcome and observation window. Attributed sales follow a reporting rule; a suitable holdout can help estimate how many customers would have returned without the message.
Bring Blackleaf the situation, current system and outcome you want to support. We can review the supported texting setup, audience and workflow before you launch.