How to Find Customer Pain Points

min read - Updated on Nov 17, 2026

You can find customer pain points in Kimola by turning your customers' reviews, support tickets or survey answers into a Report that lists what goes wrong, how many customers run into each problem and why it happens. Kimola asks two research Dimensions of every piece of feedback: Pain Points, which asks "What goes wrong or creates difficulty?", and Underlying Causes, which asks "Why does this occur?" The Report then ranks the themes customers are most dissatisfied with and shows where the problems concentrate, by customer group, platform, place or time. This guide follows four steps: create the Report, read the pain points, rank the themes by dissatisfaction and find where the pain concentrates.

Getting Ready

Reports, the Pain Points and Underlying Causes Dimensions, Performance, Tables and Signals are available in every package. Sign in to your Kimola account and have your customer feedback ready: a spreadsheet export, the review page links of your product or a connected helpdesk.

The Goal

This guide answers the question that product, support and customer experience teams ask before they decide what to fix first: what goes wrong for our customers, and why. Customers describe problems in their own words in every channel, and most of it is never counted. Kimola reads all of it, groups the same problem across thousands of records and counts the records behind each one, so you see which problems affect the most customers and which of them share one cause.

Pain Points adds something that themes and sentiment do not give you. A theme tells you what customers talk about, and sentiment tells you how they feel about it. A pain point names the problem itself, such as "slow check-in" or "items replaced without asking", in the terms your customers use. Every pain point stays tied to the records behind it, so you can open it and read what customers wrote.

Example

A hotel group wants to know why its guest ratings fell in the summer. It puts the guest reviews of its hotels into one Report. The Pain Points analysis might show slow check-in, noisy rooms and breakfast queues as the largest problems. Underlying Causes might name one receptionist at the desk during arrivals behind the first and a new events hall next to the rooms behind the second. Each pain point then comes with a cause the hotel can act on.

The method works best on feedback in which customers describe their experience in their own words: product and app store reviews, support tickets and chat conversations, and open-ended survey answers to questions such as "What was the hardest part?". Short notes of praise carry no problem to find, and Kimola leaves them without a Pain Points answer.

Step 1: Create a Report with Pain Points and Underlying Causes

Create one Report from the feedback you want to study, and add the two Dimensions while you create it. 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.

In the classifiers step, choose the Automatic Classifier, which discovers the themes of your data, and the Sentiment Classifier. Step 3 needs both. In the Structure step, turn on Enable Multi-label Classification, so that a review that praises one thing and criticizes another receives a label for each. See Multi-label vs Single-label Classification.

Note

Performance ranks the themes of a Report only when the Report has a content classifier, which gives the themes, and a sentiment classifier. The Automatic Classifier is a content classifier.

In the Dimensions step, select Pain Points and Underlying Causes. Pain Points is listed under All and under Issues, and Underlying Causes is listed under All and under Drivers. Click each one to add it to your selection. Pain Points names what goes wrong, and Underlying Causes names why it happens, so the two together turn a list of complaints into a list of problems with their reasons.

[Screenshot: The Dimensions step with Pain Points and Underlying Causes selected and My List showing 2]

Tip

The Dimensions you select appear under My List, so you can review them before you create the Report.

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.

Tip

If you have a Report already, you don't need to create it again. Open its Dimensions page, click the Pain Points tab without a check mark and click Generate Now. The Dimensions window opens with Pain Points already in My List, and you can add Underlying Causes there. See Add Dimensions to a Report.

Step 2: Read the Pain Points Analysis

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. All shows one card for each analyzed Dimension. Click the Pain Points card, or its tab, to open the analysis. 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 tells you how often your customers report a problem at all, and it is the first number to note. Below it, a headline and a few paragraphs say what customers struggle with 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 problem is larger.

Below the summary, each pain point is a cluster card, largest first. A card shows the pain point's name, a one-line finding, 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 pain point with a bar for its share. Cluster Scale shows each pain point's share of the records that answer Pain Points, and Dataset Scale shows its share of all the records in the Report. Use Cluster Scale to compare problems with each other, and Dataset Scale to see how many of all your customers a problem touches.

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

Note

One piece of feedback can name several pain points, and each one is counted, so the shares on Cluster Scale can add up to more than 100%. A pain point that only a few records give is still counted, but its summary is not written, and the page says so.

To see why a problem happens, click Dimensions at the end of a pain point's card. It lists the Report's other Dimensions, each with the share of this pain point's records that also answer it. If most of the records under a pain point also answer Underlying Causes, customers tell you the reason along with the problem. Drag Underlying Causes into the box that says "Drop columns and dimensions to create tables". The card then shows a table of the causes within this pain point, each with its number of records, its share and its sentiment. A table on a card is a quick look and is not saved.

[Screenshot: A Pain Points cluster card with the Dimensions list open and a table of Underlying Causes built inside it]

Example

For the hotel group, the Pain Points tab might show slow check-in as the largest cluster, with 410 records. Dragging Underlying Causes into that card shows one receptionist at the desk during arrivals as the largest cause behind it, ahead of the booking system freezing. The quotations show how guests put it. The hotel now has a problem, its size and a cause it can test.

Open the Underlying Causes tab as well, to read the causes of the whole Report next to its pain points. A cause behind several pain points is usually the one to fix first, because one change solves many complaints. See What is the Underlying Causes Dimension? for how Kimola reads causes.

Tip

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.

Step 3: Rank Themes by Dissatisfaction

Click Performance in the menu of the Report. The page ranks the themes of the Report by how satisfied and how dissatisfied customers are with them. Every theme gets a Satisfaction Score and a Dissatisfaction Score from 0 to 100, and the page lists the Worst Performing Themes by Dissatisfaction Score, highest first. Pain Points tells you which problems customers describe, and Performance tells you which areas of your business those problems drag down. See Performance in Reports for the whole page.

Read the ranges of the Dissatisfaction Score as follows. A score of 80-100 is Critical: most of the theme's feedback is negative, across enough records to be sure of it. 60-79 is Moderate: the theme draws a lot of negative feedback and is worth watching. Below 60 is Acceptable. The scores are not plain percentages. They are adjusted for the number of records, so a theme with three negative reviews cannot outrank a theme that thousands of customers complain about, and the same records always give the same scores.

[Screenshot: The Performance page with the Worst Performing Themes by Dissatisfaction Score list]

The ranking becomes more useful when you read it for one problem. Under Dimensions on the Performance page, choose a pain point, and both lists are calculated again for the records that give it. The Worst Performing list then shows which themes come with that problem and how negative customers are about them. To read the records behind a theme, open the Content page and filter by the theme's label, or by the pain point itself. See Filter Records in Reports.

Example

For the hotel group, the whole Report might rank room cleanliness as the worst performing theme. Choosing the pain point slow check-in might put front desk and arrival experience at the top of the list instead. The first ranking tells the group where guests are unhappy overall. The second tells it where one specific problem hurts.

Note

Performance needs a content classifier and a sentiment classifier in the Report. If the page shows no scores, check that you chose the Automatic Classifier and the Sentiment Classifier in Step 1.

Step 4: Find Where Pain Concentrates

A pain point that affects all customers equally needs a different fix from one that comes from a single platform, product, branch or period. Kimola gives you three ways to see where a problem concentrates, and each one reads the analysis the Report already has, so none of them uses queries.

The first is Tables. Open it from the menu of the Report and drag a column, such as a platform, a product, a country or a branch, into the table area, then drag Pain Points under it. Each value of the column then shows its pain points with their shares and their sentiment. Reverse the order, with Pain Points first and the column second, to see how each pain point splits across the values. If a problem is large in one group only, you know where to look first. See Tables in Reports.

[Screenshot: A table grouped by a region column, then by Pain Points, with each region's problems and their sentiment bars]

The second is Signals. Click Signals in the menu of the Report. Kimola tests every topic against every group of your feedback and lists the findings that hold up. A Differences signal says that a topic is mentioned more, or more negatively, in one group than in the others, for example in one platform or one persona. A Trends signal says that mentions of a topic changed over time. Click Open in Tables on a card to see the records behind it with the signal's filters already applied. See Signals in Reports.

[Screenshot: A Differences signal card with Why this is shown opened and Open in Tables at the bottom]

The third is the card of a pain point on the Dimensions page. Click Columns at the end of its card to list the columns of your dataset, and drag one into the box to see the values of that column within this pain point, each with its records, its share and its sentiment. It is the fastest way to check a single problem against a single column. A table on a card is not saved. To keep a view, build it in Tables and click Save.

Example

For the hotel group, a table by hotel and by Pain Points might show that slow check-in makes up 38% of the pain points of one city hotel, and under 10% in the others. A Differences signal might say that noisy rooms is mentioned in 31% of the reviews of one branch and in 11% of the reviews of the others, and a Trends signal might show breakfast queues rising in the last weeks. The group now knows which branch to visit and which problem is new.

Tip

Trends need the dates of your records. When you upload a file, choose its date column, so that Kimola can tell which problems are growing.

Note

A signal needs enough reviews in a group, and groups to compare, before a difference can be told apart from chance. When no signal appears, add more reviews or a file with more descriptive columns, such as a product, a platform or a country.

What You Get

The method gives you four results, each tied to the feedback behind it.

A list of pain points. The problems your customers describe, grouped across all records, each with its number of records, its share and quotations in customers' words, and a summary of what goes wrong overall.

The reasons behind them. The underlying causes of each problem, so that you can tell which single cause sits behind several complaints.

A ranking of themes by dissatisfaction. The areas of your business that customers are most negative about, scored so that small themes and large themes compare fairly, and the same ranking for the customers of one pain point.

A map of where the pain concentrates. The groups, places and periods where a problem is larger than elsewhere, from Tables, Differences and Trends, with the records one click away.

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, and drops the actions its checks cannot support. Choose the goal Customer experience, or keep Balanced, which is selected when the step opens. See Create an Action Plan and How to Turn Customer Feedback into an Action Plan.

To share the findings, export the Report as a PowerPoint file or copy the cards you need as images. To find out what customers wish for next to what goes wrong, add the Unmet Needs Dimension to the Report, as described in Add Dimensions to a Report. Both together are the base of How to Analyze Product Feedback for Your Roadmap.

Note

To follow pain points continuously, as new files arrive, use a Space. 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 Pain points.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.