Which ticket choice needed explanation?
Read for choice clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Mobility and public places / Survey guide
Mobility and public places · A focused questionnaire
Rail ticket machine survey
Identify ticket-machine decision barriers.
Opens product registration. Example questions are not imported automatically.
ILLUSTRATIVE FINDING → ACTION
What people might say
Zone choices lack destination examples.
What you could investigate
Add destinations beside zone choices.
Synthetic scenario, not a customer result.
A useful starting point
Three questions for this specific decision.
Identify ticket-machine decision barriers. These prompts examine choice clarity, abandonment context, help route. Choose only questions your audience can answer. A missing detail can be answered with none; do not assume an issue occurred.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What happened before you stopped?
Read for abandonment context. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
What help did you seek?
Read for help route. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which ticket choice needed explanation? What happened before you stopped? What help did you seek?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which ticket choice needed explanation? | Optional free text; none or not applicable accepted | Read for choice clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What happened before you stopped? | Optional free text; none or not applicable accepted | Read for abandonment context. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What help did you seek? | Optional free text; none or not applicable accepted | Read for help route. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
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
Check what your wording assumes.
Would you agree that this entire experience was clear and easy?
Which ticket choice needed explanation?
The first wording assumes a positive outcome and combines clarity with ease. The revised prompt asks about the concrete situation; respondents may report no difficulty.
Read the answers carefully
What these answers cannot establish.
Do not request payment details.
Zone choices lack destination examples. This is an illustrative pattern, not observed customer data. Do not request payment details.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Zone choices lack destination examples.
Choose an action to test
Add destinations beside zone choices.
Check the experience again
After testing this change—Add destinations beside zone choices.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Zone choices lack destination examples.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
From question to next step
Make the feedback useful.
Set the decision
Identify ticket-machine decision barriers.
Invite relevant voices
Ask after an adult respondent has encountered this specific situation. For draft-copy testing, show the actual material first; accept none or not applicable when the issue did not occur.
Choose an action
Add destinations beside zone choices.
Before you send it
Questions, answered.
Who should answer?
Adult visitors, travelers and service operators who encountered the described information or arrangement. Ask only about the step each person actually encountered; voluntary responses are not automatically representative.
What does the first question help explain?
Read for choice clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. It supports this decision: Identify ticket-machine decision barriers.
What should I preserve in the second answer?
Read for abandonment context. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
How should I read the third answer?
Read for help route. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. Do not request payment details.
What would a practical follow-up look like?
Add destinations beside zone choices. After testing this change—Add destinations beside zone choices.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Zone choices lack destination examples.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
Can I load this automatically in SurveyTeams?
The page offers text, CSV, JSON and Markdown downloads plus manual copying. Registration does not import the questionnaire. Use account-supported features and verify your own response-handling arrangements.
Inside the product
Create a manual draft and check the questions
The real SurveyTeams screenshot shows a separate labelled synthetic event survey. It demonstrates the manual builder, not this questionnaire already loaded and not the task described in the software being evaluated.
- Start a draft with this decision in mind: Identify ticket-machine decision barriers.
- Copy or select only applicable questions from this page. Add them as optional text prompts; the download is an editorial definition, not a product importer.
- Preview the respondent wording. Do not request payment details. Explain your actual response handling before distribution.
Creation and preview were exercised in the observed account. Distribution, results and other features are separate workflows and depend on account conditions.
Build with SurveyTeams
Adapt these questions in your own survey.
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