Write a customer-story request that leaves room for refusal

A customer story can explain how a product was chosen and used, but the request should leave room for a genuine refusal. A satisfied buyer is not automatically a marketing participant, and a private conversation is not automatically publishable material.

Make the purpose, use and choices clear. The resulting story will be stronger when the customer can describe their actual experience rather than perform a script written by the business.

Choose an appropriate moment

Ask after the customer has had a meaningful opportunity to use the product and any active support issue has been handled appropriately.

Do not tie the invitation to a refund, replacement or other service the customer is already entitled to receive.

Avoid repeated requests if the person does not respond. Silence is not an invitation to move the request to several other channels.

Explain the intended use

State where the story may appear, such as a website article, social post or email. If you want photographs or a name, ask specifically.

Do not use a broad phrase like “for our records” when the purpose is public marketing.

Separate optional elements so the customer can agree to a written quote without agreeing to a photograph or full-name display, where your process can support that choice.

Make refusal easy

Say that participation is optional and will not affect their order or support. Provide a simple way to decline.

Do not make the invitation sound like a debt owed because the business worked hard on the order.

If you offer any benefit, keep it independent of a positive account and check the relevant disclosure and platform requirements. Do not buy a predetermined success story.

Ask open questions

Invite the customer to describe what they needed, how they chose and what the experience was like. Ask about limitations or surprises as well as benefits.

Avoid leading questions that contain the desired conclusion, such as “How did our amazing product transform your life?”

Do not infer results the customer did not state. A pleasant purchase is not evidence of a financial, health or business outcome.

Limit the information collected

You usually do not need a home address, identity document or detailed personal history for a product story.

If a photograph includes other people, private locations or identifying details, consider the appropriate permissions and handling before publication.

Keep the interview material in a controlled place and use only what supports the agreed story.

Edit without changing meaning

Improve clarity carefully, preserving important qualifications. Do not turn “worked well for this occasion” into a universal recommendation.

Distinguish the customer's words from the business's explanation. If you add context or product facts, verify them independently.

Give the customer an appropriate opportunity to review the proposed attributed material and confirm the publication permission for that version.

Present the context honestly

Identify the relevant product and time context where it affects interpretation. Do not imply that one experience is typical of every buyer without evidence.

Avoid invented ratings, metrics or before-and-after claims. If the story contains a numerical result, verify what it means and whether it can be supported.

Use the product-page checklist to keep factual specifications separate from subjective experience.

Maintain the published story responsibly

Keep a record of the permission and agreed use. If the product changes materially, review whether the story needs context or removal.

Provide an appropriate route for questions or concerns about the published material. Do not promise a withdrawal process you cannot operate, and seek suitable advice for rights or retention questions.

A good customer story is not merely persuasive copy with a person's name attached. It is a real experience presented with permission, accurate context and room for nuance.

That approach may produce fewer dramatic claims, but it gives future customers something more useful: a recognisable account they can interpret without being told that another person's experience guarantees their own.

Store the final approved wording separately from rough interview notes so a later editor does not publish an unapproved version.