How to Turn Customer Feedback into an Action Plan

min read - Updated on Nov 15, 2026

You can turn customer feedback into an action plan in Kimola by analyzing it in a Report, checking the Signals Kimola finds in it, writing an Action Plan from the Report for an organization and rating the actions the plan proposes. Kimola classifies every piece of feedback into themes and sentiment, tests where the feedback differs between groups or changes over time, and then writes up to 12 concrete actions, each with an owner, a metric and the evidence behind it. Actions that the evidence does not back are dropped before you see them.

This guide follows four steps from the data to rated actions: create the Report, check the Signals, create a Profile and an Action Plan, and rate the actions. It works with any feedback Kimola can analyze, such as the reviews of a product, app or place, a file of survey answers or support tickets, or data from an integration.

Getting Ready

Reports, Signals and the Action Plans of a Report are available in every package. Sign in to your Kimola account and have the feedback you want to analyze ready: the link to a page with reviews, or a file with your feedback in .xls, .xlsx, .csv or .tsv format.

The Goal

This guide answers the question that comes after every research project: we know what customers say, so what do we do about it. Product managers, customer experience leads, marketers and founders ask it when they hold a pile of reviews, survey answers or tickets and a meeting where someone has to decide what changes next. A list of themes tells you what customers talk about. It does not tell you who should change what, how to see whether the change worked, or which of ten findings deserves the first month of work. An Action Plan does.

Kimola writes the plan from the Report in four stages. It forms hypotheses about where problems, needs and strengths concentrate, reads the feedback behind each hypothesis and sizes what actually happens, turns each finding into a concrete change with an owner and a metric, and checks every figure and quote against the evidence. Every action that survives rests on counts and quotes from your own feedback, so your team can check it before it acts on it. The plan gives your team a ranked set of proposals to judge, and rating the actions in Step 4 is where your team does that.

Example

A regional bank collects the App Store and Google Play reviews of its mobile app in one Report. Over the next steps, the Report might show that Login Problems is a theme mentioned far more in the Android reviews, that Card Blocking is the theme customers are most negative about and that customers ask most for higher transfer limits. The plan might turn these into actions such as fixing the Android login flow first and telling customers why a transfer was blocked and how to lift the limit. The rest of this guide follows this bank.

Step 1: Create the Report

An Action Plan of a Report is written from that Report, so the quality of the plan starts with the Report. Create one Report about one thing: your own product, a rival's product or your market. Kimola then reads the whole Report from that point of view. The wizard is the one you use for every Report, so this step names only the choices that matter for a plan and links the articles that describe each part in full.

Choose the Data

Choose the way in that matches your feedback. Paste the link of a product page, an app page or a business profile on a platform Kimola supports to collect its public reviews. See Create a Report by Adding Links and Supported Platforms for Creating Reports from Links. To analyze feedback you already hold, such as survey answers, support tickets or an export from another tool, upload it as a file in .xls, .xlsx, .csv or .tsv format, one file at a time, up to 30 MB. You choose the column that holds the text, and optionally a URL column and a Date column. See Create a Report by Uploading a Custom Dataset. In the paid packages, you can also read the feedback straight from Zendesk, Intercom or Google Sheets. See Create a Report Using Integrations.

[Screenshot: The report creation area on Home with a link pasted in the search bar and the upload area under it]

Decide who the Report is about before you create it, because the plan is written from that point of view in Step 3. A Report of your own app's reviews is about your own offering. A Report of a rival's reviews is about a rival, and a Report of several brands' reviews in your category is about your market. A Report that holds your reviews and a rival's can be read from your side too, when one of its columns tells the brands apart, and Step 3 shows how.

Note

Signals compare groups and follow dates, so keep the columns that describe your feedback, such as the product, platform, country or customer segment, and keep a date column when you have one. A Report from links brings its own Platform column, and a file brings the columns you give it.

Choose Classifiers and Dimensions

In the Classifiers step, choose the Automatic Classifier, which discovers the themes of your data, and the Sentiment Classifier, which labels every piece of feedback as positive or negative. The themes are what Signals compare, and the sentiment lets them measure how negatively a topic is mentioned. See Create a Report Using Automatic Classifier. In the Structure step, turn on Enable Multi-label Classification, so that a review that praises one aspect and criticizes another gets a label for each. See Create a Report Using Multi-Label Classification.

[Screenshot: The Classifiers step with the Automatic Classifier and the Sentiment Classifier chosen]

Dimensions are optional research questions that Kimola asks of every piece of feedback. For an action plan, two of them add the most. Pain Points asks "What goes wrong or creates difficulty?" and Unmet Needs asks "What is missing or desired?". Their answers are the problems to fix and the requests to consider, in customers' own words, with the number of records behind each one. Every answer of a Dimension is also a group that Signals can compare with the others. See What is a Dimension?.

Tip

The Dimensions you select appear under My List on the left side, so you can review them before you create the 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.

On the Review screen, check the Report Title, the Report Language and the Required Query, then click Create Report. The Report Language is the language the results are written in: English, Spanish, French, German, Portuguese, Dutch or Turkish, whatever the language of the feedback. See Language Options in Reports. When the analysis is complete, click View Report.

[Screenshot: The Review screen with the Report Title, the Report Language and the Required Query]

Example

The bank adds the App Store and Google Play pages of its app with add multiple, names the Report "Mobile banking app reviews", chooses the Automatic Classifier and the Sentiment Classifier, turns on multi-label classification and selects Pain Points and Unmet Needs.

Note

A Report holds the feedback Kimola read when you created it and doesn't update itself. To write a plan from newer feedback, create a new Report.

Step 2: Check the Signals

When the Report is ready, it opens on Overview. Before you write the plan, click Signals in the menu of the Report. Signals are the statistically tested findings of a Report: topics that customers mention more often, or more negatively, in one group of feedback than in the others (Differences), and topics whose mentions changed over time (Trends). Kimola generates a Report's signals after its analysis completes, so the page is ready when you open the Report. An action of the plan can name a Signal among the claims it rests on, so reading the signals first lets you recognize them when you read the plan. See Signals in Reports for every part of the page, and What is a Signal? for how Kimola tests them.

[Screenshot: The Signals page of the Report with the Differences and Trends tabs and the first signal cards]

Read Differences and Trends

The page opens on Differences. A Difference points to a topic that stands apart in one group of feedback. The group is a value of one of your columns, such as a platform, a product or a country, or an answer of a Dimension. A Negativity Difference compares how negative the mentions of a topic are in a group and in the rest of the feedback. Trends lists the topics whose share of mentions changed in the latest periods against the periods before, and it is built from the dates of your records.

Every signal is a card. Two large percentages give the measure in the group and in what it is compared with, a title sums up the finding, and two or three sentences explain it with its numbers. Up to three quotes show what customers wrote, in their own words. Why this is shown opens the evidence: what the group is compared with, the numbers behind the finding and its consistency, which says how well the finding holds when Kimola splits the reviews into comparable groups: Consistent, Mostly consistent, Varies or Holds overall. Kimola scores and ranks signals with deterministic methods, so the same records always give the same signals in the same order. An AI model writes the titles and texts afterwards, from numbers that are already computed.

Example

For the bank's Report, a Difference might say that Login Problems is mentioned in 34% of the Google Play reviews and in 12% of the App Store reviews. A Trend might say that Card Blocking has a larger share of the reviews in the latest weeks than in the weeks before it. These two findings tell the bank where to look and when the problem grew. They don't yet tell it what to change, and that is what the plan is for.

Give Verdicts and Open Records

Each card takes a verdict from you, so your team can tell which findings it already knew. Known marks a finding your team already knew, New & important one that is new and needs attention, Unimportant one that holds but doesn't matter for your work, and Artifact one that comes from how the data was collected, not from customers. Click the same verdict again to take it back, and add a note under Add a note (optional) to say why. See Review Signals.

A card is a summary. To read the feedback behind it, click Open in Tables at the bottom of the card. The Tables page opens with the signal's group and topic already applied as filters, so you can read the records and cross them with other columns and Dimensions.

Tip

To check a signal whose consistency is Varies or Holds overall, open it in Tables and break its records down by your other columns, to see where the finding comes from.

Kimola also checks each card before it shows it. Cards marked Not supported by the verbatims or Volume driven are hidden unless you choose to show all signals, so the list starts with the findings that hold up.

Note

Re-generate on the Signals page generates the signals again and permanently deletes the current signals with all the feedback given on them: the verdicts and the notes.

When the page says "No signal has enough evidence in this report", the Report has too few records, groups or periods for the tests to tell a difference from chance. More reviews, more descriptive columns, a date column and Dimensions give the tests more to work with. Continue with Step 3 to see what the plan finds in the Report's other analyses.

Step 3: Create a Profile and an Action Plan

Click Actions in the menu of the Report. A Report without a plan shows Turn this report into an action plan and Create an action plan. Once the Report has a plan, New plan at the top of the page opens the same wizard and keeps the plans already written. The wizard asks four things: who the plan is for, where that organization stands in the Report, what the plan is for and, if you like, the situation you are facing. This step shows the choices that suit a plan written from a Report of customer feedback. Create an Action Plan describes every screen and message.

[Screenshot: The Actions page of the Report with no plan yet, showing Turn this report into an action plan and the Create an action plan button]

Choose or Create a Profile

The first step, Action Plan, asks who the plan is for. A Profile is the organization your plans are written for: your company, a brand of yours, or a client you work for. Select an existing Profile, or click New profile and fill in two fields: the organization's name and a short description of what it does, what it offers and who it serves. Click Next. Profiles are shared across your team, and you can also create, edit and search them in Account › Profiles.

Tip

Give the Profile a description. A few words on what the organization does and to whom make its actions specific, where the name alone gives advice that fits any company in its category.

Example

The bank creates the Profile Acme Bank with the description "A regional bank that serves retail customers and small businesses and offers a mobile app for payments, transfers and card management."

[Screenshot: The Action Plan step with the Profile list and the New profile fields]

Say Where You Stand

The second step, Where do you stand?, shows what Kimola found when it read the Report's columns: a sentence about the data and the side it suggests. When Kimola isn't sure, it adds "This is a guess, please check it." Check the side, because the plan is written from it. Our own offering means the Report is about you, and the plan says what to fix, protect and build on. A rival means the Report is about a rival, and the plan says how to win the demand it leaves open. Our market means the Report is about your category, and the plan says where the opportunities are.

When a column of the Report names brands or products, the step also lets you choose the values that name you. Under Choose column values naming you, pick the column, search its values with Search values and tick every spelling of the name. The other values are compared with you as your rivals. To read the whole Report as yours, leave the column at None: the whole report is about us. A Report can hold several plans, so you can write one for each side, for example one for your own offering and one for a rival's.

Example

The bank's Report holds only the reviews of its own app, so the bank keeps Our own offering and leaves the column at None: the whole report is about us.

[Screenshot: The Where do you stand? step with Our own offering selected]

Choose the Goal and Describe the Situation

The third step asks What is the plan for? A goal narrows the actions to its kind. Balanced covers what matters most, of every kind, and is selected when the step opens. Product development covers what to build, change or fix in the product. Positioning covers what to claim and to whom, and which claims to avoid. Competitive strategy covers where to attack rivals and where to defend. Campaign covers the messages, audiences and moments the feedback backs. Customer experience covers onboarding, support, delivery, billing and service.

Keep Balanced for a first plan, when you want to see what the feedback supports most strongly. Choose a goal when the plan serves one team or one decision, such as next quarter's roadmap or a campaign brief. Under The situation, you can describe in your own words what you are facing, so the actions speak to it. Leave it empty when you have nothing to add. Written in sets the language of the plan: English, Spanish, French, German, Portuguese, Dutch or Turkish. The feedback can be in any of the languages Kimola analyzes.

Example

The bank has capacity for a few major changes in the next two releases of its app. It chooses Product development and writes under The situation: "We plan the next two releases of the app and can take on four major changes."

[Screenshot: The What is the plan for? step with the goals, the situation field and the Written in menu]

Generate and Read the Plan

Click Generate the Action Plan. To change an earlier answer first, click Back. The Actions page shows Generating your action plan with a progress bar and four steps. Forming hypotheses reads the Report and tests where problems, needs and strengths concentrate. Reading the evidence reads the reviews behind each hypothesis and sizes what actually happens. Writing the actions turns each mechanism into a concrete change, with its owner and metric. Checking every claim checks figures and quotes against the evidence, and drops the actions it cannot support. Writing a plan takes about 5 to 7 minutes, and you can leave the page meanwhile: the plan is ready when you return.

When the plan is ready, the page shows its Profile, side, goal and situation, and up to 12 action cards, numbered from 1. The top line of a card says what kind of action it is (Fix, Lean in, Defend or Capture), the area of the organization it belongs to, how firmly the evidence backs it (High confidence, Medium confidence or Low confidence) and which team should own it. Under it, the action is stated in one line and described in concrete terms: what to change, add or stop. A row of tabs answers the questions around the change: Why, Who, When, Where, Risk and How to See It Worked, the metric that shows whether the change worked. A few quotes show what customers wrote. Notes on the plan above the cards lists what Kimola noticed while putting the plan together, such as findings it joined into one action. See Actions in Reports for every part of the page.

[Screenshot: An action card with its kind, area, confidence and owner, the action, the Why tab open and the quotes]

Example

For the bank, the first card might read: Fix, Product, High confidence, owned by the mobile team. The action: "Fix the sign-in failure on Android devices before the next release." How to See It Worked: fewer Google Play reviews mention Login Problems in the months after the release. The quotes are customers' own words, such as "I can't log in since the last update".

At the bottom of a card, Evidence and how we got here opens the claims the action rests on. Each claim is labeled with where it comes from, for example Report brief for a figure from Kimola's overview of the Report, or Signals for a Signal of the Report, such as the ones you read in Step 2. Every claim carries its numbers, such as a count of reviews, a share and the share it is compared with. What happens describes what actually happens to customers, and What customers ask for: lists the remedies they ask for in their reviews.

Under the last card, a line says how many actions were drafted and then dropped because the checks found them unsupported or repeating another one. Sometimes the evidence backs no action firmly enough. The page then says "No action passed the checks this time: the evidence did not back any of them firmly enough. A narrower goal or a situation may help." Click New plan and try again with a goal other than Balanced, or describe the situation so Kimola knows where to look. If the page says This plan could not be generated, click Start a new plan to open the wizard again.

Step 4: Rate the Actions

An Action Plan is a set of proposals, and your team decides which of them to follow. Rating the actions records that decision on the plan, where every team member can see it. You rate on the same Actions page, at the bottom of each card. Rate Actions in an Action Plan describes every part of rating.

Read a card before you rate it. The action, its tabs and the customers' quotes tell you what to change and why, and Evidence and how we got here shows the numbers behind it. Then choose one of the five verdicts. Useful means you would act on it. Already known means you already know it or are already doing it. Too vague means it is not concrete enough to act on. Wrong means its evidence or reasoning is wrong. Not for us means it does not fit your organization. Hover over a button to see what it means. The verdict is saved as soon as you click it, and the card shows the verdict you gave, because every team member rates for themselves.

[Screenshot: The bottom of an action card with the five verdict buttons and Evidence and how we got here]

After you choose a verdict, a field with the hint Why? (optional) opens under the buttons. Type a note of up to 1,000 characters and click Save note, or leave the field empty, because the verdict is already saved. To change a verdict, click another one. To take it back, click the highlighted verdict again, which also removes its note.

Tip

Open Evidence and how we got here before you choose Wrong. It shows the figures and the reasoning behind the action, so your note can say which of them is wrong.

Example

The bank's product team rates the Android login action Useful. It rates an action that says "Improve the app experience for new customers" Too vague, with the note "It doesn't say what to change in onboarding". It rates an action about a feature that already ships in the next release Already known, with the note "Release 4.2 includes this".

The verdicts don't change the plan: every action stays on it. Use them in your planning meeting. Start with the actions rated Useful and give each an owner and a date. Take the actions rated Wrong back to their evidence and to the Report's records, where Open in Tables on a signal and the Content page show the reviews behind a finding. When many actions come out Too vague, write a new plan with New plan, with a narrower goal or a situation that tells Kimola what you are deciding.

An Action Plan of a Report doesn't create Tasks, so your team moves the actions it keeps into the way it already tracks its work. In a Space, which is available in the Enterprise package, every action card has Make a task. See Actions in Spaces.

Note

Delete Plan in the header of a plan permanently deletes the plan with its actions and their verdicts and notes. The other plans of the Report stay as they are.

What You Get

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

A Report of your feedback. Every piece of feedback classified into themes and sentiment, with the answers to Pain Points and Unmet Needs, each with the number of records behind it and quotes in customers' own words.

A list of tested findings. The Differences and Trends of the Report, each with its numbers, its consistency level and the evidence behind it, and your team's verdict on each.

An Action Plan. Up to 12 actions written for the Profile you chose, from the side and for the goal you chose. Each action says what to change, for whom and when, who owns it, how confident Kimola is and how to see it worked, with its evidence.

Rated actions. Your team's verdicts and notes on every action, so the planning meeting starts from which actions are useful, which are known and which need more work.

Next Steps

To write a plan for a different side or goal, click New plan on the Actions page: a Report can hold several plans, and the plans already written stay. Profiles are managed in Account › Profiles, described in Manage Profiles. To understand how Kimola builds a plan and what each part of it means, see What is an Action Plan?.

For the research that comes before the plan, follow How to Find Customer Pain Points to rank the problems in your feedback, How to Analyze Competitor Reviews to write a plan against a rival, or How to Analyze Product Feedback for Your Roadmap to write a plan with the goal Product development. To follow the same feedback continuously and turn actions into tasks, see What is a Space?. Spaces and Tasks are available in the Enterprise package.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.