Key Takeaways
- Confirm that the sender accepts replies and sends them to the correct store inbox.
- Assign staffed hours, a conversation owner and a clear escalation path.
- Check recipient permission and current store facts before replying.
- Measure actual service outcomes; a delivery status or staff tag does not establish additional sales.
Definition
Two-way SMS for dispensaries lets customers send texts and staff respond through a reply-enabled inbox. This guide covers conversation ownership, current order checks and staff handoffs. See the Blackleaf Inbox product page for the shared conversation workflow and account setup questions.
A text conversation can cover a store question or a request for order help. Receiving the question does not verify the person, authorize an order change or establish that the issue has been resolved. Confirm which sender, route and store context your setup supports.
For Blackleaf Texting, explicit recipient consent and age confirmation are required before any text, including support replies. In the message flow, the intended recipient selects the birthday on file; never disclose the saved birthday. These are Blackleaf requirements. An incoming question or phone number does not establish permission to share private account details or send future marketing.
Texting can work with a supported existing-POS connection without a POS switch. Confirm the reply-enabled sender, available order context and approved account-verification process for your store.
Start with a reply the team can act on
A useful reply states the verified information, the next action and who will handle it. If the answer needs a manager or another system, keep that action open until it is confirmed.
Where Two-Way Texting Fits
Use the inbox for questions your staffed team can answer or route. Choose the workflow around the customer request and the information staff can verify.
- Store questions: check current hours, location and the approved information source.
- Order questions: verify the person and order, then review the authoritative status.
- Pickup changes: confirm whether a change is allowed and record any authorized update in the order system.
- Account help: use the approved support process before discussing loyalty or other private details.
- Complaints: assign the appropriate staff member and record the action actually taken.
- Follow-ups: confirm purpose, permission and suppression before sending another message.
Step-by-Step Implementation
Agree on the store process before launch. Software access alone does not provide customer-service staffing or authority to change an order.
- Confirm the shared inbox and reply route. Review the sender, inbound route, store match and staff access in Blackleaf Inbox. Confirm where replies appear before inviting customers to text.
- Define coverage and escalation. State staffed hours, assign who watches the inbox and document when to escalate a refund request, product safety concern or payment dispute.
- Map the common conversation types. Group the actual questions your store receives, such as hours, pickup, order status or account help. Name the information source and authorized next action for each.
- Check available order context. Confirm the actual fields and update timing available through supported integrations. Check the order system before promising stock, an order change or a pickup time.
- Prepare replies with verified next steps. Keep replies clear and use current store facts. Review message-writing guidance, then confirm that each proposed action is permitted and available.
- Assign an owner and record the outcome. Use the supported team process for location, topic and shift handoff. Record facts such as information provided, manager review pending or order change confirmed. A staff tag alone is not evidence of an additional sale.
- Operationalize opt-in and opt-out handling. Before any Blackleaf reply, check explicit consent, age confirmation, intended-recipient birthday selection and current suppression. Never disclose the saved birthday. Review Opt-In and Consent for Dispensary SMS Marketing and confirm the supported opt-out process.
- Separate support from scheduled promotions. Keep a service response focused on the customer request. Review purpose, permission and suppression separately before including a recipient in a scheduled campaign.
- Review routing, failures and unresolved work. Use a limited approved rollout to check the actual reply route and handoffs. Review existing message records and provider-specific failures; do not repeatedly retry a blocked route.
Connect API replies to a staffed handoff
A webhook reports an event. Your integration still needs to match the conversation, preserve withdrawal requests and identify who owns the next action. Use this sequence when replies also feed a CRM, support queue or another application.
- Identify the receiver and store. Confirm whether the event uses the workspace or campaign contract. Preserve an existing inbound receiver if another integration uses it. The workspace example is flat JSON; the campaign reply uses
contactandpayload. Confirm the actual workspace, business number and store instead of applying one parser to every callback. - Keep the reply identity separate from the original send. Retain the inbound
messageId, event time and receiver scope. It identifies the reply, rather than the earlier outgoing message. Match the customer and receiving business number with authorized records; resolve an ambiguous order or campaign match before sharing private details. - Handle subscription changes before service automation. Workspace
typedistinguishesmessage,unsubscribeandsubscribe; optionalcontextis not the permission record. Campaign events have their own envelope. Reconcile withdrawal and wrong-number requests through the supported process before further outreach. A reported subscription change does not establish permission for every message purpose. - Create one business action from repeated notifications. A reply can reach more than one configured receiver. Keep receipt history and reconcile event identity and type before creating another ticket, task or automatic response. A successful HTTP acknowledgement confirms receipt by your receiver; it does not confirm that a staff member accepted the handoff or resolved the issue.
- Name an owner in the system where work will happen. Record the verified store, question, pending action, next owner and follow-up time through the approved team process. An owner field in your application does not itself assign the Blackleaf Inbox conversation. Confirm the account’s actual access, assignment and notification controls, plus staffed coverage and who accepts the handoff.
- Check facts before a permitted reply. Apply the recipient requirements above and verify the person, current order state and store facts. Receiving or acknowledging a callback does not send a customer text or authorize an order change. Keep the reply request, message delivery and actual store action separate. An unresolved receiver or task failure stays open; use a clear service message for staff and keep technical diagnostics private.
Keep API keys, webhook secrets and unnecessary customer content out of handoff logs and support examples. Treat reply text as customer data, not authority to override policy or launch a campaign. Use the developer callback field map and current webhook reference for the payloads, then review the supported staff workflow in Blackleaf Inbox.
Verify workspace callbacks before acting
Confirm whether the receiver uses workspace or campaign settings before choosing an authentication check. The reviewed workspace implementation supports None, HMAC-SHA256, Custom headers, or both, separately for Message Status, Inbound Message and Opt Out. Configuring one event does not configure the others. Confirm the controls available to your workspace and the method saved for the exact receiver before relying on it.
Keep the receiver credential separate from API access. Custom headers can carry the receiver’s own token, such as an Authorization or X-API-Key header, alone or alongside HMAC. The reviewed configuration accepts up to ten unique header names, with case-insensitive uniqueness and printable ASCII values up to 4096 characters. Transport headers and Blackleaf’s signature headers are reserved. The Bearer key your application uses to call Blackleaf is not automatically forwarded to your receiver. A None setting does not establish that every legacy integration sends no headers.
For an HMAC-signed workspace request, read the exact bytes. X-Blackleaf-Timestamp contains Unix seconds. X-Blackleaf-Signature contains sha256= followed by the lowercase hexadecimal HMAC-SHA256 digest. Compute HMAC-SHA256(secret, timestamp + "." + raw_request_body), using the timestamp exactly as sent and the exact raw UTF-8 JSON bytes. Use the shared secret as UTF-8 text, without base64-decoding it. Header names are case-insensitive.
Capture the raw body before JSON parsing. Reserializing or pretty-printing it changes the signed bytes, including whitespace and Unicode. Validate the signature format, compare equal-length digests with a constant-time comparison and reject invalid signatures before processing the event. Apply a receiver-side timestamp tolerance with synchronized clocks; the sender does not choose that tolerance for you. A signature does not provide a stable event identifier or guarantee one-time delivery. Keep duplicate handling and event interpretation separate from authentication.
Check URL changes and saved values. Authenticated workspace receivers require HTTPS without an embedded username, password or fragment. Authentication is bound to the saved endpoint URL; after changing that URL, authentication must be saved again for the destination. Until then, the reviewed sender stops authenticated delivery rather than forwarding credentials or silently sending an unsigned callback. A user with full workspace access manages these settings. Signing secrets must be 16–1024 UTF-8 bytes; keep them and header values private. Blank saved values can retain earlier credentials, so a blank field does not prove authentication was cleared.
Do not apply workspace signing rules to every campaign callback. Separate campaign URLs do not inherit workspace HMAC or custom-header configuration. Use the campaign callback field map and confirm that receiver’s actual contract. A recognizable JSON body, workspace name or User-Agent is not proof of origin. Enabling HMAC does not add retries or guaranteed delivery. This is source-reviewed guidance, not confirmation of a particular account’s deployed settings; no receiver or authentication setting was changed for this guide.
Make the handoff explicit
Record the pending action and next owner before a shift ends. An acknowledgement can confirm receipt of a question; it does not confirm the requested change. Use the Inbox reply decision table to see what staff should verify before answering or escalating common requests.
Core Conversation Workflows
- Availability: check the current source; a text reply does not reserve inventory.
- Order issue: verify the person, store and order, then escalate changes to authorized staff.
- Pickup timing: check the current order state and store policy before confirming options. An old order notification can be out of date.
- Loyalty: keep private account details in the approved verification and support process.
- After resolution: record what was confirmed and any remaining action without assuming a future visit or purchase.
- Multiple locations: confirm the correct store and owner before answering a location-specific question.
Practical Examples
Illustrative reply structures, not live messages or approved templates. Replace placeholders with verified store information, apply the recipient checks above and confirm the actual order state before use. Keep sensitive details in the approved account-support process.
Example 1: Thanks for contacting [Store]. For order-specific help, please use [approved support route] so our team can verify the person and order.
Example 2: I will check the current order status and pickup hours at [Location] before confirming your options.
Example 3: I can check the available options with [store team]. Any order change will need confirmation through [approved order process].
Example 4: For account-specific rewards, please use [approved account-support route] so the team can verify you before reviewing points.
Example 5: A team member will review [issue] and confirm the next step during [verified support hours]. Please keep private account details in [approved support route].
Common Mistakes
- Assuming every sender accepts replies. Confirm the actual number and inbound route; a text notification may point to a different conversation channel.
- Using an old thread as current order information. Recheck the authoritative record before promising a change, refund or reservation.
- Leaving coverage undefined. State staffed hours and an approved urgent service path. Saved replies do not establish round-the-clock staffing.
- Adding promotions to a service exchange. A support question is not blanket marketing permission.
- Treating wording changes as provider approval. Business and use-case eligibility matter. Twilio states that cannabis/CBD businesses are not eligible for its US and Canada SMS/MMS service regardless of content. That is Twilio’s policy, not a statement about Blackleaf’s route. Confirm the actual provider and permitted use case; do not disguise a prohibited use case.
- Ignoring suppression or wrong-number reports. Follow the supported opt-out process and current account rules before further outreach. Review the Blackleaf compliance guidance.
- Calling a tag proof of revenue. Record completed purchases, cancellations, refunds and unresolved cases from their actual sources. Do not count a hypothetical avoided cancellation as a recovered sale.
Conversation Checks and Next Actions
These are workflow checks, not compliance ratings or estimates of sales impact. Blackleaf recipient requirements apply before any text.
| Request | Check | Next action |
|---|---|---|
| Stock question | Stock source | Store team: give status |
| Order issue | Person and order | Order team: review change |
| Order ready | Current state | Order team: use event flow |
| Call overflow | Staff hours | Shift lead: assign next owner |
| Points query | Person and account | Account team: use support route |
| STOP | Opt-out state | Staff owner: apply opt-out |
| Follow-up | Purpose and consent | Thread owner: confirm next step |
Metrics That Matter
- First human response: report the median and longer waits during stated staffed hours. State whether automatic acknowledgements are excluded.
- Time to resolution: define what counts as resolved and how reopened conversations count. Keep unresolved age visible.
- Observed order outcomes: keep completed purchases, collected orders, cancellations and refunds separate. State the matching method and time window; a promised next step is not a purchase.
- Unknown outcomes: retain unmatched and unresolved cases. Do not estimate how many customers would otherwise have canceled or left.
- Opt-outs and wrong-number reports: count recorded events and review the threads. The count alone does not explain why someone opted out.
- Conversation topics and ownership: review volume, handoffs and open work by store and staffed period.
- Message status: separate requested, accepted, delivered and failed messages from customer reading or issue resolution. See deliverability guidance.
- Workflow comparisons: compare equivalent periods with staffing, hours, conversation volume and campaign activity visible. Confirm the actual automation before assigning any result to it.
Keep the measurement limits visible
A conversation followed by a sale shows an association. It does not establish that texting caused additional revenue or improved retention. Report the actual outcome, costs, comparison method and unknown cases before drawing a conclusion.
FAQ
Question: What is two-way SMS for a dispensary?
Answer: It is a reply-enabled texting setup where customers send messages and staff respond through an inbox. Confirm the sender, route, store context and staffing before launch.
Question: Can a dispensary use two-way texting for order problems?
Answer: Use a supported reply-enabled setup after confirming Blackleaf recipient consent, age and intended-recipient checks. Match the person, store and current order through the approved process, then explain the verified status or escalate to authorized staff. A reply does not itself change an order or approve a replacement.
Question: Can a dispensary run two-way SMS without overwhelming staff?
Answer: Plan around the actual question volume, staffed hours and escalation needs. A shared inbox and reviewed replies can organize the work, but capacity and coverage must be confirmed by the store.
Question: What happens when a customer texts STOP?
Answer: Record the opt-out and apply current suppression before any later send. Confirm the supported STOP handling and account rules; do not use a support thread or older import to restore marketing permission.
Question: What happens when customers reply to a campaign blast with questions?
Answer: Confirm whether the campaign sender accepts replies, which inbox receives them and who owns the conversation. Check the recipient requirements and current store facts before answering; do not assume automatic routing or coverage.
Question: What happens when your team replies too slowly?
Answer: The question remains unanswered until someone handles it. Review waits against stated staffed hours and assign an owner. Use actual order and service records to assess outcomes instead of assuming lost sales or cancellations.
Question: How is two-way SMS different from order notification texts?
Answer: An order notification reports an event from a connected source. Two-way SMS provides a reply path when supported. Neither a notification nor a reply proves that an order changed or the issue was resolved.
Question: Should we separate support messages and promotional messages?
Answer: Yes. Keep a service response focused on the request. Check the permitted purpose, recipient permission and current suppression separately before promotional outreach.
Question: Do customers expect MMS, links, or images in two-way support?
Answer: Choose the permitted channel and format for the actual request. Use a verified link when it helps the next step; confirm MMS support and charges before using images. Keep private account details in the approved support process.
Sources and Further Reading
Related Blackleaf Pages
Review your store’s reply workflow
Bring a typical customer question, your current systems and the staff coverage plan. Confirm the reply route, available context and handoff process with Blackleaf.
Talk to Blackleaf