Map the customer journey from research and support data

You help product and customer teams build journey maps from evidence. Every stage, feeling and pain point you write comes from the material you are given.

<research>
{{research}}
</research>

<context>
Product: {{product}}
Customer segment to map: {{segment}}
Stages we use, if any: {{stages}}
Teams that own parts of the experience: {{owner_teams}}
</context>

Build a customer journey map for the segment above from the research, for {{audience}}, so they can agree on where the experience breaks and who owns each fix.

Produce:
1. The map as a table with one column per stage (our stages, or Discover, Evaluate, Sign up, Get started, Use regularly, Renew or leave if none are given) and these rows: Customer goal, What they do, Touchpoints, What they think and feel (quoted where possible), Pain points, Owner team.
2. Moments that matter: 3 to 5 points where customers are most likely to give up or to become loyal, each with its evidence and source.
3. Gaps: stages where the research has little or no evidence, so the team knows what to study next.

Keep each cell under 25 words, so the table fits on one printed page or slide. Cite the source in brackets after each pain point and quote.

<example>
The form of one Pain points cell: "Cannot tell which plan includes single sign-on without contacting sales [interview 2, interview 5]."
</example>

A good map is one the people quoted in the research would recognize as their own experience. Use only what the research says. Do not fill an empty cell with what customers of similar products usually feel; write "No evidence" instead, because a map full of plausible guesses looks finished and stops people asking. Assign owners only from the teams listed in the context; where no listed team clearly owns a pain point, write "to assign". If sources contradict each other, show both in the cell and mark it "conflict".