{
  "title": "Partner introduction survey",
  "questions": [
    "Which responsibility was unclear?",
    "What information did you need before meeting?",
    "What should the introduction include?"
  ],
  "question_notes": [
    "Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: customers cannot tell who handles account questions.",
    "Preparation information reveals what customers need to understand the partner's role before an introduction. Clarify verified responsibilities and meeting purpose; an introduction alone does not endorse every partner capability or service promise.",
    "Turn the requested improvement into a testable next step. One illustrative action is: clarify responsibilities before the partner meeting."
  ],
  "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 imply partner capabilities without verification."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Clarify responsibilities before the partner meeting."
    }
  ],
  "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."
}