Customer Journey Touchpoints Mapping Across Five Stages

Map customer journey touchpoints in all five stages, including ones you do not own, and give each an owner, a purpose and a signal.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Customer journey touchpoints are the specific moments where a customer meets your company or forms an opinion about it: an ad, a search result, a pricing page, a sales call, an invoice, a support chat, a review on a third-party site. In the five-stage customer journey framework, touchpoints are what turn awareness, consideration, purchase, retention and advocacy from labels into things a team can inspect and change. This skill produces a touchpoint inventory: a structured list of every touchpoint for one segment, sorted by stage.

The inventory is harder than it looks because touchpoints are spread across teams and many are not yours. Research on customer experience describes customers interacting with firms through myriad touch points in multiple channels and media, with experiences that are increasingly social. Marketing knows the ads, sales knows the calls, support knows the tickets, and nobody has the whole list. The review sites and peer conversations that shape consideration may not appear on anyone's list at all.

A finished inventory does three things. It shows coverage, meaning which stages are crowded and which are empty. It shows ownership, meaning who is responsible for each touchpoint and which ones belong to no one. And it links each touchpoint to a signal, so the team can tell whether it is helping. Nielsen Norman Group lists assigning clear ownership of touchpoints as one of the business goals journey work should serve, and the inventory is where that ownership gets written down.

Use this skill before or alongside building a journey map, when onboarding a new stage owner, or when a stage metric moves and nobody can say which interaction caused it.

How It Works

The inventory is a table with one row per touchpoint. The core columns are stage, touchpoint name, channel, who owns it, whether you control it, what the customer is trying to do there, and the signal you would watch. Optional columns include volume, the last time anyone reviewed it, and a link to the asset itself.

Touchpoints fall into rough ownership groups. Some are fully owned by you, such as your website, product and emails. Some are run by partners, such as resellers, marketplaces or implementation firms. Some are driven by the customer, such as their own internal discussions and the way they use the product. Some are external and social, such as reviews, communities, press and word of mouth. Sorting touchpoints this way matters because the action differs: you can redesign an owned touchpoint, but for an external one you can only monitor, respond and influence.

The inventory is built from several sources at once. Analytics and marketing tools list digital touchpoints and their volume. The CRM and sales notes list calls, demos and proposal steps. Support and success tools list the post-purchase interactions. Interviews and reviews reveal the touchpoints no system records, such as a peer recommendation or a comparison article. Each source is biased toward the team that owns it, so combining them is what makes the list complete.

The inventory is a customer-side view. It records what the customer encounters, not the internal work behind it. When a touchpoint needs fixing and the cause is internal, a service blueprint shows the frontstage and backstage actions and the support processes that produce that touchpoint. Keep the two separate so the inventory stays readable.

Last, the inventory is a living list. Touchpoints appear when the company launches a campaign or a feature and disappear when a channel is dropped. A review date on each row keeps the list honest.

Step-by-Step Guide

Step 1: Fix the segment and the stage definitions

Pick the segment you are inventorying and write down what each of the five stages means for that segment, including what event moves a customer from one stage to the next. For example, consideration might start at the first pricing-page visit and end at a signed order. Without shared definitions, two teams will file the same touchpoint under different stages. Keep the definitions next to the table.

Step 2: Collect owned touchpoints from each system

Export every page, email, in-app message, call type, document and support channel the segment encounters, using analytics, the marketing automation tool, the CRM and the help desk. Ask one person in each customer-facing team to add what their systems miss. Record the owner as a named person or role, not a department. Leave the purpose column blank for now so the collection step stays fast.

Step 3: Add the touchpoints you do not control

List review sites, community forums, analyst reports, partners, marketplaces and peer recommendations where the segment forms opinions about you. Recent customer interviews and win-loss notes are the best source, because customers will tell you where they looked. Search for your category the way a new buyer would and note what they would find. Mark these rows as external so the team knows its options are monitoring and response.

Step 4: Record purpose and signal for each row

For each touchpoint, write in one line what the customer is trying to do there and what the touchpoint should achieve for them. Then add the signal that shows whether it works, such as a click-through rate, a reply rate, a resolution time or the sentiment of recent reviews. If you cannot name a purpose, question whether the touchpoint should exist. If you cannot name a signal, add one to the measurement backlog.

Step 5: Look for gaps, overlaps and orphans

Read the table by stage. A stage with very few rows, often retention or advocacy, is a gap where the customer hears nothing. A stage with many rows saying the same thing is an overlap that may confuse customers. A row with no owner is an orphan, and orphans are where problems go unnoticed. List each finding with a proposed owner.

Step 6: Walk the journey as a customer

Pick a few touchpoints in sequence and experience them yourself, from the first search to a support request. Note where a message contradicts an earlier one, where a link breaks, or where the customer has to repeat information. This walk finds problems that a table cannot, especially at the handoffs between stages. Add what you find to the table as notes on the relevant rows.

Step 7: Publish the inventory and set a review date

Share the table where stage owners can edit it and link it from the journey map. Put a review date on each row and a date for the next full review of the list. Hand the findings from steps 5 and 6 to the relevant owners with the stage metric they affect. The inventory is finished for now when each row has an owner and a signal.

Best Practices

• Name people, not departments. "Marketing" cannot be asked a question. A named owner can, and naming one makes orphaned touchpoints obvious.
• Count the customer's touchpoints, not your campaigns. A campaign might produce several touchpoints, and several campaigns might share one. Record what the customer encounters.
• Interview recent buyers for external touchpoints. They remember where they read about you and whom they asked. No system records a colleague's recommendation.
• Keep one row per touchpoint per stage. If a touchpoint serves two stages, such as a pricing page read by prospects and customers, list it twice with the different purpose for each.
• Sort external touchpoints separately. It keeps the team realistic about what it can change and prompts a monitoring plan for review sites and communities.
• Review the list on the same cadence as the journey map. New campaigns and features add rows every quarter, and stale rows mislead.

Common Mistakes

• Inventorying only what marketing controls: A list built from the marketing stack stops at purchase. Pull from support, success, billing and product analytics to cover retention and advocacy.
• Skipping touchpoints you do not own: Review sites and peer conversations often decide consideration. Leaving them out hides the places where your reputation is formed.
• Listing channels instead of touchpoints: "Email" is a channel. "Renewal reminder sent before the contract ends" is a touchpoint with a purpose and a signal.
• Stopping at the list: An inventory without owners and signals is a catalog. The value comes from gaps, overlaps and orphans turning into assigned work.
• Letting the list go stale: A touchpoint list from last year still includes retired emails and misses new features. Put review dates on rows.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: The Five-Stage Customer Journey Framework

Related Skills

• How to Create a Customer Journey Map That Drives Action
• Customer Journey Content Strategy by Stage
• Identifying Customer Journey Pain Points and Drop-Offs

Sources

• Lemon and Verhoef: Understanding Customer Experience Throughout the Customer Journey
• Nielsen Norman Group: When and How to Create Customer Journey Maps
• Nielsen Norman Group: Service Blueprints Definition

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.