Customer Journey Mapping: Stages, Template and a Worked Example

A customer journey map is a picture of everything a person does, thinks and feels from the moment they first hear about you to the point they buy again or leave. Teams build one to find the places where good intentions fall apart: the form that asks for too much, the welcome email that arrives three days late, the support chat nobody answers on Sunday. This guide explains what journey mapping is, gives you a template you can copy, walks through a worked ecommerce example, and shows how to turn the map into messages that actually send.

What is customer journey mapping?

Customer journey mapping is the practice of laying out, in order, the steps a customer takes while trying to achieve a goal with your company, along with the touchpoints they use and the emotions they have at each step. It sits inside the wider discipline of customer experience. The research group Nielsen Norman Group describes a journey map as a visualisation of the process a person goes through to accomplish a goal, and stresses that it should be grounded in real research rather than assumptions made in a meeting room.

That last point matters more than any template. A map drawn from opinion produces a tidy poster and no change. A map drawn from interviews, support tickets and event data produces a short list of fixes you can ship next month.

Why it is worth the effort

• It exposes handoffs. Most drop-offs happen where one team ends and another begins: marketing to sales, checkout to fulfilment, onboarding to support.
• It gives teams a shared picture. Product, marketing and support usually see different slices of the same customer. The map puts them on one page.
• It tells you what to automate. Every gap between two stages is a candidate for a triggered message or an in-app prompt.
• It keeps you honest about retention. Maps that stop at the first purchase miss the part of the journey where most of the profit sits.

The stages of a customer journey

Different industries use different labels, but five stages cover most journeys.

What goes into a journey map

A useful map has a small number of rows. More than seven and nobody reads it.

1. The persona and scenario. One person, one goal. “First-time buyer replacing a worn pair of running shoes” works. “All customers” does not.
2. Stages. The phases above or your own.
3. Actions. What the customer actually does at each stage.
4. Touchpoints. Every place they meet you: ad, website, email, WhatsApp, app, store, support line.
5. Thoughts and feelings. A line or a simple curve from frustrated to delighted.
6. Pain points. What gets in the way.
7. Opportunities. What you will change, with an owner.

How to create a customer journey map

1. Set one clear objective. Decide what the map is for: reducing checkout drop-off, speeding up onboarding, cutting early churn. A scoped map finishes; a general one never does.
2. Choose a single persona. Pick the segment that matters most to revenue right now. You can map others later.
3. Collect evidence. Run five to eight customer interviews, read support tickets and reviews, and pull funnel numbers from analytics. Mix what people say with what they do.
4. List the touchpoints. Walk the journey yourself as the customer, including the confirmation email, the invoice and the cancellation page.
5. Draw the stages and fill in actions, feelings and pain points. Use sticky notes, a whiteboard or a spreadsheet. Keep the language of real customers.
6. Mark the moments of truth. Circle the two or three points where the customer decides to continue or give up.
7. Turn pain points into actions. Assign each opportunity an owner and a date, and decide how you will measure it.
8. Review every quarter. Journeys change as products, prices and channels change. A map that is a year old is a historical document.

Worked example: an online footwear store

Take the persona “Meera, first-time buyer of running shoes”. The numbers below are illustrative and show how a map turns into decisions.

Notice what the map did. It did not say “improve marketing”. It surfaced three specific, ownable changes: a fit guide, a payment-retry message, and a replenishment reminder. Each of those is a message you can build once and let run.

Journey map vs related tools

Metrics to attach to each stage

A map without numbers drifts. Attach one primary measure to each stage so you know whether a change helped.

For retention in particular, a cohort view shows whether customers who joined in a given month keep coming back, and it is more honest than a single average. You can build these views in Flowfox under analytics.

From map to automation

This is the step most guides skip. A journey map describes what customers do. A journey in a marketing platform is the set of rules that responds to what they do. Each opportunity on your map can become a trigger, a wait and a message.

{
  "trigger": "checkout_started",
  "wait": "60 minutes",
  "if_not": "purchase_completed",
  "send": [
    { "channel": "whatsapp", "template": "cart_reminder" },
    { "channel": "email", "template": "cart_reminder_email", "delay": "24 hours" }
  ],
  "exit_when": "purchase_completed"
}

That sketch is what Flowfox journeys build visually: events start the path, segments decide who qualifies, and goals stop the messages once the customer converts. Our first journey tutorial and the guide to goals and waits take about twenty minutes to follow. If you want ready-made starting points, the onboarding and retention use cases contain journeys you can adapt, and the abandoned cart recovery guide shows the checkout example from this article in full.

A journey map shows you where customers struggle. A journey in your platform is how you show up there in time.

Common mistakes

• Mapping the company, not the customer. If your stages are internal department names, start again.
• Skipping research. Workshop-only maps reproduce your own assumptions.
• Trying to map everyone. One persona per map keeps the picture sharp.
• Stopping at purchase. Post-sale is where repeat revenue and referrals live.
• Filing it away. Pin the map where teams plan work, and review it each quarter.

If you run an online store, the ecommerce solution bundles events and journeys for the stages above. Subscription and software teams can look at the SaaS solution. For more on keeping customers once they have joined, read our guide to customer churn rate and browse the Flowfox blog.