Written by DROPS.ST.
Prioritize cannabis-shop support requests using the actual task at risk, the commitment already made and the person authorized to decide. Do not let the loudest message or most familiar contact become the default queue rule.
DROPS connects products, stock, Customer Accounts and order items. That context helps staff distinguish a blocked order question from an information request before assigning the next action. Use the shared records as evidence for triage, with a responsible owner for the queue rather than an assumed automatic ranking tool.
Separate receipt from a promised answer
A received message establishes that somebody contacted the business. It does not establish that the team has verified the facts or accepted the requested outcome.
Record the question in operational terms: which decision does the requester need, what is currently blocked and what has the shop already promised? Keep necessary references in the approved support process rather than copying customer details into unrelated lists.
Apply the card to staff-originated operating issues too, and return the decision to the reporter. Formal personnel complaints need their separate responsible process. For product enquiries, identify the actual store or team and approved information source, then confirm someone accepts the route. A forwarded or abandoned enquiry is not a completed handoff.
Give each request an owner and next review point. A higher-priority item can move ahead without leaving the remaining items unacknowledged or forgotten.
Use a short priority card
Apply the same questions to every request. This original card is an owner-managed aid, not a native DROPS queue feature.
| Priority question | Evidence to record | Triage decision |
|---|---|---|
| What task is affected? | Order, information or service decision | Identify the actual work |
| What is the impact? | Confirmed block or consequence | Avoid ranking from assumptions |
| What commitment exists? | Approved next step or timing | Recognize an obligation already accepted |
| Who can decide? | Responsible person and action authority | Route beyond the current worker when needed |
| What is missing? | Specific unanswered fact | Request it instead of guessing |
| What happens next? | Owner, permitted action and review point | Keep the request moving |
Use plain priority labels your team can explain. A sensitive privacy or safety concern should go to the responsible process, not compete with ordinary commercial requests solely by revenue or customer size.
Rank work against the capacity you have
Distinguish a verified blocker, a time-bound decision, an ordinary clarification and an improvement suggestion. Define those categories for your business; they are not universal response deadlines.
During a call or inbox surge, assign available coverage and preserve sensitive escalation; no native shared inbox, call routing or response deadline is assumed. Consider the staff available and the authority required. Several quick questions may be answerable from approved information, while one exception needs an owner who is unavailable. Record that dependency instead of repeatedly reopening the same investigation.
GOV.UK’s user-support planning guidance considers enquiry types, channels, staffing and actual demand. Use those practical planning questions without importing its government-service rules or example targets into your shop. GOV.UK user-support guidance.
Hypothetical example: two requests, different consequences
A retailer asks for clarification needed to complete an agreed order decision. Another sends a suggestion for future menu wording. The first request has a confirmed current consequence; the second can be recorded for planned review.
The queue owner checks the order context, assigns the authorized decision-maker and gives both requests a next step. If the supposedly urgent request turns out not to block anything, its priority can be revised using the same evidence.
This hypothetical example is not measured support performance or a customer case study.
Keep the reply separate from action authority
DROPS has separate order controls for actions such as changing status, cancellation and refunds. The worker coordinating the request may not be the person authorized to act.
A support duty also does not justify broad catalogue editing, which includes customer-account edits and wallet adjustments. Keep the action with the appropriate person and use the staff permissions guide to review that scope.
Where another provider must investigate, the vendor escalation guide helps make the next handoff explicit.
Review the backlog for repeated problems
Check unresolved items, missed update commitments and recurring reasons for contact. A repeated question may need a better approved answer; a repeated exception may need an operating decision. Do not infer a cause solely from message counts.
DROPS gives your team connected shop facts for that review. Pair them with consistent triage and named next actions so limited support capacity is directed by the work that needs resolving.
Explore DROPS.ST and the shop demos. Bring two fictional competing requests and demonstrate which evidence changes their priority and who owns the next step.