{
  "title": "Email verification experience survey",
  "questions": [
    "Where did you expect the message?",
    "Which instruction was unclear?",
    "What should happen after verification?"
  ],
  "question_notes": [
    "The expected message location identifies where people look for verification instructions. Compare it with the documented delivery route without inferring a delivery failure from expectation alone.",
    "An unclear verification instruction reveals whether the message explains the required action and its prerequisites. Clarify the observed process without asking for tokens or verification links; feedback does not diagnose message delivery failures.",
    "Expected behavior after verification identifies the continuation users anticipate. Explain the verified next step without requesting tokens or assuming verification completes every setup task."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Optional short text",
      "reason": "Retain the specific point or condition described; avoid replacing it with an unexplained rating."
    },
    {
      "question": 2,
      "format": "Optional written explanation",
      "reason": "Keep context that distinguishes different experiences. Do not collect verification links or tokens."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Provide a clear continuation action."
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "field_protocol": null,
  "editorial_sections": [],
  "note": "Examples to adapt. Not a validated instrument; manual editorial data, not a product import payload."
}
