A customer journey mapping template helps you organize what a customer does, needs, and experiences while trying to complete a goal. Use the copyable template below to map one journey, connect problems to evidence, and assign improvements your team can follow through on.
This guide uses a customer-support journey as its worked example. The same structure can be adapted for onboarding, purchases, renewals, or another clearly defined task.
Copy this customer journey mapping template
Start with the scope block, then copy the table into your shared document, spreadsheet, or whiteboard. Add one column per stage and replace every placeholder with research or a clearly labeled assumption.
Journey name: Customer segment: Customer goal: Start and end of the journey: Current state or proposed future state: Research period and sources: Map owner: Last reviewed: Next review:
| Field | Stage 1: [name] | Stage 2: [name] | Stage 3: [name] |
|---|---|---|---|
| Customer goal | [What they need here] | [What they need here] | [What they need here] |
| Customer action | [What they do] | [What they do] | [What they do] |
| Touchpoint and channel | [Where the interaction happens] | [Where the interaction happens] | [Where the interaction happens] |
| Question or expectation | [What they want to know] | [What they want to know] | [What they want to know] |
| Reported feeling | [Evidence or unknown] | [Evidence or unknown] | [Evidence or unknown] |
| Friction | [What makes the task harder] | [What makes the task harder] | [What makes the task harder] |
| Evidence | [Source, date, and scope] | [Source, date, and scope] | [Source, date, and scope] |
| Improvement to test | [Specific proposed change] | [Specific proposed change] | [Specific proposed change] |
| Owner and measure | [Responsible team and outcome] | [Responsible team and outcome] | [Responsible team and outcome] |
For a narrow journey, three stages may be enough. Add more when they expose meaningful changes in customer activity. Preserve loops and alternative routes in notes rather than forcing every customer through the same sequence.
What belongs in a customer journey map?
A useful map has a specific customer, a scenario, stages of activity, and the customer’s experience at each stage. Nielsen Norman Group’s journey-mapping guide describes actions, thoughts, emotions, opportunities, and ownership as core elements.
The evidence and measurement fields in our template help a support team use the map in an improvement review. They make it easier to distinguish a recorded customer problem from a workshop suggestion and to decide what to investigate next.
Worked example: getting help with a failed export
Illustrative scenario, not a customer case study: an administrator needs to export a report before a meeting. The export fails. The journey starts when the error appears and ends when the customer confirms that the downloaded report is usable.
| Stage | Customer activity and question | Possible friction to investigate | Improvement hypothesis |
|---|---|---|---|
| Try self-service | Search the help center: “What does this error mean?” | The error text does not match the article’s terminology. | Add the exact error and a relevant troubleshooting path to the article. |
| Contact support | Open a ticket: “Can you help me finish the export?” | The form asks for context the customer has already provided. | Request only missing diagnostic details and preserve earlier context. |
| Share evidence | Show the steps and result: “Is this enough to reproduce it?” | A screenshot does not show the sequence before the failure. | Offer a short screen-recording request alongside a written option. |
| Try the proposed solution | Follow instructions: “What should I see if it works?” | The reply omits the expected result. | Include a concise walkthrough and an explicit success check. |
| Confirm completion | Open the exported file: “Is the report complete?” | The ticket closes before the customer validates the result. | Ask for confirmation that the export contains the needed data. |
These are hypotheses for research. A real map needs ticket evidence, customer feedback, and observations before you label a problem common or claim an improvement worked.
How to fill in the template
1. Choose one customer goal and segment
Write a question the map should answer, such as “Where do new administrators get stuck when setting up their first report?” Define the start and finish. Keep an experienced administrator’s renewal journey separate from a new user’s onboarding journey if their needs differ.
2. Collect the relevant evidence
Review support tickets, interviews, feedback, and available usage observations for the chosen journey. Record dates and scope. A ticket sample selected because it contains failures cannot tell you how frequently all customers fail.
Use customer statements for feelings and expectations where possible. A long wait may be observable; frustration should be supported by what customers say or do. Leave “unknown” in the map when you need further research.
3. Arrange actions into customer stages
Use stage names such as “Find help,” “Explain the problem,” and “Confirm the fix.” Department names such as “Tier 2” describe your organization and may not describe the customer’s experience. Note channel switches, repeated attempts, and handoffs.
4. Identify the friction and its impact
Describe a specific obstacle: “The customer must re-enter the error after switching from chat to email.” Record the supporting evidence and what remains uncertain. Keep the proposed solution in its own field so it does not obscure the problem.
For richer context, screen recordings can show a software task and its failure. Share only the relevant part and remove unrelated information. Our bug-report templates help structure steps, expected results, and actual results.
5. Assign a testable improvement
Give each proposed change an owner, a success measure, and a review date. Start with a change the team can observe and evaluate. “Improve communication” is too broad; “Add an expected-result section to export support replies” is actionable.
Turn the map into an action plan
Copy this block for each selected improvement:
Problem and affected stage: Supporting evidence: What is still unknown: Proposed change: Owner: Baseline measure and period: Success measure: Potential tradeoffs: Review date: Observed result and next decision:
In the export example, you might measure how often customers need another clarification after the proposed fix, alongside whether the task is completed. Compare equivalent cases and document other changes during the period. A lower reply count alone does not prove a better experience.
Use our customer-service metrics guide when selecting measures, and our communication guide when improving handoffs.
Current-state, future-state, or service blueprint?
- Current-state map: document the experience supported by your evidence today.
- Future-state map: describe a proposed experience and label what still needs validation.
- Service blueprint: add the people, systems, and internal work that support customer-facing interactions.
Keep current observations and future proposals distinct. For broader orientation, read our customer experience journey-mapping guide; use this page when you need the copyable working template.
Review checklist
- The map names one customer segment, goal, and start/end point.
- The stages describe customer activity.
- Every important claim has evidence or an assumption label.
- Loops, channel switches, and missing information are visible.
- Proposed changes have owners and measurable outcomes.
- The review date reflects upcoming product or process changes.
- The team records what happened after each change.
Frequently asked questions
Can I use this customer journey template in Excel or Google Sheets?
Yes. Copy the table into a sheet, replace the placeholders, and add stage columns. Use links or a separate evidence tab for source references rather than putting long ticket transcripts into every cell.
How many stages should a customer journey map have?
Use enough to explain the chosen goal and meaningful changes in the experience. A short support journey and a purchase-to-renewal journey need different levels of detail.
Who should own the map?
Assign one person to maintain it and named owners for improvements. Invite the teams involved in the journey to challenge assumptions and provide evidence.
How often should we update it?
Choose a review date and revisit the map when the relevant product, policy, or customer behavior changes. Update the evidence after an improvement test so the map reflects what you learned.
