Learn the job customers hired the product to do, what they value, and what creates uncertainty.
What were you hoping this product would help you do?
Start with the complete working structure, then adjust the language, timing, and incentive to fit your customers and brand.
Best used when
Your team has a specific decision or growth objective and needs a focused artifact to move from planning to launch.
What were you hoping this product would help you do?
open textWhy ask it: Captures the job the product was bought to do, in wording that is usually narrower and more concrete than the benefit printed on your product page. Mine the phrasing for copy, and flag any goal your product cannot actually deliver before it turns into a return.
Which feature or benefit mattered most to you?
open textWhy ask it: Tells you which single line of your product page did the selling, so everything else can be cut or moved down. When the answers name a benefit you barely mention, you have found conversion lift that costs nothing but a rewrite.
Overall, how satisfied are you with your experience?
CSATSuggested answers
Why ask it: Gives you one comparable number for the moment you asked about, which is the only way to tell whether a change to support, packaging, or delivery actually landed. Keep the wording and the five options identical every time you run it, and send the two dissatisfied answers to a person the same day.
What is the main reason for your answer?
open textWhy ask it: The score records what happened and this records why, which is why it belongs immediately after the rating while the customer is still holding the thought. Read it grouped by score: the reasons behind low answers are your fix list, and the reasons behind high answers are the next line of your product page.
What is the one thing we could improve?
open textWhy ask it: Asking for one thing instead of general feedback forces a priority, so the answers arrive already ranked by what the customer cares about most. Count how often each theme repeats rather than reacting to the most articulate response, and carry the top three into the next planning cycle.
Is there anything else you would like us to know?
open textWhy ask it: The last question is where the unprompted things arrive: a packaging complaint, a size you do not stock, one support agent thanked by name. Keep it optional and last so it costs nothing in completion, and lean on AI analysis to group the themes once you pass a few hundred responses.
Generate a focused variation while keeping the expert-written version available as your baseline.
Add your goal and audience. If AI is unavailable, the complete template on this page still works as a practical starting point.
Your inputs are sent only to generate this result and are not stored by UserLoop.
Three specifics worth checking against your own store before you launch.
Start with the focused version, publish, and let the first answers steer the next iteration.
Send it by email once the customer has used the product long enough to have a view, which for most categories is one to two weeks after delivery
Ask which item the answers are about when the order held several products, then keep that question first
Read results by product and variant, and take the goal and valued-feature answers straight into that product page
Strong execution usually comes from removing ambiguity and keeping every action tied to the original objective.
Asking on the confirmation page, before the customer has opened the box
Sending one survey for a five-product order, so you never learn which product the answer describes
Collecting the satisfaction score and skipping the reason, which leaves a number with no fix attached
Acting on the most articulate response when the counts point somewhere else
Long enough for real use, short enough for real memory. One to two weeks suits most categories, a supplement or a skincare routine needs three to four before anyone can answer honestly, and a piece of furniture only needs the assembly to be finished. Set the delay by how long your product takes to prove itself rather than by a rule.
Read the answers against the line items. Surveys links every response to the Shopify order, so filtering down to a single product or variant is one step, and a low score on one line stops hiding inside a healthy store average. For multi-product orders, ask the customer which item they are answering about before the detail questions run.
A review is written for other shoppers, a survey answer is written for you. Reviews reward strong opinions and arrive from the customers most motivated to publish, while a survey reaches the quiet middle and stays private, which is exactly why people include the awkward part. Run both, then invite your happiest respondents to leave the public version.
Fewer than you think for direction, more than you think for a number. Three customers describing the same confusing instruction is a real problem worth fixing that week; a satisfaction score built on eleven responses is noise. Let open text drive fixes early and hold the scores until each product line has a stable base underneath it.
Collect useful customer insight with Surveys and grow your audience with Contests.
