Describe your customers, the experience you want to understand, and the decision you need to make. Makeform turns that brief into a focused survey with comparable ratings, diagnostic follow-ups, and open questions.
Send customer responses to Google Sheets, Slack, and Zapier.
Sample prompts for the survey builder
Choose a complete brief, adapt it to your customer journey, or send it into the Makeform builder. Each example shows a practical structure, not a live AI result.
Audience
Active customers across plans and lifecycle stages
Format
Quarterly survey with stable metrics and priority questions
Prompt size
581 chars
Example survey structure
Quarterly survey with stable metrics and priority questions
Overall, how satisfied are you with your experience?
What is the main reason for your rating?
Which two improvements would matter most?
What should we never change?
Suggested analysis tags
Customer strengths
Journey friction
Follow-up requested
Ask about one experience at a time. A single rating that mixes product quality, support, price, and onboarding tells the team that something is wrong without showing where to act.
Step 1
Frame
choose the customer moment, audience, and decision
Step 2
Listen
combine comparable ratings with customers' own words
Step 3
Diagnose
separate journey stages, themes, and root causes
Step 4
Close
assign follow-up, share changes, and listen again
Turn feedback into direction
Satisfaction, recommendation, and effort scores can reveal movement, but they cannot explain it alone. Connect each signal to a journey moment, a diagnostic follow-up, and an owner.
Keep a small core on satisfaction, recommendation, effort, or confidence. Repeat the same scale and direction when comparison matters, while rotating diagnostic topics.
Ask about discovery, purchase, onboarding, product use, support, and renewal separately. When a score falls, teams can locate the friction.
Place a focused optional comment after a rating or selected problem. Prompts such as what made this difficult preserve useful customer wording without adding essay boxes everywhere.
Listening moments
A relationship survey, a journey survey, and a support follow-up answer different questions. Start with the moment your team can improve, then keep only the measures and context needed to understand it.
Check the wider relationship across usefulness, reliability, value, support, and confidence. Ask customers to rank or choose priorities so a broad survey ends with a practical view of what matters most.
Send a short survey after purchase, delivery, onboarding, a key task, or support. Anchor every question to that recent interaction so responses describe an experience customers can still recall clearly.
Use survey responses to identify themes and invite willing respondents to a conversation. Make contact permission explicit and optional, rather than assuming every person who comments wants direct outreach.
Let customers flag an unresolved issue and request contact. Route those submissions to the right owner while keeping the research response distinct from a support promise or guaranteed outcome.
VoC survey workflow
Start with a customer moment and an internal decision. Define both, generate a focused draft, test the response path, and agree on ownership before launch.
Name the customer group, experience period, and decision the findings will inform. Choose a relationship baseline, journey diagnosis, recovery signal, or one product question.
Tell Makeform the audience, trigger, length, core measures, themes, and follow-up rules. Request one idea per question, balanced options, and useful branching.
Replace internal jargon, leading claims, and double-barreled questions. Preview the form on mobile, test high and low ratings, confirm required fields are necessary, and check that optional contact permission is clear.
Explain why you are asking, survey length, and how feedback will be used. Assign response review, requested follow-up, prioritization, and customer updates.
Relationship vs transactional vs exploratory
Use relationship listening for the broader account, transactional feedback for a recent moment, and exploratory research to understand needs before choosing a solution.
Field guide
A practical questionnaire connects a customer outcome to the journey conditions that shaped it. Use these six sections as a starting point, then remove anything your team cannot interpret or act on.
Purpose and context
Tell customers which relationship, transaction, product, or period to consider. Collect only context that changes interpretation, such as journey stage, use case, or tenure. Avoid undefined recall periods and internal jargon.
Outcome signals
Choose a fitting outcome signal: satisfaction, likelihood to recommend, effort, confidence, or goal completion. Keep scale wording, range, and direction stable. Review the response distribution and reasons, not only one average.
Experience drivers
Separate usefulness, reliability, ease, clarity, speed, support, and value. One idea per rating makes a low result diagnosable. Offer not-applicable when a customer has not encountered a feature or service.
Customer language
Pair important ratings with optional follow-ups. Ask what shaped the score, what the customer was trying to do, what got in the way, or what should remain unchanged. Show conditional prompts only when useful.
Priorities and tradeoffs
A long list of requested improvements can leave every idea looking equally important. Ask customers to choose or rank a limited number of priorities, then compare those choices with satisfaction and open comments. Keep the options specific enough that a product or CX owner knows what the label means.
Follow-up and closure
Let respondents choose whether they want contact about an unresolved issue, a research interview, or neither. Keep the contact field optional and state what kind of follow-up they are requesting. Internally, assign an owner and distinguish urgent service recovery from themes that need broader investigation.
Related tools
Use the broad voice of the customer survey to find themes, then choose a focused survey for satisfaction, recommendation, product feedback, onboarding, support, or churn.
Measure satisfaction across an experience and ask focused follow-ups that explain high and low ratings.
Open toolBuild a recommendation survey with an optional reason and customer context for interpretation.
Open toolCollect ideas, problems, praise, and contact permission in a flexible feedback channel.
Open toolExplore customer goals, current alternatives, unmet needs, and priorities before choosing a product direction.
Open toolFind setup friction, missing guidance, and obstacles between signup and a customer's first successful outcome.
Open toolAsk departing customers about triggers, unmet expectations, alternatives, and what could have changed their experience.
Open toolFAQ
Practical answers for product and CX teams designing a customer survey that produces interpretable ratings and useful language.
A voice of the customer survey is a structured way to learn what customers are trying to accomplish, how they experience a product or service, where friction occurs, what they value, and what they want improved. It combines comparable questions such as satisfaction or effort with focused open prompts that capture customers' own language. The useful output is not merely a score; it is a set of signals tied to journey moments, customer needs, and decisions a product or CX team can make.
Begin with the customer outcome you need to understand: satisfaction, recommendation, goal completion, effort, confidence, or continued-use intent. Add separate diagnostic questions about relevant drivers such as usefulness, reliability, ease, support, delivery, onboarding, or value. Include an optional reason after an important rating, a priority question that asks which changes matter most, and a final prompt about what should remain unchanged. Collect only segment details you have a plan to compare.
A customer satisfaction survey usually centers on how satisfied someone is with a product, service, or interaction. A voice of the customer program can include satisfaction, but it reaches further into customer goals, unmet needs, journey friction, expectations, language, and improvement priorities. Use a satisfaction survey for a focused experience measure. Use a broader VoC survey when several teams need to connect relationship signals, journey diagnostics, and open feedback to a shared set of decisions.
Choose the measure that fits the decision rather than adding every familiar metric. Recommendation questions can support relationship listening, satisfaction fits an evaluated product or interaction, and effort fits a specific task such as setup or getting support. Keep wording and scales stable when comparison matters, and always add enough diagnostic context to understand what shaped the answer. A metric identifies a signal; journey questions and customer comments help the team investigate the cause.
Length should match the moment and the value of the invitation. A post-transaction survey may need only a few ratings, one conditional follow-up, and an optional comment. A periodic relationship survey can cover more themes if each one has an owner and a planned use. Tell customers the expected time, test on mobile, use branching to hide irrelevant questions, and remove repeated measures. A focused survey is easier to interpret than an inventory of everything the business might someday want to know.
Start with response distributions and patterns by journey stage or planned customer segment, then read comments alongside the ratings that triggered them. Group open responses into a consistent theme list, retain representative wording, and distinguish frequency from severity or strategic importance. Check who was invited and who responded before generalizing. Combine survey evidence with support, interview, or product-use evidence where available, choose a limited set of priorities, and assign each next investigation or change to an owner.
Yes. Makeform supports unlimited free forms and responses, so you can generate a voice of the customer survey, edit the wording and response scales, and publish it without a response cap. The paid tier removes the Makeform badge. You can create separate relationship and journey surveys, test each response path, and keep collecting customer feedback on the free plan.
Before launch, decide who reviews new responses, who handles requested contact, and how themes enter product or CX planning. Separate individual service recovery from broader research: an unresolved case may need a direct reply, while a repeated theme may need investigation across teams. After decisions are made, tell customers what the team heard, what it is changing, what it is still studying, and when the next update or listening round will happen. Avoid promising a specific outcome for every suggestion.
Turn customer signals into questions your team can use.
