Post-purchase questions.
For checkout feedback, ask about checkout. For product feedback, wait until the item has arrived and the customer has had a fair chance to use it.
“How has it been to use?”
If they haven’t used it yet, keep that context rather than treating it as a product opinion.
The answer can tell you what works in everyday life and what falls short. Follow one concrete detail. Avoid bundling fit, delivery, price, and satisfaction into a single question.
Ask about a real moment of use
| What they describe | Ask next | What to investigate |
|---|---|---|
| Fit or function | “What were you doing when it didn’t work as expected?” | Check the product’s dimensions, intended use, or size guidance. |
| Wear or durability | “When did you first notice the change?” | Inspect wear and care conditions before attributing the issue to a material. |
| Unmet expectations | “What felt different from what you expected?” | Compare the product with its description, photographs, and claims. |
| Value | “What has felt most or least useful to you?” | Learn which benefits matter before assuming price is the whole problem. |
Use the customer’s language in the follow-up. If they mention pockets, ask which pocket and what they wanted to carry. Don’t jump straight to “Would deeper pockets fix it?”
Match timing to the experience
There is no universal seven-day rule. A product used immediately may need a different window from an item that needs assembly, repeated wear, or several washes. Ask once the relevant experience has happened.
Include actual users
Ask people who received and used the item. For a gift, the buyer may know about delivery while the recipient knows about use.
Keep contexts separate
Delivered but unused is different from used and disliked. New and repeat buyers may also compare against different expectations.
Use a permissioned customer mailing list. Don’t assume every store, marketplace, or checkout system gives you permission or access to the buyer’s email.
Turn the answer into something you can check
“my phone won’t fit in the pockets”
First clarify the detail.
Ask “Which pockets—the front or back?” Then ask what happens when they carry the phone. The product decision depends on whether depth, opening size, or security is the issue.
Preserve the positive as well as the problem
“Love the fit” is a strength to keep. A pocket complaint doesn’t mean the whole product needs a redesign.
Compare the original words
Check whether several customers describe the same use case. Don’t merge delivery complaints and product-function complaints into one theme.
Make a testable decision
For example, compare front-pocket dimensions on the next sample using the phone sizes customers mentioned. Verify the change with actual use before treating it as solved.
This fictional example is a way to reason about feedback. It doesn’t establish prevalence or predict sales.
Keep useful partial replies
A single answer can contain a specific issue. Keep it even if there is no follow-up reply, and record what remains unknown. Read the surrounding conversation before using a quote to justify a change.
Product-use feedback helps decide what to investigate. It has a different purpose from checkout attribution or collecting public reviews.