How to Map the Customer Journey from Feedback

min read - Updated on Nov 15, 2026

You can map the customer journey from feedback in Kimola by turning your customers' reviews, survey answers or support conversations into a Report that places what they write on the stages of their experience. Kimola asks two research Dimensions of every piece of feedback: Experience Stages, which asks "When does this occur?", and Experience Context, which asks "Where does this occur?" The Report then counts how much feedback each stage holds, and Tables shows how positive or negative customers are at each stage and which problems sit where. This guide follows three steps: add the two Dimensions, read the stages and cross the stages with sentiment.

Getting Ready

Reports, the Experience Stages and Experience Context Dimensions and Tables are available in every package. Sign in to your Kimola account and have feedback ready in which customers describe what happened to them.

The Goal

This guide answers the question that customer experience, product, marketing and operations teams ask when they want to improve how customers move from first contact to long-term use: at which moments do customers have a good or a bad experience with us. A customer journey map is usually drawn in a workshop, from interviews and from what the team already believes. Kimola builds the same picture from what customers wrote without being asked. It finds the stages and moments they describe, names each one in their terms and counts the records behind it, so you see which parts of the journey your customers talk about and how much each one weighs.

Experience Stages adds the moment to what a Report already knows. Themes tell you what customers talk about, and sentiment tells you how they feel about it. A stage tells you when it happened, and Experience Context tells you where: at home, in a store, at a branch or on the road. A stage comes from the words of the feedback and never from a date column. A review written in March can be about the day the product was delivered in January, and Experience Stages places it on delivery.

The method works on feedback in which customers tell what happened to them: product and app store reviews, open-ended survey answers and support conversations. Some feedback names the stage directly ("At checkout…", "When it arrived…", "After six months…"). Other feedback shows it through what the customer was doing. Feedback that gives no clue about the moment, such as "Great value for the price.", gets no answer for Experience Stages. The share of records that do answer tells you how much of your feedback can be placed on the journey at all. One piece of feedback can describe several stages, and each one is counted.

Example

A meal-kit delivery service wants to know where new subscribers lose patience. It puts the reviews of its app and its website into one Report. Experience Stages might find choosing a plan, delivery, cooking the first meals and pausing or canceling as the stages customers write about, and Experience Context might find in the kitchen and at the front door as the settings. The questions that follow are which stage holds the most feedback and at which stage customers are most negative.

Step 1: Add Experience Stages and Experience Context

Create one Report from the feedback you want to study, and add the two Dimensions while you create it. Both are available in every package. Start from Reports or Home, depending on where your feedback is. Upload a spreadsheet (.xls, .xlsx, .csv or .tsv, one file of up to 30 MB) and choose its text column, paste the link of a product or business page, or connect a helpdesk or a spreadsheet in Google Sheets. Every way leads to the same classifier, structure and Dimensions steps. The full methods are in Create a Report by Uploading a Custom Dataset, Create a Report by Adding Links and Create a Report Using Integrations.

If your file has a date column, choose it as the Date Column. A stage comes from the text, and the date tells Kimola when the feedback was written, which it uses for the Over time charts and for the trends of Signals.

In the classifiers step, choose the Automatic Classifier, which discovers the themes of your data, and the Sentiment Classifier. Step 3 reads sentiment stage by stage, and Performance needs both a content classifier and a sentiment classifier. The Automatic Classifier is a content classifier. In the Structure step, turn on Enable Multi-label Classification, so that a review that praises one moment and criticizes another receives a label for each. See Multi-label vs Single-label Classification.

Note

Choose the Sentiment Classifier together with the Automatic Classifier, because Performance needs a content classifier and a sentiment classifier.

In the Dimensions step, select Experience Stages and Experience Context. Both are listed under All and under Context. Click each one to add it to your selection. Selected Dimensions appear under My List, so you can review them before you create the Report. Experience Stages names the moments of the journey, and Experience Context names the settings around them, so the two together tell you when something happens and where. They overlap in some sentences: "on my way to work" gives Experience Stages a moment of the day and Experience Context a setting, the commute.

[Screenshot: The Dimensions step with Experience Stages and Experience Context selected and My List showing 2]

Tip

Review your selection under My List before you create the Report.

A third Dimension is worth adding when you also want to know what goes wrong at each stage: Pain Points, listed under All and under Issues. Step 3 crosses it with the stages. Every Dimension you add multiplies the queries the Report uses: queries = rows × models × Dimensions. Add Pain Points only if you plan to read it.

On the Review screen, check the Report Title and the Report Language, the language in which Kimola writes the analysis. Required Query shows the queries the Report will use. Create the Report. When it is ready, click View Report.

Note

Every Dimension you select adds to the queries of the Report: queries = rows × models × Dimensions. See How to Calculate Queries for an example.

If you have a Report already, you don't need to create it again. Open its Dimensions page, click the Experience Stages tab without a check mark and click Generate Now. The Dimensions window opens with Experience Stages already in My List, and you can add Experience Context there. Kimola then classifies the Report's existing records with the new Dimensions. See Add Dimensions to a Report.

Tip

A Report you already have gets both Dimensions on its Dimensions page with Generate Now.

Step 2: Read the Stages

Open the Report and click Dimensions in its menu. A row of tabs runs across the top: All, then one tab for each Dimension, with a check mark on the ones the Report has analyzed. Click the Experience Stages tab. Dimensions in Reports describes every part of the page.

The summary card comes first. It shows how many records answer the question and their share of all records, for example "600 records" and "20% of total records". That share is the first number to note, because it tells you how much of your feedback can be placed on the journey. Below it, a headline and a few paragraphs say which stages customers write about across the whole Report, with the key terms in bold. Kimola counts the answers first, and an AI model writes the summary afterwards from numbers that are already computed, so the text never decides which stage is larger.

Below the summary, each stage is a cluster card. A card shows the stage's name, its number of records and its share, a short summary and quotations: excerpts in your customers' own words. Click the eye icon next to a quotation to open the whole record. The panel on the right lists every stage with a bar for its share. Cluster Scale shows each stage's share of the records that answer Experience Stages, and Dataset Scale shows its share of all the records in the Report. Use Cluster Scale to compare stages with each other, and Dataset Scale to see how much of all your feedback a stage holds. Copy as image and Download as image in the top right corner of a card turn it into a picture, ready for a presentation or a chat.

[Screenshot: The Experience Stages tab with the summary card, the record counts and the cluster panel with Cluster Scale on the right]

Note

One piece of feedback can describe several stages, and each one is counted, so the shares on Cluster Scale can add up to more than 100%. A stage that only a few records give is still counted, but its summary is not written, and the page says "Summaries are not available due to small cluster sizes."

The page shows the stages as clusters with their counts. To read them as a journey, arrange them in the order your customers go through them, for example choosing, buying, delivery, first use and renewal. The counts then show where along the journey customers write the most. The counts show where customers write, which is not always where the experience is worst, and Step 3 adds sentiment to answer that.

Open the Experience Context tab to read the settings in the same way: the places and situations customers describe, such as at home, in a store, at a branch or on the road, each with its records, summary and quotations. A stage is a moment, and a setting is the surrounding it happens in. A setting you never designed for, such as a kitchen appliance used in a camper van, is worth a closer look.

To see where each stage happens, click Dimensions at the end of a stage's card. It lists the Report's other Dimensions, each with the share of this stage's records that also answer it. Drag Experience Context into the box that says "Drop columns and dimensions to create a table". The card then shows a table of the settings within this stage, each with its number of records, its share and its sentiment. Columns works the same way with the columns of your dataset, such as a platform or a country. A table on a card is a quick look and is not saved. To keep a view, build it in Tables, as Step 3 does.

[Screenshot: A stage card with the Dimensions list open and a table of Experience Context settings built inside it]

Example

For the meal-kit service, the Experience Stages tab might show that 62% of the records answer the question. Cooking the first meals might be the largest cluster, with 940 records, followed by Delivery with 610 and Choosing a plan with 380. The quotations under the first one describe recipe cards that skip steps and ingredients that arrive in the wrong portions. Dragging Experience Context into that card might show in the kitchen as the largest setting. The service now knows that most of its feedback is written about the first meals cooked from the box, and that the experience happens at the kitchen counter.

To read what lies behind a stage, open Content in Reports and filter by the stage, so that only the records of that moment remain. See Filter Records in Reports.

Step 3: Cross Stages with Sentiment

Click Tables in the menu of the Report. Tables is the page where you cross-tab the Report's feedback: you drag classifiers, columns and Dimensions into a table, and Kimola groups every record by them and shows how many records fall into each group, what share of the feedback that is and how positive or negative each group is. Tables is available in every package. It works on the data the Report has already analyzed, so building a table never starts a new analysis and never uses queries. See Tables in Reports for the whole page.

Build the Table

Drag Experience Stages from the Dimensions card into the area that says "Drop columns to create tables". The table appears at once, with one row for every stage. Every row shows the name of the stage, the number of records in brackets and a bar with its share. The bar on the right shows the sentiment of the stage: green for positive feedback, red for negative feedback and grey for feedback that is neither. The label above it gives the share of positive feedback, such as "81% Positive", or the share of negative feedback, such as "100% Negative", when the stage has no positive feedback at all.

To split every stage by sentiment, drag the Sentiment Classifier from the Classifiers card into the table next. Its labels then appear under each stage, each with its records and its share of that stage. A row under a stage shows its share of the stage above it: if a stage has 100 records and 51 of them carry one sentiment label, that row shows 51%. Because a piece of feedback can carry several labels, the shares of a metric in a multi-label Report can add up to more than 100%.

[Screenshot: A table grouped by Experience Stages, then by the Sentiment Classifier, with the two metric chips above it]

Read Where the Journey Hurts

Compare the stages by their bars and by the number of records in brackets. A stage with a large red share and many records is where many customers have a bad time. A stage with a large red share and few records needs a second look before you act, because the count in brackets shows how much feedback the share rests on. A stage that is mostly green is a moment to protect.

The order of the metrics decides how the table reads. A table grouped by Experience Stages, then by the Sentiment Classifier, shows how each stage splits by sentiment. A table grouped by the Sentiment Classifier, then by Experience Stages, shows how the negative feedback splits across the stages, which is the quickest way to see where most of it sits.

Tip

Put Experience Stages first to read each stage on its own, and the Sentiment Classifier first to see where the negative feedback gathers.

Example

For the meal-kit service, the table might show Choosing a plan (380) at 82% Positive, Delivery (610) at 71% Positive, Cooking the first meals (940) at 46% Positive and Pausing or canceling (260) at 21% Positive. Customers like picking a plan and receiving the box, and sentiment falls at the first cooking and at the end. Grouped the other way round, the table would show how much of the negative feedback each stage holds, and Cooking the first meals would be the one to look at first.

See What Goes Wrong at Each Stage

Drag a second or third metric under the stages to see what sits behind them. Drag Experience Context to see the settings of each stage, and Pain Points, if you added it, to see the problems of each stage with their shares and their sentiment. The themes of the content classifier work in the same way and show which topics customers raise at each moment. See How to Find Customer Pain Points for reading Pain Points in depth.

To compare journeys, drag a column such as a platform, a product line, a country or a branch above the stages. Each value of the column then shows its own stages with their records and sentiment, so you see whether one group of customers goes through the journey differently from the rest.

Example

For the meal-kit service, grouping by the column that holds the platform, then by Experience Stages, might show that Cooking the first meals is mostly negative in the app reviews and mostly positive in the website reviews.

Filters narrow what a table reads. Click Add in the Filters card to filter by Classifications, Columns or Languages, or click the dates at the top right of the page to choose a period, and the table is built again from the matching records only. Filter to one period and then to the period before it to see whether a change, such as a new onboarding flow, moved a stage. Filters change what the table reads and never the data of the Report.

Read the Records and Rank the Themes

A table shows where the feedback sits, and the records show what customers say. Open Content in Reports and filter by a stage to read its records. Then open Performance in the menu of the Report and choose the stage under Dimensions. Both lists are calculated again for the records of that stage, so Worst Performing Themes by Dissatisfaction Score shows which themes drag that moment down. A Dissatisfaction Score runs from 0 to 100: 80 to 100 is Critical, 60 to 79 is Moderate and below 60 is Acceptable. See Performance in Reports.

Save the Table

A table you build disappears when you leave the page, unless you save it. Click Save at the top right, type a friendly name in the Save Table window and click Save. Choose a name that says what the table shows, such as "Stages by Sentiment". Saved tables are listed under Choose a Table. A saved table can also be pinned to the Overview of the Report, so that the journey view is on its first page: the TABLES card of Overview in Reports shows each pinned table with an Open Table link.

Tip

Name a saved table after what it shows, such as "Stages by Sentiment", so it is easy to find in Choose a Table.

[Screenshot: The TABLES card on the Overview of the Report with the Stages by Sentiment table and its Open Table link]

What You Get

A journey Report gives you the following, all from your own feedback.

Stages in your customers' words. The moments customers describe, each with its number of records, its share, a summary and quotations, on the Experience Stages tab of Dimensions.

The settings around them. The places and situations of the feedback, on the Experience Context tab and inside the card of each stage.

Sentiment by stage. A table that shows how positive or negative customers are at each stage, with the number of records behind every share.

Problems and themes by stage. The pain points and themes raised at each moment, from Tables, and the themes that drag one stage down, from Performance.

Journeys compared. The same stages for each platform, product line, country, branch or period, from a column or a filter in Tables, saved under a name and pinned to the Overview.

To share the findings with colleagues who don't use Kimola, export the Report as a PowerPoint file or copy the cards you need as images.

Next Steps

Turn the findings into work. Click Actions in the menu of the Report and create an Action Plan: Kimola writes up to 12 actions from the Report's evidence, each with an owner, a metric and a way to check that it worked. Choose the goal Customer experience, the goal for onboarding, support, delivery, billing and service, and describe the stage you want to improve in The situation. See Create an Action Plan and How to Turn Customer Feedback into an Action Plan.

To see who goes through each stage, add Personas and Social Context to the Report, as described in How to Build Customer Personas from Feedback. To see why a problem occurs at a stage, add Underlying Causes.

A Report analyzes the feedback of one moment. To follow the journey as new feedback arrives, use a Space, which grows file by file and shows how a stage's share changes after each upload. A Space gets Experience Stages from a Dimension model in its Funnel: define the stages in Labels, and every file uploaded to the Funnel's Spaces afterwards is classified with them. If your team already works with a customer journey map, enter its stages in Labels, so every file is read against the same journey. See Add Dimensions to a Funnel.

Tip

If your team already has a customer journey map, enter its stages in Labels, so every file is read against the same journey.

Note

Spaces are available in the Enterprise package. They are also available in Kimola On-Premises.

For more on how teams use this kind of research, see Customer Journey.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.