Written by DROPS.ST.
Ask for the information needed to understand the enquiry and provide its approved next step. A cannabis-shop customer asking what a package contains does not automatically need to submit an identity-document bundle or a detailed personal profile.
DROPS gives your team product, unit and package context, with customer-linked orders when an authorized order check is needed. Use those records to answer the actual question rather than recreating a broad customer dossier in a contact form.
Define the question the form serves
Separate a general information enquiry, a specific order question and a sensitive request requiring another process. They may need different information and response owners.
For each field, ask what decision would be impossible without it. If the team cannot explain that need, review the request rather than declaring every input mandatory.
OPC guidance recommends collecting personal information needed for an identified purpose. Apply that principle with the requirements relevant to the business. It does not remove required age, identity, licence, payment or other transaction checks. OPC collection guidance.
Use a purpose-to-field worksheet
This original worksheet is a design aid, not a claimed native DROPS form builder.
| Proposed information | Purpose to establish | Owner decision |
|---|---|---|
| Enquiry type | Find the person or process that can answer | Use categories the team understands |
| Product reference | Identify the item or package in question | Accept enough information to locate it |
| Order reference | Locate a specific authorized support case | Do not treat the reference alone as disclosure authority |
| Reply route | Provide the approved response | Explain why it is needed and how it is used |
| Free-text detail | Identify the unresolved question | Ask for relevant facts, not a personal story |
| Attachment | Supply evidence genuinely required for the task | Use the appropriate secure process if necessary |
Record required, optional or redirected information for the actual supported form. Check its required inputs and behavior before changing them.
For a trade-show business enquiry, retain the relevant origin and purpose rather than collecting identity documents by default. Attendance alone does not establish permission for later promotional contact; justify any additional checks separately.
For an early B2B discovery call, supplier contact or software application, distinguish the initial business question from later required trade evidence. Ask who receives private documents and how approved records are protected. A supplier enquiry does not establish a native supplier CRM or remove required checks.
Before account creation, explain required versus optional information, applicable company checks and the actual support route. Keep empty hardware, cannabis-filled items and nicotine products separate when reviewing the required business evidence; do not infer approval from another category.
Keep sensitive requests out of routine intake
A general form should explain where a sensitive request belongs. Do not invite full payment credentials, passwords or unrelated health information simply because an attachment button is available.
If the task needs additional evidence, the responsible person should identify the missing fact and use an approved submission route. Asking for everything in advance is not a substitute for understanding the enquiry.
Assign response ownership too. A lean form still fails the customer if the submission reaches an unmonitored destination. The support priorities guide helps connect receipt to an owned next action.
Hypothetical example: an unclear package
A fictional customer asks whether a displayed quantity refers to a package or an individual unit. Staff need enough item information to find the product and an approved way to answer. They do not need the customer’s unrelated purchase history to explain the unit.
If the question instead concerns an existing order, the worker follows the appropriate authority check before disclosing its details. The original form should not assume that every visitor is making that request.
This hypothetical example establishes neither a required-field list nor a native identity-verification feature.
Test the full receipt and response path
Rehearse with fictional details in an approved environment or use written cards if safe submission is unavailable. Check the customer’s understanding of required inputs, the receiving owner and the response process.
Confirm whether free text or attachments expose information to staff beyond the intended purpose. Check what is retained and which copied records exist under the actual policy. Do not infer automatic deletion, field masking or secure upload handling from the form’s appearance.
Use the service FAQ guide for general answers and the privacy-request guide for requests needing that separate decision process.
Make the enquiry useful to the next person
DROPS connects product facts and customer-linked order context. Pair that foundation with purposeful intake so the receiving worker can identify the question, necessary evidence and next step without collecting a second version of the customer’s life.
Explore DROPS.ST and the shop demos. Bring one general question and one fictional order enquiry, then justify each requested field before choosing the form you will use.