Shared Text Inbox for Dispensaries
A two-way dispensary SMS inbox brings customer replies and conversation history into a shared workspace so staff can respond with context. Blackleaf helps your team handle questions and continue conversations alongside its texting campaigns. Confirm the reply-enabled sender and routing for your account before inviting customers to text back.
A useful reply starts with what the customer needs now: store hours, a pickup question, an offer clarification or a problem that needs a person. Keep the answer accurate and the next action clear. A reply is not proof of marketing permission, a completed order or an additional sale.
Read the conversation before making a promise.
Review the latest customer question and earlier messages, identify the correct store, and check the current facts. Blackleaf helps draft responses; your team stays responsible for the answer and any action it promises. Suggested wording is not evidence of order readiness or available stock.
- Sam Rivera · Customer
Can I pick up my order after work?
- Store team · First response
I’ll check the pickup window and current order status before confirming.
- Store team · After verification
Your order is still ready at our North store. Pickup is available until 8 tonight. Please follow the pickup instructions in your order details.
Assumes staff verified the person, store, current order and hours.
Check the latest order in the authoritative system. A previous notification may be stale after a cancellation, collection or change. For event-based updates, review order alerts; for repeatable wording, use the message-template guide.
Make the handoff as clear as the answer.
A shared inbox gives staff a common conversation to review. Preventing overlapping replies still needs an agreed team process. Confirm the actual access, assignment, notification and status controls in your account rather than assuming automatic routing or collision prevention.
- Read and identify. Check the latest thread, sender, store and relevant customer record. Resolve an ambiguous match before sharing personal order or account details.
- Choose an owner. Agree who handles the question. Before another person takes over, record what is pending in the supported team process.
- Check and respond. Verify hours, offer terms, stock or order state using the appropriate source. Review assisted copy before using the permitted reply workflow.
- Confirm the next action. Separate a sent reply from an actual store action. Escalate refunds, changes and exceptions to the person authorized to decide.
- Hand over or close. Name the next owner and follow-up time when work remains. Record the actual outcome; do not call the issue resolved just because a reply was delivered.
At shift change, pass on the customer’s question, verified facts, latest answer, unresolved action and next owner. Define staffed hours and an urgent service path. Do not advertise replies as monitored around the clock unless your operation provides that coverage.
Different replies need different decisions.
This is a staff planning checklist, not a claim that every check or action is automated. On smaller screens, focus the table and use the arrow keys to scroll.
| Customer message | Check first | Useful next step |
|---|---|---|
| “What time do you close?” | Correct location, current date and special hours. | Give the verified hours and location. Avoid an unnecessary promotion. |
| “Is my pickup ready?” | Identity, order/store match and latest authoritative readiness state. | Confirm the actual status and pickup path. Do not invent an ETA. |
| “Does this offer apply?” | Dates, location, eligibility, exclusions and approved terms. | Explain the real terms or ask the authorized manager to review. |
| “Something is wrong with my order.” | Approved verification process, order facts and who may resolve it. | Escalate through the staffed service path. Do not promise an unapproved refund or replacement. |
| “Stop texting” or “Wrong number” | Current suppression and the supported opt-out/reporting process. | Honor the request through that process. Hold further outreach; do not keep texting to test the number. |
Keep sensitive details out of ordinary texts when they are not needed. Use an approved verification or service destination for private account questions. A phone number alone is not enough to decide who may see order or loyalty information.
Keep customer service and the next campaign separate.
A question about an existing order does not establish permission for future promotions. Check documented permission, current suppression, the message purpose and the permitted business, content and route. An opt-out, wrong-number report or ambiguous identity needs attention before more outreach.
System safeguards support the team; they do not guarantee that every individual reply is permitted or that every provider supports the business. Neutral wording, an age gate or a “service” label does not override a provider prohibition. Review opt-in records, messaging requirements and delivery evidence and route restrictions.
Keep scheduled campaigns and automations in view when a customer has an unresolved issue. Define who can pause affected outreach and how the supported account implements exclusions. Do not assume a staff conversation automatically pauses every campaign.
Use assistance with facts your team can check.
AI can help prepare wording, but the answer still needs a reliable source and a responsible operator. Confirm the exact assisted or automatic workflow before enabling it. This page does not establish an always-on agent that reads every POS, changes orders, reserves stock or issues refunds.
For available campaign preparation and connected AI app workflows, explore AI dispensary text marketing. Connected Blackleaf POS AI agents are in production in California and are separate from those texting tools. More states are rolling out soon.
Blackleaf texting is available separately; adopting Blackleaf POS is not required. If a reply depends on purchase history, inventory or an order, check the supported source fields, location and latest update through integrations and the POS-to-texting checklist. A shared inbox does not by itself supply live POS data.
Test the conversation from both ends.
Use authorized test recipients and a permitted sending setup. Start with one location and the staff who will actually answer.
- Send a test through the actual reply-enabled number. Confirm where the inbound reply appears and which staff can see it.
- Check the correct person, store, conversation history and current message status. Reconcile an uncertain send before retrying.
- Rehearse a shift handoff, an unresolved issue and an after-hours question. Confirm notifications and any acknowledgement behavior actually configured.
- Test supported opt-out handling and exclusions. Do not override suppression to complete the test or finish a promotion.
- Confirm billing for inbound and outbound usage, staff/location access and any AI or managed service. Review texting costs and current plans.
For a failed reply, inspect the existing message record and provider-specific explanation. Use an approved fallback when appropriate instead of repeatedly attempting a blocked route. The troubleshooting guide explains the investigation.
Measure whether the customer got useful help.
Track conversations awaiting a response, first human response time during stated staffed hours, unresolved age, repeat contacts and the actual service outcome. State whether automatic acknowledgements are excluded and how reopened conversations count.
Keep message requests and delivery states separate from customer reading, issue resolution, pickup and completed purchase. A conversation followed by a sale is not proof of additional revenue caused by the inbox. Review comparable periods with staffing, store hours and conversation volume visible.
If you want help operating campaigns, review managed texting and confirm whether reply handling is included. Campaign management alone is not a promise of store customer-service coverage.
Inbox questions, answered.
What is a two-way dispensary SMS inbox?
It is a shared workspace for receiving customer texts, reviewing conversation history and sending permitted replies. It helps staff continue a conversation rather than treating every customer response as a new campaign. Confirm the reply-enabled sender and account setup.
Can customers reply to every campaign number?
Do not assume every sender or route accepts replies or returns them to the same inbox. Test the actual number, inbound routing, store match and staff access before telling customers to reply.
Does a customer reply give us permission for future marketing?
Do not treat a service question, purchase, loyalty record or saved phone number as blanket marketing permission. Check the actual permission and suppression records and the permitted purpose, content and route before future outreach.
How should staff answer a pickup question?
Match the person, store and order through the approved process, then check the authoritative order state and current pickup instructions. An incoming text or an old ready notification does not prove the order is still available. Do not promise a reservation, changed order or refund that has not been authorized.
How do we avoid duplicate staff replies?
Agree on who handles each conversation and how shifts hand work over. Check the latest thread before replying, record the pending action in the supported team process and name the next owner. Confirm actual assignment, access and notification controls in the account; do not assume automatic collision prevention.
Will AI answer every customer automatically?
No universal automatic-reply service is established here. Blackleaf helps prepare responses, and your team should review current store facts, identity, permission and the action being promised. Confirm the exact assisted or automatic workflow before enabling it.
Does delivered mean the issue is resolved?
No. A delivery status concerns the message, not whether the customer read it, collected an order, accepted an answer or had an issue resolved. Record the actual service outcome separately and retain unknown outcomes.
What if a reply fails or its status is uncertain?
Review the existing message record, status and provider-specific explanation before retrying. Use an approved service fallback when appropriate. Do not repeatedly send through a blocked route or assume that a timeout means nothing was sent.
What happens after an opt-out or wrong-number reply?
Follow the supported opt-out process and check current suppression before further outreach. Escalate an unrecognized opt-out request or wrong-number report through the store’s approved process. Do not override suppression to finish a promotion or keep texting to test the number.
Do we need to replace our POS?
No Blackleaf POS switch is required for supported existing-system texting. Confirm the actual customer, order or purchase fields, update timing and allowed use case. A shared conversation does not by itself establish live inventory, order changes or a POS integration.
Does an inbox include round-the-clock support?
An inbox is software, not a staffing promise. Define staffed hours, response expectations, shift handoffs and an urgent service path. Confirm any automatic acknowledgement or managed reply service separately.
How much does two-way texting cost?
Confirm inbox access, staff or location limits, inbound and outbound SMS segments, MMS, number or registration charges and any AI or managed-service fees in the current quote. Do not assume incoming replies or assisted responses are free.
Bring a real question to the demo.
Show Blackleaf the customer situation, your store locations, current systems and who will answer. Review the supported reply route, history, staff workflow and launch checks together.