Cannabis Operations
Building an Evidence Log for Dispensary Complaints

Powered by StealthAgents
Cannabis Operations

Published August 14, 2026.
A useful customer complaints record begins with the event, not the form. Write what the person actually saw, heard, measured, or received. Then identify the decision that cannot safely be guessed. In customer complaints, that distinction matters because an apology is logged without preserving the transaction facts that can resolve the complaint. The first note should be short enough to make during the shift and precise enough for a different reviewer to retrace.
75% of customers in HubSpot’s 2024 cross-industry survey said they expected help within five minutes of contacting an agent [1]. That is useful context for Dispensary Customer Service Benchmarks 2026, but it is not a universal dispensary target. Cannabis retail combines ordinary service expectations with identity checks, product boundaries, accessibility, privacy, inventory accuracy, and jurisdiction-specific rules, so a defensible scorecard must measure both speed and correctness. ## The direct benchmark answer There is no single credible national dispensary customer-service benchmark series covering in-store, phone, text, email, web, pickup, and delivery contacts. The best 2026 answer is a layered benchmark: use dated cross-industry data as external context, then calculate store-specific performance from clearly defined events. External studies show the pressure for prompt service. Talkdesk reported that callers spent an average of 3.24 minutes waiting for an agent across 390 million calls in its 2024 global contact-center benchmark data [2]. HubSpot reported that 75% of surveyed customers expected help within five minutes, while 48% expected specialized treatment for being a good customer [1]. Those figures have different populations and methods. They should not be averaged, converted into a promise, or treated as cannabis compliance standards. A useful dispensary scorecard separates seven measures, an editorial recommendation: queue wait, first meaningful response, complete resolution, repeat contact, escalation, accuracy, and accessibility. Each tells a different operational story, and each needs its own denominator. ## Screenshot-ready benchmark scorecard | Measure | Published value or local formula | Population and meaning | Source or label | | --- | ---: | --- | --- | | Expected help within five minutes | 75% | Cross-industry surveyed customers, expectation rather than observed performance | HubSpot, 2024 [1] | | Expected specialized treatment | 48% | Same survey, customers expecting recognition for loyalty | HubSpot, 2024 [1] | | Average wait for an agent | 3.24 minutes | 390 million calls in vendor benchmark data | Talkdesk, 2024 [2] | | Retail trade quits rate | 2.7% | US retail trade, seasonally adjusted, May 2024; workforce context, not dispensary-only | BLS, 2024 [3] | | Queue wait | Median of service-start time minus arrival time | Local calculation; report channel and period | Editorial calculation | | First-contact resolution | Contacts resolved without another customer contact divided by eligible contacts | Local calculation; publish exclusions | Editorial calculation | | Accessible completion | Tested priority journeys completed with defined assistive methods divided by journeys tested | Local calculation; not a legal conformance claim | Editorial calculation | The 2.7% quits rate is included because staffing stability can affect service continuity, not because it predicts any individual dispensary’s turnover [3]. The three local formulas are calculation definitions, not recommended thresholds. ## Measure the in-store journey in stages A single “wait time” hides distinct delays. Capture arrival, check-in completion, eligibility or identity verification completion, service start, checkout start, and transaction completion only when the system can record each event lawfully and consistently. Report the median before the mean. A small number of long waits can pull the mean upward, while the median describes the middle observed contact. If management needs the tail, report a named percentile and label it as a local calculation rather than inventing an industry norm. Separate walk-ins from scheduled pickup. A pickup customer may still require verification, product confirmation, payment, and a legally required handoff. Combining both paths can make improvements in one channel conceal delays in the other. Do not optimize speed at the expense of required controls. The Virginia pharmaceutical processor regulations govern the state’s medical cannabis dispensing framework, including dispensing and record requirements [4]. The accountable licensee must determine which controls apply to each transaction. ## Phone, message, and web response benchmarks “First response” should mean a meaningful human or approved automated answer, not a delivery receipt. A message that says only “we received your request” can be tracked as acknowledgment, but it should not stop the substantive-response clock. Define business hours and pauses before measuring. If a customer writes outside operating hours, report both elapsed time and staffed time or clearly choose one. Never remove difficult cases from the denominator merely because another team handled them. The Federal Communications Commission regulates unwanted calls and texts, and its consumer guidance explains consent and opt-out concerns [5]. A fast promotional text program is not good service if its consent records or unsubscribe process are weak. Email and chat logs can contain health, identity, or purchase information. NIST’s Privacy Framework organizes privacy risk around identifying, governing, controlling, communicating, and protecting data processing [6]. Collect only what the service question requires, restrict access, and set a documented retention rule. ## Resolution, accuracy, and escalation Resolution time starts when the customer presents a defined issue and stops only at a defined outcome. “Transferred,” “ticket closed,” and “customer’s question answered” are not equivalent outcomes. Create reason codes that reflect actual dispensary work: product availability, pickup status, return policy, account access, loyalty, accessibility, payment exception, adverse-event routing, and regulatory question. The categories are an editorial recommendation and should be adapted to the operation. Accuracy review should examine the approved source used, not only whether the customer was satisfied. FDA states that it has not approved cannabis itself for treating any disease or condition, although it has approved specific cannabis-derived and cannabis-related drug products [7]. Staff scripts must avoid turning retail assistance into unsupported medical claims. Route clinical, legal, privacy, security, and regulator-facing issues to authorized owners. The support team can collect facts and preserve the interaction record, but escalation closure should name the person who accepted responsibility. A repeat contact is not automatically failure. Customers may add a new question or choose another channel. Count repeats only when they concern the same reason, customer or order identifier, and defined time window. ## Complaint handling as a benchmark Complaint volume alone is not a quality rate. It rises with transaction volume, channel availability, and better reporting access. Use “complaints per completed eligible transactions” only when both counts cover the same period and population, and label the result as a local calculation. Track substantiated and unsubstantiated outcomes separately without treating “unsubstantiated” as frivolous. Missing evidence, conflicting records, or an issue outside the review scope can all prevent substantiation. FTC advertising guidance requires claims to be truthful, not misleading, and supported when necessary [8]. Complaints about price displays, product descriptions, promotions, or endorsements should therefore preserve the exact message the customer saw and the date it appeared. For safety-related product complaints, preserve lot, product, purchase date, symptoms as volunteered, and routing evidence without providing a diagnosis. FDA’s MedWatch program describes channels for reporting serious problems with regulated products, though applicability depends on the product and event [9]. ## Accessibility is part of service quality The Department of Justice explains that businesses open to the public generally fall under ADA Title III and must communicate effectively with people with disabilities [10]. Digital service also matters because menus, pickup flows, contact forms, and loyalty accounts can become essential parts of the customer journey. WCAG 2.2 contains 86 success criteria across conformance levels A, AA, and AAA [11]. That count is a specification fact, not a statement that every criterion applies to every page or that automated testing can establish legal compliance. Measure successful completion of priority journeys with keyboard-only operation, screen readers, zoom, captions where relevant, and clear form errors. Keep automated scan results and human task results separate because tools can identify only some accessibility barriers. Read the sibling dispensary digital accessibility data guide for criterion-level evidence. Service teams needing documented front-of-house queue and communication support can also review our front-of-house dispensary service. ## Building a local 2026 baseline Choose a stable observation period that includes ordinary operating conditions. Record store, channel, staffed hours, contact reason, arrival or receipt time, first meaningful response, resolution time, outcome, escalation owner, and any exclusion reason. Freeze definitions before looking at results. If “resolved” changes from ticket closure to customer-confirmed completion, start a new series and annotate the break. Calculate rates from eligible records only, but publish exclusions and missing timestamps. A missing time is not zero minutes.
Separate containment from investigation. Containment protects people, product, privacy, money, or a promised service while facts are still being assembled. Investigation explains the cause and decides whether the routine needs changing. For this topic, the first response may be a hold, a callback, a second count, a corrected notice, a locked cabinet, or a facilities work order. Record that temporary measure separately from the final conclusion. For training, ask the team to explain customer complaints in plain language and then demonstrate one exception. Listen for whether they can distinguish an observation from an assumption and an approval from an acknowledgement. Coach the missing step with a concrete example. People remember a decision boundary better than a slogan, especially when the work involves customers, service staff, managers, and the quality reviewer. Update the instruction only after observing where the handoff actually breaks.
Use the current primary guidance for the jurisdiction and activity: Federal Trade Commission complaint-handling guidance and Consumer Financial Protection Bureau complaint resources. Check the source directly when a rule, safety decision, or customer communication depends on it.