Written by DROPS.ST.
After a cannabis trade event, record why a business contact was made, what follow-up was requested and who will handle it. Keep those facts separate from permission for a wider campaign. A list of names without context leaves the next employee guessing what the business agreed to do.
DROPS gives the follow-up a useful product foundation: item references, units, stock and optional wholesale packages and tiers explain what a commercial question concerns. Customer-linked orders provide operating context when an actual order exists. Use those records without assuming an event attendee has become an approved buyer.
The same record discipline can help nicotine-vape businesses. Their product, promotion and sales requirements need separate review; a cannabis event example does not approve a nicotine-vape route.
Capture the request while its meaning is clear
Write the business question and requested next action rather than an account of everything discussed. “Asked for the current package definition” is more useful than “interested lead.”
Identify the meeting source and date, the business role stated and any limitations attached to the contact route. Do not infer purchasing authority, personal preferences or permission from a badge, job title or scanned list alone.
Keep required business checks for their proper stage. Minimizing an initial note does not remove licensing, age, identity or other obligations that apply later.
Keep a contact-provenance card
Use this original card in the business’s approved process. It is not a native DROPS event-importer or consent feature.
| Card entry | What to record | Next-action check |
|---|---|---|
| Meeting source | Event or conversation and date | Can the contact’s origin be explained? |
| Business context | Stated organization, role and relevant need | Is the question understood? |
| Requested action | Specific information or agreed review | Is it narrower than a general campaign? |
| Contact route | Provided route and stated restrictions | Can the proposed use be justified? |
| Permission evidence | Actual basis and scope reviewed for the message | Are assumptions visibly unresolved? |
| Receiving owner | Named person accepting the task | Who prepares and approves the response? |
| Review and outcome | Completion, open question or approved disposition | What remains necessary to retain? |
Keep unnecessary identity documents and personal narratives out of the card. The OPC’s PIPEDA collection guidance ties collection to an identified need. Apply it within the privacy requirements governing your business. OPC limiting-collection guidance.
Review the proposed message separately
The CRTC explains that a business card may support implied consent under specific conditions, including relevance to the recipient’s business role and no stated restriction. It also places the burden of proving consent on the sender. A business-to-business message is not universally exempt. CRTC CASL frequently asked questions.
Check the actual message purpose and applicable consent or exemption conditions, identification and unsubscribe requirements. Do not send a “permission confirmation” automatically without considering the requirements for that message itself.
Cannabis promotion needs its own review alongside messaging rules. Health Canada’s guidance includes intra-industry circumstances and restrictions; “trade event” is not blanket permission for every recipient or message. Health Canada cannabis promotion guidance.
Hypothetical example: a package question, not a campaign signup
At a fictional event, a retailer asks for clarification of a named package. Staff record that narrow question and the contact route supplied, then pass it to the catalogue owner for factual review.
The receiving employee checks the current unit and package definition, and the responsible person reviews whether the proposed reply may use that route. Nobody adds the contact to a general promotional list merely because the meeting happened.
This hypothetical record does not establish consent, buyer eligibility or a native follow-up workflow.
Give the task an accepted receiver
The receiver needs the question, checked source, unresolved conditions and approved next step. Use the shift-handover guide when responsibility moves between people.
Keep preparing an answer separate from applying broad shop edits or approving commercial terms. DROPS order actions have separate controls; catalogue editing also includes customer-account and wallet changes. A contact-coordination task does not justify every power.
Turn meeting context into useful shop work
Choose DROPS when event questions need clear catalogue references and customer-linked order context rather than disconnected product copies. Keep contact provenance and message approval in your accountable process.
Explore DROPS.ST and the shop demos. Bring a fictional business question, inspect its package meaning and identify the permitted next action before treating the contact as another campaign audience.