Set the decision
Start with the decision: Improve how customers describe a problem initially.
Customer experience / Survey guide
Customer experience · Practical survey guide
Support intake survey
Improve how customers describe a problem initially.
Opens product registration. Example questions are not imported automatically.
QUESTION WORDING LAB
Assumes a positive answer
Would you agree that everything about support intake was clear and easy?
Ask about the actual situation
Which detail was difficult to provide?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
From question to next step
Make the feedback useful.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which detail was difficult to provide?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Pass intake context to the assigned responder.
Read the answers carefully
Keep the conclusion within the evidence.
Avoid account secrets and identifiable support logs.
Customers repeat information already in their request. This is a synthetic example, not a customer result. Avoid account secrets and identifiable support logs.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Customers repeat information already in their request.
Choose an action to test
Pass intake context to the assigned responder.
Check the experience again
After trying the change, repeat “Which detail was difficult to provide?” with people who experienced it. Check whether they still describe the original issue: customers repeat information already in their request. Compare explanations and sample context, rather than claiming the change caused an improvement.
A useful starting point
Questions to understand the actual experience.
Improve how customers describe a problem initially. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Which detail was difficult to provide?
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: customers repeat information already in their request.
What information did you repeat?
Repeated details can locate a broken handoff between the initial form and later support conversations. Check which context was already available before adding fields; some repetition may serve legitimate verification.
What would simplify the request form?
Locate an avoidable field, repeated entry or unclear instruction in the initial request form. Check the purpose of that requirement before simplifying it, while retaining necessary verification.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which detail was difficult to provide? What information did you repeat? What would simplify the request form?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Before you send it
Check what your wording assumes.
Would you agree that everything about support intake was clear and easy?
Which detail was difficult to provide?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which detail was difficult to provide? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What information did you repeat? | Optional written explanation | Keep context that distinguishes different experiences. Avoid account secrets and identifiable support logs. |
| What would simplify the request form? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Pass intake context to the assigned responder. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Before you send it
Questions, answered.
Who should receive this questionnaire?
Customers and service owners involved in the described interaction. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “Which detail was difficult to provide?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Customers repeat information already in their request. This is an illustrative pattern to look for, not a claim about your respondents. Avoid account secrets and identifiable support logs.
What would a practical follow-up look like?
Pass intake context to the assigned responder. After trying the change, repeat “Which detail was difficult to provide?” with people who experienced it. Check whether they still describe the original issue: customers repeat information already in their request. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “What information did you repeat?”?
Repeated details can locate a broken handoff between the initial form and later support conversations. Check which context was already available before adding fields; some repetition may serve legitimate verification. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Build with SurveyTeams
Draft your own support intake questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Continue exploring