How to create a customer journey map in 5 steps?

You create a customer journey map in five steps: define your persona and purpose, collect customer data, map all touch points, add emotions and pain points, and analyze where the experience can be improved. The process takes an average of one to two weeks and provides a visual overview of the entire customer journey, from first contact to aftercare. In this article, we answer the most frequently asked questions about customer journey mapping so you can get started right away.

What do you need before you start mapping?

Before you start customer journey mapping, you need three things: a clearly defined persona, reliable customer data and the right stakeholders at the table. Without this foundation, you’re building a map on assumptions rather than reality, leading to insights that don’t align with the real customer experience.

Start by determining your scope. Will you map the entire customer journey, or will you focus on one specific journey, such as the application process or the handling of a complaint? A defined scope makes the process manageable and the outcomes more useful.

What you specifically need:

  • Customer data: call recordings, survey results, complaint records and data from your contact center on contact reasons and volumes
  • Internal knowledge: employees who have daily customer contact know exactly where things go wrong
  • Technical overview: a list of all systems and channels customers use to contact us
  • Personas: descriptions of your key customer segments, including their goals, frustrations and expectations

Also, be sure to appoint a facilitator to guide the process and schedule a joint work session with representatives from customer service, marketing, IT and operations. Diverse perspectives prevent blind spots in the map.

What are the 5 steps to creating a customer journey map?

You create a customer journey map by successively defining your persona, collecting data, mapping touchpoints, adding emotions and pain points, and identifying improvement opportunities. Each step builds on the previous one, making the map increasingly concrete and actionable.

Step 1: Define your persona and the scenario to be mapped

Choose one specific persona and one specific scenario. Don’t try to map all customers and all situations at once. A sharp focus yields better insights than a broad, vague map.

Step 2: Collect qualitative and quantitative data

Combine hard numbers (contact volumes, wait times, channel selection) with soft insights (customer interviews, feedback forms, recordings of conversations). Data from your contact center is particularly valuable here because it shows directly where customers get stuck.

Step 3: Map all touchpoints

Write down every moment the customer interacts with your organization: website, phone, email, WhatsApp, store, invoice, or social media. Plot these touchpoints chronologically on a timeline.

Step 4: Add emotions, thoughts and pain points

At each touchpoint, indicate how the customer feels: frustrated, satisfied, confused or relieved. This is the heart of the customer journey map. Here you can see where the experience drops and where opportunities lie.

Step 5: Identify improvement opportunities and set priorities

Highlight the moments where the emotion curve drops the deepest. These are your priority areas for improvement. Link a concrete action, owner and timeline to each pain point.

What touchpoints should not be forgotten in a customer journey map?

The touchpoints that organizations most often forget are the moments between active interactions: the waiting time after an initial contact, the confirmation email that never arrives, or the moment when a customer searches for information themselves because the service is closed. It is precisely these quiet moments that often determine the overall experience.

Make sure you include at least these touchpoints:

  • Advance search behavior: how and where does the customer search for information before contacting them?
  • First contact: which channel does the customer choose and what is their expectation at that time?
  • Wait and transfer moments: every moment of waiting or transfer is a touchpoint with emotional charge
  • Aftercare: what happens after the problem is resolved? Does the customer receive a summary, a satisfaction survey, or nothing?
  • Channel switching: the moment a customer switches from WhatsApp to phone, or from website to email, is often a signal of frustration
  • Out of office hours: what does a customer who tries to contact you at 8 p.m. experience?

A complete picture of the customer journey only emerges when you also include the invisible, passive moments. This is precisely where the greatest opportunities for improvement lie hidden.

What is the difference between a customer journey map and a service blueprint?

A customer journey map describes the experience from the customer’s perspective, while a service blueprint shows the internal processes and systems that make that experience possible. The journey map answers the question “how does the customer experience this?” while the service blueprint answers “how does this work behind the scenes?”

The two instruments complement each other. In practice, use them as follows:

  • Customer journey map: ideal for identifying emotional pain points, improving customer experience and creating support among management and teams
  • Service blueprint: ideal for redesigning processes, resolving operational bottlenecks and aligning systems and departments with the desired customer experience

Always start with the customer journey map. Once you know where the customer experience is lacking, use the service blueprint to understand what internal processes or systems are causing it. This is how you work from the outside in: from the customer to the organization.

How do you use a customer journey map to prioritize improvements?

You use a customer journey map to prioritize improvements by combining the moments with the lowest customer satisfaction with the moments with the highest contact volume. Where the two converge, the impact of improvement is greatest and the urgency is highest.

A practical approach is to create a priority matrix after completing the map. Rate each pain point on two axes:

  1. Impact on customer experience: how much does the emotion curve drop right now?
  2. Frequency: how often does this occur? How many customers hit this point?

Pain points that score high on both axes are prioritized. This prevents you from investing time in solving problems that rarely occur or have little impact on the overall experience.

Then link each selected area of improvement to a measurable objective. Think about reducing the number of call transfers, reducing the average handling time, or increasing the customer satisfaction score on a specific channel. Without measurement goals, the journey map remains a pretty poster instead of a steering tool.

How often should you update a customer journey map?

You should update a customer journey map at least once a year, and immediately after significant changes in your services, systems or customer behavior. A journey map that remains unchanged for more than 12 months often no longer describes today’s reality.

Concrete reason to update earlier:

  • You add a new contact channel, such as a chatbot or WhatsApp integration
  • You are migrating to a new telephony platform or contact center system
  • Complaint volumes suddenly rise at a specific touchpoint
  • Your customer satisfaction scores drop for no apparent reason
  • Your target audience changes in composition or behavior

Schedule updating your journey map as a recurring activity, not a one-time project. Organizations that structurally embed customer journey mapping into their improvement cycle consistently see better results than those that set up the map once and then leave it.

How Pegamento helps with customer journey mapping

We understand that a customer journey map only has value if you can actually do something with it. That’s why we help organizations not only to understand the customer journey, but also to implement the resulting improvements.

What we specifically do for you:

  • Insight into contact reasons and customer behavior: with our omnichannel technology, you bring telephony, chat, WhatsApp and email together in one view, so you can finally measure what’s really going on
  • Customized solutions with standard building blocks: no costly customization, but smart combinations of proven modules that perfectly fit your customer journey
  • Everything under one roof: from consulting and implementation to management and support, so you have a single point of contact and no complex supplier structures
  • AI-driven automation: our Agentic AI assistants take over repetitive queries, allowing employees to focus on the complex, human moments in the customer journey

Ready to map and really improve your organization’s customer journey? Contact us and we’ll be happy to think with you about the first step.

Frequently Asked Questions

How long does a customer journey mapping session take on average?

A full customer journey mapping session takes one to two days on average, depending on the complexity of the customer journey and the number of stakeholders involved. Preparation - collecting data and inviting the right people - usually takes the most time and can take one to two weeks. Schedule the work session itself to be at least half a day to achieve sufficient depth and not get stuck in superficial observations.

Which tools are best to use to visualize a customer journey map?

For visualizing a customer journey map, tools such as Miro, Mural or Lucidchart are popular choices because they allow real-time collaboration and are easy to share with stakeholders. For a more structured approach, there are specialized tools like Smaply or UXPressia, designed specifically for journey mapping and persona development. Are you starting out for the first time? Then a simple whiteboard or shared Google Slides document will suffice just fine to put together the first version.

What do you do when team members disagree among themselves about what the customer journey looks like?

Differences of opinion among team members are actually valuable: they point out blind spots or departmental silos that negatively affect the customer experience. Resolve this not by voting or following the loudest voice, but by going back to the data. Customer interviews, call recordings and contact center data are objective referees that help test assumptions against reality. Write down talking points as hypotheses and plan targeted customer surveys to confirm or refute them.

Can you create a customer journey map even without extensive customer data?

Yes, you can - but be aware of the limitations. Without customer data, you build a so-called 'assumption map,' which is useful as a starting point but not as an end product. Start with the knowledge of employees who have daily customer contact, supplemented by public reviews, complaint registrations or Net Promoter Score results. Then validate the map as soon as possible with real customer input, for example through five to ten short interviews, to replace assumptions with facts.

How do you ensure that the insights from the journey map are actually taken up within the organization?

The biggest pitfall after a journey mapping process is that the map is hung up nicely but no one takes responsibility for it. Prevent this by immediately naming an owner, a concrete action and a deadline for each identified pain point during the session itself. Link the improvement points to existing KPIs and schedule a quarterly review in which progress is discussed. A journey map that does not lead to action is a costly investment of time with no return.

Does a customer journey map also make sense for small organizations with a limited budget?

Absolutely - indeed, small organizations often benefit faster from a journey map because the lines of communication are shorter and improvements can be implemented faster. You don't need an expensive agency or sophisticated software: a facilitated half-day work session with the right people, a whiteboard and a handful of customer conversations are all it takes to produce an initial usable map. The investment in time far outweighs the cost of customer turnover or repeated contact that could have been avoided.

What's the difference between a current-state and a future-state customer journey map?

A current-state map describes what the customer journey looks like now, including all the pain points and frustrations - this is the map you create based on existing data and customer feedback. A future-state map describes what the ideal customer journey should look like after improvements are made. Always start with the current-state map to have a fair starting point, and then use the future-state map as a blueprint and communication tool to align teams and management on the desired customer experience.

More blogs

Download the white paper here

Deepen your knowledge with Pegamento’s white papers.

Joost Schaap-Account manager Pegamento

Joost Schaap

Senoir Account Manager

When a customer contacts an organization because they have a complaint, it is crucial that the employee of the organization begin by listening carefully. What does this complaint mean for the customer and also for their own organization? How can this complaint be resolved? After listening carefully the employee needs the right information so that a solution can be offered.

This piece was written by Joost Schaap, working as an Account Manager at Pegamento.

Tim Treurniet-AI developer Pegamento

Tim Treurniet

Designer of Intelligent Systems

Real childhood heroes I never had. But in retrospect, I believe figures like Willie Carrot or Dexter’s lab may have had an influence on me. I get energy from actually making innovative and useful products myself. Nothing like seeing the effect of a project that automates a boring task, or makes a complex process suddenly accessible.

A nice bridge to my photograph is the physical aspect of my work. By working with image recognition, I am often very directly connected to the physical world and my work is more than just programming. For example, our image recognition software ensures safety on bridges, tracks players on a soccer field or uses your own smartphone to accurately measure yourself. This combination between physical and digital provides variety and extra challenge. For me, these are the main reasons for my interest and enthusiasm in what I do!

This piece was written by Tim Treurniet, employed Designer of intelligent systems at Pegamento.

Vera van der Plas-UI-UX designer

Vera van der Plas

UI/UX Designer

As a UX/UI designer, I deal daily with transforming complex data into user-friendly visualizations. All of this topped off with a digital lick of paint which should attract the visitor’s attention to take action.

One of the interesting aspects of this field I find the effects that small tweaks, both textual and visual, can have on conversion. The psychological impact that a simple background color of a CTA button has on our behavior is huge. After all, that color can determine whether or not you are going to buy that product.

What we see and how our brains process and interpret this information fascinates me. The possibilities of subconsciously pointing potential customers in your chosen direction are endless. I hope to apply my expertise more often within our solutions in the future.

This piece was written by Vera van der Plas, working as a UX/UI Designer at Pegamento.

Fouad Rahaoui-Finance Pegamento

Fouad Rahaoui

Financial Controller

A Financial Controller within a company should not only be an expert in Finance. You must also have knowledge of the latest IT developments. Because these are also moving very quickly in the world of Finance.

At Pegamento, I can learn all about the latest IT developments. Like the latest development in the field of Machine learning and deep learning.

Through these application areas, as Financial Controller, I can further automate the financial business processes within Pegamento and implement improvements for the automatic processing of financial data.

This piece was written by Fouad Rahaoui, working as a Financial Controller at Pegamento.

Ernst Vegter-Business consultant Pegamento

Ernst Vegter

Business Consultant

Hospitality is one of my deepest motivations.
Not surprisingly, of course, customer service is a common thread in my career. Aspects of hospitality is being able to connect, to facilitate but mainly to make someone feel genuinely welcome. My intuition is my greatest asset to be able to put myself in the shoes of a guest. A customer is my guest.

Fed by various senses, an image forms around the client. I listen to what is being said, watch facial expressions, taste the underlying tone and get a feel for the challenge to be addressed. An image literally forms on my retina. I have to be able to see it. If I can see it, I can create it.

In this, the trick is to pursue simplicity, give the client a warm feeling that the problem is understood, receive good advice, facilitated and carefully guided to the solution. Trust, connect and unburden.

The feeling when a guest arrives at your hotel after a long tiring journey, can sit in front of the fireplace, be handed a good glass of wine and stare carefree at the fire. My guest knows it will be okay.

This piece was written by Ernst Vegter, working as a Business Consultant at Pegamento.

Gunisch-AI developer Pegamento

Gunish Alag

AI Developer

A picture is worth a thousand words, is an expression most of us have heard. We see a lot of things around us on a daily basis and subconciously have the ability to recognize and understand them. This ability of humans to me seems bizarre.

As a computer vision developer at Pegamento that is what I do, break down complex problems and turn them into solutions using images by meticulously extracting useful data.
With the world moving forward and new technologies emerging, complicated problems which were difficult to solve a decade earlier suddenly seem possible and viable. The future is full of new challenges and I look forward to them.

This story is written by Gunish, working as an AI developer at Pegamento.

Ewold Jansen-Service engineer Pegamento

Ewold Jansen

Service & Support Engineer

Hearing the wishes a customer has or the problems a customer is facing is important in order to then be able to help them properly. In both cases, I help find the right solution.

When the customer comes to us with a desire, they don’t know what all the options are. In this I advise them to make the right choices. When problems arise, listening to them is important. For example, a problem arises from a wrong action. By communicating well in this, many problems can be solved quickly by explaining it well. Through poor communication, a small problem can become very big.

This piece was written by Ewold Jansen, working as a Service & Support Engineer at Pegamento.

Andre Glasbergen-Scrum master Pegamento

Andre Glasbergen

Scrum Master

After completing my studies, I started working as a developer at a young Pegamento with a lot of ambition and enthusiasm. In the first years I learned all about process automation, now better known as RPA. I often had to rack my brains to convert the work instruction into a logical function, with not too many If-statements, so that the robot could perform the work.

I developed further and went to work as a consultant. Listening well to the customer and supporting in the pre-sales phase of projects. Executing projects and listening suited me very well. It was a small, but logical, step to now work as a Scrum Master and Project Manager. I have been supervising projects for a few years now. Such as RPA, Cloud applications and AI, according to the Human lead agile approach, We build this with a large team of specialists.

This piece was written by André Glasbergen, working as a Scrum Master at Pegamento.

Ensar Ari-IT engineer Pegamento

Ensar Ari

IT Engineer

Good communication between customer and organization is very important. As an organization, you naturally want to be easily accessible to your customers. Either via social media channels or via the old familiar telephone. Often organizations do not know exactly how they want their telephone line set up. That is why I like to help them think along and give them ideas. I believe there is a solution to every problem. But sometimes you just need someone who looks at the situation a little differently.

This piece was written by Ensar Ari, working as an IT Engineer at Pegamento.

Nini Heerings-Chief Happiness Officer Pegamento

Nini Heerings

Chief Happiness Officer

“You get to know someone better by playing for an hour than by talking for a year.”

This quote from Plato is totally hitting home for me. That’s why I like to connect people through play. Because while playing, you are totally on, all your senses at work.
In my great role as Chief Happiness Officer, I want to do that by connecting colleagues with each other and with the organization. In a creative and playful way that suits Pegamento.

When I’m not at work, I also enjoy connecting people. I do this by organizing The Playground, where adults play games you used to play in the schoolyard, gymnasium or neighborhood playground. The pure feeling of fun, total relaxation and no thoughts of anything but playing. That feeling is the goal.

This piece was written by Nini, working as Chief Happiness Officer at Pegamento.

Ger Koedam-Communication & Marketing Pegamento

Ger Koedam

Marketing & Communications

How can I help you? That’s pretty much the first question I ask when talking to people who are curious about our services. In such a conversation, the use of senses is very important. Because not everyone is the same. One person thinks in images, while for another words are important or how something feels. For me, sight and hearing are the most beautiful senses, because both eyes and ears absorb information and can convey or process emotions.

Why hearing? Because listening is essential in contact. And it’s the key to unlocking valuable insights.

I developed this skill early on. As a child, I enjoyed radio plays on the radio, bringing the stories to life in my head.

Pim Ritmijer-Software developer Pegamento

Pim Ritmeijer

Software Developer

Programming is more than just “code knocking. For me, listening to what the customer wants and visualizing that is an important part of software development.

Actively listening to a customer to understand the customer’s full story is crucial before building a solution. When you understand a customer’s story, you can think together about a solution that truly helps the customer.

Visualizing solutions is the next step for me. What will be the route we will climb to get to a solution? What challenges are we going to face to get to the top?

Like climbing, good preparation is valuable. Even though you can’t prepare for everything, preparation helps make the application fit the client’s needs as well as possible.

What a beautiful and fascinating profession programming is.

This piece was written by Pim Ritmeijer, working as a Software Developer at Pegamento.

Denise Verhoef-Software developer Pegamento

Denise Verhoef

Software Developer

Hearing is something you do a lot of as a programmer but also thinking, for example, when you are tasked with putting together a customer need. If the customer wants a function for his application, it is important that as a programmer you think carefully about which functions are functional and which functions are not. In this way, you will put together the most functional application possible and the customer will have a good end product. Turning needs into code into functionality is something I find interesting.

I am currently doing an internship at Pegamento and studying Software Developer. I get a lot of information that you have to process and apply. The nice thing about this is that you can learn new things but also that you can experience how it works in real business. I started this training last year and knew nothing about programming beforehand. Now I can find my own way with programming and I enjoy working with it. That you can get from a blank page to a functional application through code is cool!

This piece was written by Denise Verhoef, working as a Software Developer intern at Pegamento.

Remco Pabst-Business consultant Pegamento

Remco Pabst

Computer Vision & AI Lead

Using innovative software technology for people or business to make “things” easier and smarter is really a driving force. That’s why the connection between the senses appeals to me the most. Our brains connect the senses just like a business process connects people, systems (data) and logic. They register and trigger an action, exactly how it should be in an optimal workflow. Very cool what is already possible today when we add a lot of computational power to that as well.

Hearing also means a lot. Not because I like to listen to Jazz, Soul, Deep House or Focus-like music every day AND have to be able to listen well to interpret a wish or pain point, but more because not everyone can have all the senses at their disposal. Think of him or her with a visual impairment. The fact that in close cooperation we were able to apply AI, TTS/STT technology (which is still in development) for this often underserved group of people in today’s digital world and to improve the interaction and experience with it gives me a lot of energy and meaning to what I try to do with technology; create value.

This piece was written by Remco, working as a Business Consultant at Pegamento.

Thomas de Wolf-Vision Engineer Pegamento

Thomas de Wolf

R&D Director

Once when I had to choose which study I was going to do, I had a hard time making that choice. I was interested in engineering, but what I most wanted to do was just work with a team toward a common goal.

To this day, that is still what I love doing most. The technology has become image recognition and the team the computer vision department of Pegamento. So it’s logical that in terms of sense, I end up with “seeing. By using our image recognition solutions to see things in the real world, our entire team solves relevant problems for our customers. And because of the variation in customers, the places where our solutions end up are never the same. For example, one moment I am in the control room of a bridge and the next day I am on a production line for sandwiches or between the fences of a TBS clinic.

This piece was written by Thomas de Wolf, working as a Computer Vision & AI Lead at Pegamento.

Rob Roode-Research Development

Rob Roode

Research & Development

Recognizing and automating patterns. Tasks we are constantly working on when implementing our robots at Pegamento. My 2 Drentsche Patrijshonden are hunting dogs and certainly not robots. The hunting instinct and intuition is basically in their genes. Continuing to offer new forms of training has taught them to recognize and act independently in hunting situations. Even “unsupervised,” even if I’m not around.

But when you try to teach a brain something, it also starts to see things you don’t expect. Dogs pick up on the slightest deviation in your voice or directions. To start recognizing that and correcting it again is perhaps the most complex challenge. But in our work, for the wonderful clients for whom we get to work, it often yields the most beautiful new insights!

This piece was written by Rob, founder of Pegamento and in charge of Marketing and R&D.

Serge Poppes-CEO Pegamento

Serge Poppes

CEO

Feeling. That’s the best thing Pegamento stands for. Feeling for technology in the broadest sense of the word. Not only feeling for the exciting stuff like AI, but also for the basics of communication.

The very best part of my job is selling, listening, translating and thinking about what really matters. We bring the digital transformation with a great team!
The diversity of our team, how sharp we are, but especially the wonderful things we get to make makes me feel extremely good. Hence, I intuitively chose the sense of “feeling.

Feeling gives life and differentiation!