How to Close the Loop on Customer Feedback

min read - Updated on Nov 15, 2026

You can close the loop on customer feedback in Kimola by turning a finding in a Space into a Task for the teammate who can act on it, sending the Task to Jira when your team plans its work there, and letting Kimola read the same feedback again after the work is done to tell you whether customers noticed. Closing the loop means that a finding has an owner and a due date, that the work happens where your team does its work, and that someone checks afterwards whether the feedback changed.

This guide follows four steps from a finding to a measured result: spot a finding in a Space, make a Task of it, send the Task to Jira and read what Kimola measures after the Task is done. It works for any channel a Space holds, such as a call center, a survey, support tickets or app reviews.

Getting Ready

Spaces, Tasks and the Jira integration are available in the Enterprise package. They are also available in Kimola On-Premises.

Sign in to your Kimola account and have a Space that already holds classified feedback.

The Goal

This guide answers the question that follows every finding: who is going to do something about it, and how will we know it worked. Customer experience leads, product managers and support managers ask it when the feedback shows a problem and the team that can fix it sits in another department. The loop usually breaks at two points. The finding travels as a message or a screenshot, so the person who owns the fix never sees the numbers and the customers' words behind it. And when the work is done, nobody returns to the feedback to check whether anything changed.

Kimola closes both gaps. A Task carries the finding to one teammate, with its feedback and its numbers kept as evidence. Jira, when your team uses it, holds the work itself. After the Task is done, Kimola reads the same feedback again and compares the weeks before the Task was made with the weeks after it was done, so the answer comes from the feedback itself. Kimola is not a task tracker: the work happens where your team plans it, and Kimola keeps the reason for the work and measures the result.

Example

A car dealership group collects its service customers' feedback in a Space called Service surveys, with a new file every month and a Branch column. Over the next steps, a Signal might show that waiting time at the service is mentioned far more in the Northside branch than in the others, the service manager of that branch takes a Task, the group's Jira project holds the work, and four weeks after the work is done Kimola tells whether customers noticed. The rest of this guide follows this group.

Step 1: Spot a Finding

A finding is something the feedback shows that one team can act on. A Space with classified feedback gives you several places to look, and the most direct is the Signals page. Signals are the statistically tested findings of a Space: topics that customers mention more often, or more negatively, in one group of feedback than in the others, and topics whose mentions changed over time. In the menu of the Space, click Signals, which appears once the Space has its first signals. See Signals in Spaces for every part of the page.

Read the Signals

The page has two lists. Differences points to a topic that stands apart in one group of feedback, where the group is a value of one of the Space's columns, such as a branch, a product or a country, or an answer of a Dimension. Trends lists the topics whose share of mentions changed in the latest periods. Every Signal is a card: it shows the two shares it compares, a title, two or three sentences with the numbers, a consistency level and up to three quotes in customers' own words. Why this is shown opens the evidence behind the card. See What is a Signal? for how Kimola tests them.

A Space runs its Signals again after every file, and every file is also a group, so a Signal can point to what the latest upload brought. On Overview, With the latest files lists the answers and themes that moved with the latest files, which is another way to find what changed. See Overview in Spaces.

[Screenshot: The Signals page of a Space with the Differences and Trends tabs and the first Signal cards]

Example

In the dealership group's Space, a Difference might say that waiting time at the service is mentioned in 31% of the Northside feedback and in 11% of the feedback of the other branches. Two of its quotes are survey answers in which customers say they waited more than an hour for a routine service.

Check the Evidence and Choose

A Signal is a summary, so read the feedback behind it before you act. Click Open in Content on the card to open the records of its group. Then give the Signal a verdict, so your team can tell its findings apart: Known, New & important, Unimportant or Artifact. Mark a Signal Artifact when it comes from how the data was collected, and New & important when it deserves work. See Review Signals.

Choose a finding that one team can own. A finding such as "customers are unhappy with the service" has no owner, while "waiting time at the service in one branch" has one. A large share of the feedback, a clearly negative sentiment and quotes that describe a concrete problem make a finding worth a Task.

Not every finding is a Signal. A theme, a single piece of feedback, a filtered view of Content, a table, an action of the Space's Action Plan, a Customer and a Department can all become Tasks, and Step 2 shows where each one starts. Reports, with their Signals and Action Plans, don't make Tasks.

Note

Reports and their Signals don't make Tasks.

Step 2: Make a Task

You make a Task where the finding is shown, so it carries the finding and its feedback from the first moment. On a Signal card, click Make a task. The same button appears on a single record and on the filtered feedback on Content, on a theme in the All Themes part of Overview, on a table in Tables, on an action card in Actions, on a Customer's page and on a Department's page. See Create a Task for every source. A Task made from a Customer or a Department belongs to no Space, and its evidence reads all your Spaces.

[Screenshot: A Signal card of a Space with the Make a task button]

When the task window opens, Kimola checks whether a teammate already has an open Task of the same finding. If one exists, the window shows it first with "You can follow one of them, or make a new task anyway." Follow the existing Task when it covers your finding, which keeps two teammates from working on the same problem. A badge on a Signal, a theme or an action shows that the finding already has a Task.

Tip

Look for the badge on a Signal, a theme or an action before you click Make a task.

Review the Draft

Kimola writes a draft from the finding, its numbers and a few quotes, in the language of the Space's Funnel, and the window shows Writing... meanwhile. The Title says what needs doing in one line. The Description says why it matters, what to do first and how you will know it is done. Change anything in either one before you create the Task. If the draft can't be written, the window says "The draft could not be written, please try again."

Example

For the Northside finding, the draft might be titled "Cut the waiting time at the Northside service desk". Its description says how much of the branch's feedback mentions the wait, what to check first, such as how many technicians work on the busiest days, and that the Task is done when fewer customers mention the wait.

[Screenshot: The task window for a Signal, with the drafted Title and Description]

Assign and Schedule

Below the draft, Assignee is the teammate who does the work. It starts as you, and the assignee must be a member of your team. Due date is optional: pick a date, or choose In 3 days, Next week or In 2 weeks. Priority is Low, Medium, High or Urgent, and Medium is selected when the window opens. Teammates who need to know about the work without doing it, such as the manager of the team that owns the finding, go under Keep informed, and they are told when the Task changes.

Click Create the task. The Task appears on the Tasks page, and Kimola emails the assignee unless you assigned the Task to yourself. Kimola keeps the finding's evidence as it was that day: its share of the feedback, its sentiment and a few quotes. The evidence doesn't change as new files arrive, so the assignee always sees the problem the Task was made for, and Kimola has a fixed point to compare with once the Task is done. The Task has a page of its own with its evidence, comments and history. See Follow a Task.

Tip

Add the manager of the team that owns the finding under Keep informed, so they follow the Task without owning it.

Note

The evidence is frozen when you create the Task and doesn't change as new feedback arrives.

Example

The group's customer care lead makes a Task of the Northside Signal, assigns it to the service manager of the Northside branch, sets the priority to High and the due date to In 2 weeks, and adds the regional manager under Keep informed.

[Screenshot: The Assignee, Due date, Priority and Keep informed fields of the task window]

Step 3: Send It to Jira

When your team plans its work in Jira, send the Task there. The work then happens in the tool your team already uses, with the finding, its numbers and a few customer quotes in the issue, while Kimola keeps the Task with its evidence and measures the result later. A team that doesn't use Jira can skip this step: the assignee moves the Task from Open to In progress with Start and to Done with Mark done in Kimola, and Step 4 works the same.

Jira is connected once for the whole team. Open ACCOUNT in the main menu, go to Integrations, click the Jira card and click Connect Jira. Kimola takes you to Atlassian to allow access, and you then choose the Jira site, the default project and the default issue type that Tasks go to. Kimola connects to Jira Cloud. See Connect Jira to Kimola.

Note

Jira is connected once for the whole team, and anyone in the team can send Tasks after that.

Send a Task as a New Issue

Send the Task as a new issue when the work isn't in Jira yet. Go to TASKS in the main menu, click View on the Task and find the JIRA card. Choose the project and the Issue type, such as Task or Story, or keep your team's defaults, then click Send to Jira. The issue types come from the project, so the list says Pick a project first until you choose one. When your team has a default project, the window where you make a Task also offers Also send to Jira, which sends the new Task as an issue at once.

The issue carries the finding, its numbers and a few quotes in customers' own words. Emails and numbers in the feedback are masked, so customers' personal details don't leave Kimola. The Task's priority, assignee and due date go with the issue, and when the Jira project doesn't accept one of them, Kimola creates the issue without it. See Send a Task to Jira.

[Screenshot: The JIRA card of a Task with a project and an issue type chosen and the Send to Jira button]

Tip

Choose Also send to Jira while you make a Task to send it without opening its page.

Example

The Northside Task goes to the group's operations project in Jira as a Task issue. The operations team opens the issue and reads how much of the Northside feedback mentions the wait, how negative it is and a few survey answers, without signing in to Kimola.

Link an Existing Issue

Link an issue when the work is already in Jira, for example when your team opened an issue about the same problem before the finding showed up in Kimola. Linking keeps the Task with that issue instead of creating a second one. On the JIRA card, click Link an issue and type the issue's key in the field that says Issue key, e.g. CX-123. Kimola reads the issue and links it to the Task.

What Follows the Issue

Once a Task is in Jira, the JIRA card says "Its status, assignee and due date follow the issue." An issue in a to-do status keeps the Task Open, an issue in progress makes it In progress, and a done issue makes it Done, while an issue resolved as won't do makes it Won't do. The assignee is the teammate whose email matches the issue's assignee, and the due date is the issue's. The Task's status can't be changed in Kimola while it follows the issue, and its comments become read-only because the conversation moves to the issue. The changes that come from Jira are listed in the Task's HISTORY and marked as Jira's.

A Task that is done in Jira is done in Kimola too, so the measurement of Step 4 starts by itself. If your team's Jira connection expires, the Task stops following its issue and the JIRA card says "The Jira connection expired." with Connect it again. The Task keeps its issue meanwhile, so it follows the issue again once Jira is connected.

Tip

Use the same email address in Jira and in Kimola, so that the issue's assignee matches the right teammate.

Note

While a Task follows an issue, its status follows the issue and can't be changed in Kimola.

Step 4: See Whether Customers Noticed

The loop closes after the work is done. When the Task is marked Done, by the assignee in Kimola or through the issue in Jira, Kimola starts to measure it. Two weeks and four weeks later, Kimola reads the same feedback again and shows the answer on the Task's page under DID CUSTOMERS NOTICE? Until the first check comes, the Task shows Being measured. See How Kimola Measures Task Impact for the full method.

What Kimola Compares

Kimola compares the weeks before the Task was made with the weeks after it was done, and the time between the two, while the work was in progress, is left out. At two weeks it compares two weeks with two weeks, and at four weeks it compares four with four. It compares the finding's share of the feedback, which is the finding's records divided by all the feedback of the same weeks, so a busy month with twice as many surveys doesn't make a problem look bigger. It also compares the finding's NPS, the positive share minus the negative share of its feedback. A lower share or a higher NPS counts as an improvement, because a Task is made from a problem. A Task made in a Space reads the feedback of that Space.

While an improvement holds, Kimola checks again at eight and twelve weeks. These checks compare the latest four weeks with the four weeks before the Task was made, and tell whether the change lasted.

Read the Result

Each check gives one of the results below. Being measured means the first check hasn't come yet. Customers noticed means the finding's share of the feedback dropped clearly, or its NPS rose clearly. No change means customers talk about the finding about as much, and in the same way, as before. Got worse means the share rose clearly, or the NPS fell clearly. Too little feedback means the weeks compared hold too few records to tell, and Kimola gives no verdict yet. Nothing to measure means the Task has no feedback behind it: a Task written in your own words, and the Task of an action whose evidence names no Signal, show it.

A change counts as clear when it passes a statistical test and moves the finding's share by at least a quarter of what it was before, for example from 20% to 15% or less, or its NPS by at least 10 points. A Space that receives a file once a month may need longer before the weeks compared hold enough records, while files added more often fill them sooner.

Tip

Files added to a Space more often fill the weeks compared sooner, so its Tasks show Too little feedback less often.

Example

Four weeks after the Northside service manager marks the Task done, the share of the Space's feedback that the finding covers has fallen from 4% in the four weeks before the Task was made to 2% in the four weeks after it was done, and the Task shows Customers noticed. At the eight-week check the share is still 2%, so the improvement held.

[Screenshot: The DID CUSTOMERS NOTICE? card of a done Task showing Customers noticed]

See All Results Together

Team overview on the Tasks page shows whether customers noticed the Tasks that were done in a period you choose: Last 30 days, Last 90 days or Last 6 months. It also shows who is on what, how many Tasks were made and the median time from made to done. See Use the Team Overview.

Kimola emails the four-week result to the people on the Task and, when the Task follows a Jira issue, writes it to the issue as well. Every Monday, each member with something to read gets a weekly digest of their open Tasks. See Task Emails and Weekly Digest.

When the Problem Comes Back

An improvement doesn't always last. When a later check finds that customers talk about the finding as they did before the Task, the Task says "It came back: customers talk about it as they did before the task." and offers Open it again. Click it to reopen the Task with its evidence and history in place, so the same teammate or another one can pick it up. When the reopened Task is done again, Kimola measures it from the start. The return of a problem is emailed, and written to the Jira issue when the Task has one.

A Task that follows a Jira issue is reopened in Jira, and the Task follows the issue. After that, the loop starts again: the next file brings new Signals, and the next finding becomes the next Task.

Note

A Task that follows a Jira issue is reopened in Jira.

What You Get

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

A finding with evidence. A Signal or a theme of your Space that you checked against its records and the customers' own words.

A Task with an owner. One teammate with a due date and a priority, and the finding's share of the feedback, sentiment and quotes kept as they were the day the Task was made.

The work where your team does it. When your team uses Jira, an issue that carries the finding, linked to the Task, with its status, assignee and due date followed by the Task.

A measured answer. Whether customers noticed at two and four weeks and whether the change lasted at eight and twelve weeks, shown on the Task and across the team in Team overview.

Next Steps

To keep the loop running, add the files of each channel to its Space regularly: every new file runs the Signals again, and the next finding is ready for a Task. See How to Track Customer Satisfaction Over Time for following one channel month after month, and Manage Tasks for the views, search and statuses of your team's Tasks.

Findings come from other places as well. A Space's Action Plan turns its feedback into up to 12 actions, and every action card offers Make a task; see Actions in Spaces and How to Turn Customer Feedback into an Action Plan. A Task of an action is measured when the action's evidence names a Signal. A Customer's page and a Department's page make Tasks too: see What is a Customer? and What is a Department?. For the research that comes before a finding, see How to Find Customer Pain Points and How to Analyze Support Tickets.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.