What an authority tends to ask for first, and how to answer without panic

An authority enquiry can feel alarming, but it usually follows a predictable pattern. The authority first wants to identify the product precisely: which wax melt set, which fragrance, which batch, and which seller. That identification step matters because a vague answer, such as sending documents for a different fragrance or a different batch, wastes time and creates confusion about which product is actually under discussion.

The seller should therefore prepare an identification pack before anything else: product name, variant, batch or production details in general terms, photographs, and a short description of the melt, its wax, its fragrance, and its container. That pack, sent first and clearly labelled, shows that the seller understands the question and can answer it precisely.

After identification, the authority usually asks for the core safety file: a description, risk reasoning, and any test or handling notes that support the product. For wax melts, that core might cover overheating, smoking, fragrance behaviour, and container heat, in general terms, with notes showing what was considered and what was checked. The seller should present that core in indexed order, with a short cover note explaining what each document is, rather than sending an unlabelled bundle.

The cover note is important. It should list the documents sent, their dates, and any gaps, such as a document that is being obtained or a test that is in progress. A cover note that admits a gap honestly is more credible than a bundle that pretends to be complete while missing a key document.

Illustration: a seller receives 40 enquiries over time and imagines that 20 of them, in round illustration terms, are resolved quickly because the seller sent an indexed identification pack first. Those figures, as presented in What an authority tends to ask for first, and how to answer without panic, are invented, not measured. They illustrate a practical point: an authority that can identify the product and find its core file quickly is more likely to move forward efficiently, while an authority faced with a jumble of documents must spend time sorting before it can even ask its real questions.

The seller should therefore treat the first response as a first impression. A calm, ordered, indexed response signals that the seller takes the enquiry seriously and has a file worth reading, while a panicked dump of everything signals the opposite, even if the underlying product is sound.

Follow up questions are normal, and they should be handled in the same indexed way. Each follow up should be answered with the specific document or note requested, plus a short explanation, rather than with a new bundle of everything. Keeping a log of questions asked, answers sent, and dates helps the seller track the enquiry and avoid contradicting an earlier answer.

• Prepare an identification pack: product, variant, batch, photographs, description.
• Present the core safety file in indexed order, with a cover note.
• Admit gaps honestly in the cover note, with actions and dates.
• Log every follow up question, answer, and date sent.

Enquiry responses often fail through panic or overproduction. A seller who sends everything at once, without an index or explanation, forces the authority to sort the file, and may inadvertently send documents for the wrong product or an old version. A seller who delays for weeks, hoping the enquiry will go away, creates a worse impression than a prompt, partial answer with a clear plan for the rest.

Another failure is to answer from memory rather than from the file. A confident answer that contradicts the file, or that promises a document that does not exist, will be discovered quickly and will damage credibility far more than an honest admission that a document is being located.

Close by filing the enquiry, the identification pack, the core file sent, and the follow up log together, as an enquiry response pack. That pack lets a future team member see what was asked, what was sent, and what remains open, without reconstructing the enquiry from emails.

After the enquiry closes, review the file for lessons: were documents findable, was the index clear, and were any gaps revealed that should be closed for future products. An enquiry, handled well, is not only a problem to solve, but a test of the file that can improve it.