How to Analyze Support Tickets

min read - Updated on Nov 17, 2026

You can analyze support tickets with Kimola by turning them into a Report that shows what customers contact support about, how they feel about each topic and which topics perform worst. You connect Zendesk or Intercom, or upload an export of your tickets, and Kimola labels every ticket with a theme and a sentiment. The Performance page then ranks the themes by Dissatisfaction Score, and an Action Plan turns the findings into up to 12 evidence-checked actions for your support and product teams. This guide takes you from the connection to the plan.

The Goal

Support tickets hold feedback that customers write without being asked, and most of it stays in the helpdesk. The questions behind this guide come from the people who run support and customer experience: what do customers contact us about, which topics make them most negative, and what should we change first. Kimola answers them from the tickets themselves, so nobody has to tag tickets by hand or read them one by one.

The result is a Report you can return to. Every theme in it stays tied to the tickets behind it, so a number on a chart always leads to the customer words that produced it. For more on how Kimola works with support and call conversations, see Conversation Analysis.

What You Need

You need your tickets in a form Kimola can read, and a paid package if you want Kimola to read them straight from your helpdesk. The Zendesk and Intercom integrations are available in the paid packages (Basic, Standard, Business and Enterprise), not in Starter, and Kimola On-Premises doesn't offer them. See kimola.com/pricing for the packages.

For Zendesk, you need your Zendesk subdomain and an account that can see the tickets you want to analyze. For Intercom, you need an Intercom sign-in that lets you allow Kimola to access your workspace.

If your tickets live in another helpdesk, or you run Kimola On-Premises, export them to a spreadsheet and upload the file instead, in any package. Kimola accepts .xls, .xlsx, .csv and .tsv files, one file at a time, up to 30 MB. You choose the column that holds the ticket text and, when the file has one, a date column. See Create a Report by Uploading a Custom Dataset. From Step 2 on, the guide applies to an uploaded file as well.

Step 1: Connect Zendesk or Intercom

Choose the integration that matches your helpdesk. You can start either connection from Reports, in the Integrations row under the upload area, or from ACCOUNT › Integrations, where each integration is listed under AVAILABLE until it is connected. A connected integration moves to ACTIVE, and its icon on Reports turns green.

The two integrations read different things. Zendesk gives Kimola the whole ticket: its description followed by every comment, with the date the ticket was created. Intercom gives Kimola the first message of each conversation, without a date. Zendesk suits an analysis that needs the replies of your team and the change of topics over time. An Intercom Report shows what customers write about when they open a conversation.

Tip

The connection belongs to your team's Kimola account, so your teammates don't need to connect again to create Reports from the same helpdesk.

Connect Zendesk

Click Zendesk in the Integrations row on Reports. In the Zendesk Support window, type your subdomain in Sub Domain, without "https://" and ".zendesk.com": acme for https://acme.zendesk.com. Click Connect. Zendesk opens its authorization page in a new window. Sign in if it asks you to and allow Kimola to access your account. Kimola requests read access only: it never answers, changes or closes a ticket.

Note

Zendesk's authorization page opens in a new browser window, so allow pop-ups for app.kimola.com.

When you allow access, the window closes by itself and Zendesk appears under ACTIVE on the Integrations page. See Connect Zendesk to Kimola for the full connection, including what to do when Kimola can't find your subdomain.

[Screenshot: The Zendesk Support window with the Sub Domain field and the Connect button]

Connect Intercom

Click Intercom in the Integrations row on Reports. Intercom's authorization window opens as a pop-up. Sign in to Intercom if it asks you to, and allow Kimola to access your workspace. The window shows "The token has been successfully saved" and closes by itself, and Intercom moves to ACTIVE on the Integrations page. If the window shows an error instead, close it and start again.

See Connect Intercom to Kimola for the full connection.

Step 2: Create a Report from Tickets

With the integration connected, click it again in the Integrations row on Reports. Kimola reads your tickets and opens them in the report wizard as a dataset: a Tickets sheet for Zendesk, a Conversations sheet for Intercom. From here the wizard is the same one you use for an uploaded file. The choices below are the ones that suit support tickets.

Choose the Columns

The wizard opens on Sheets & Columns, with a preview of the sheet. The Zendesk Tickets sheet has three columns: Content, the whole conversation of the ticket, Date, the day the ticket was created, and Ticket Id, its number in Zendesk. Choose Content as the Text Column and Date as the Date Column, and leave the Url Column empty. With a date, the Report can show how topics change over time. The Intercom Conversations sheet has only Content, so choose it as the Text Column. In an uploaded file, choose the column that holds the ticket text and, if you have one, the column with the ticket date.

Note

Kimola doesn't separate public replies from internal notes, so the internal notes your Zendesk account can see are part of Content. Zendesk's automatic chat transcripts, the comments that contain "Conversation with", are left out.

[Screenshot: The Sheets & Columns step with Content chosen as the Text Column and Date as the Date Column]

Choose Classifiers and Structure

In Classifiers, choose the models that label every ticket. Choose a content classifier and the Sentiment Classifier together: Performance in the next step needs both, because the content classifier gives the themes and the Sentiment Classifier says whether each ticket is positive or negative. The Automatic Classifier is a content classifier that discovers the themes from your tickets, so it needs no setup. If your team already sorts tickets under its own categories, such as billing, shipping and technical problems, a custom model can label them with those categories instead.

[Screenshot: The Classifiers step where Automatic Classifier and Sentiment Classifier models are selected]

In Structure, turn on Enable Multi-label Classification. A single ticket often raises more than one issue, such as a late delivery and a refund request, and multi-label lets Kimola give the ticket both labels. See Create a Report Using Multi-Label Classification.

[Screenshot: The multi-label classification option in the Structure step]

Choose Dimensions

Dimensions are optional research questions that Kimola asks of every ticket, and three of them suit support work. Pain Points asks "What goes wrong or creates difficulty?" and names the recurring problems in customers' own words. Underlying Causes asks "Why does this occur?" and explains what lies behind them. Unmet Needs asks "What is missing or desired?" and collects what customers ask your product or your team to provide. Each Dimension you add multiplies the queries the Report uses. See Add Dimensions to a Report for how to choose them.

[Screenshot: The Dimensions step with Pain Points, Underlying Causes and Unmet Needs chosen]

Review and Create the Report

The Review step shows your choices before anything is analyzed: an optional Report Title, the Report Language, the Dataset and the Required Query. The Report Language is the language the Report is written in: English, Spanish, French, German, Portuguese, Dutch or Turkish. Your tickets can be in any of the 30+ languages Kimola analyzes, whatever the Report Language. See Language Options in Reports.

Note

Analyzing tickets uses queries: one analyzed ticket, multiplied by the number of models and the number of Dimensions. Check the Required Query before you confirm, and see kimola.com/pricing for the queries each package includes.

Confirm to start the analysis. When it is complete, Kimola shows "Here we go!" and View Report opens your Report.

Note

A Report analyzes the tickets Kimola read when you created it and doesn't update itself from your helpdesk. To analyze newer tickets, create a new Report from the same integration.

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

Step 3: See Which Topics Perform Worst

The Report opens on Overview, which shows how many tickets Kimola analyzed, the sentiment of the feedback and the BEST PERFORMING THEMES and WORST PERFORMING THEMES cards. Click the worst performing themes card, or open Performance in the menu of the Report, to see the full ranking. Performance is the page that answers the question of which topics hurt the most, and the rest of this step goes from a topic to the tickets and the causes behind it.

Read the Dissatisfaction Score

Every theme has a Dissatisfaction Score from 0 to 100: its share of negative tickets, statistically adjusted so that a theme with a handful of tickets and a theme with hundreds can be compared fairly. Worst Performing Themes by Dissatisfaction Score lists the themes with the highest score first. A score of 80 to 100 is Critical, because most of the theme's tickets are negative and there are enough of them to be sure. A score of 60 to 79 is Moderate, and a score below 60 is Acceptable. The Satisfaction Score next to it works the other way round and lists the themes customers are happy with, which are the ones to protect.

Example

For an online store, the ranking might put refund delays first with a Dissatisfaction Score of 84, which is Critical, and late delivery, the largest theme by ticket count, second with 66, which is Moderate. A theme with 3 tickets that are all negative can't top the list by chance, because the score takes the number of tickets into account.

The ranking is calculated the same way every time, so the same tickets always give the same scores in the same order. See Performance in Reports for every part of the page.

[Screenshot: The Performance page with Worst Performing Themes by Dissatisfaction Score and their scores]

Narrow the Ranking

Every filter on the Performance page calculates the scores again for the matching tickets only. Choose an answer of a Dimension, such as one of the pain points, to see which themes come with it. Choose a label of another classifier to score the tickets of one kind only. With Zendesk tickets or an uploaded file that has a date, choose a period to see how the ranking looks for one stretch of time and compare it with the period before. These filters work as they do on the Content page, described in Filter Records in Reports.

Read the Tickets and Their Causes

A score tells you where to look, and the tickets tell you what to do about it. Open Content in Reports and filter by the theme's label to read the tickets that earned the theme its score. Open Dimensions to read each Dimension you added: every pain point comes with a summary, the number of tickets behind it and quotes in customers' own words, and the Underlying Causes cluster explains why those problems happen. See Dimensions in Reports.

If the Report has Signals, the Signals page adds the findings Kimola has tested statistically. Trends are the ones that matter most for support: topics whose share of tickets changed in recent periods, so you can catch a problem while it grows. Trends are built from dates, so they come from Zendesk tickets or an uploaded file with a date column, and Intercom conversations don't carry them. See Signals in Reports.

[Screenshot: The Dimensions page of the Report with the Pain Points summary and its largest clusters]

Step 4: Act

The findings become work through an Action Plan: up to 12 actions that Kimola writes from the Report, each checked against the tickets before it reaches you. You start from Actions in the menu of the Report. Action Plans of a Report are available in every package.

Create the Plan

On the Actions page, click Create an action plan. The first step asks who the plan is for. Select your company's Profile or click New profile, type the organization's name and describe in a few words what it does and whom it serves. The description makes the actions specific to you instead of general advice for your category.

The second step, Where do you stand?, shows the side Kimola suggests from the Report. Tickets are feedback about your own product or service, so choose Our own offering: the plan then says what to fix, protect and build on. The third step asks what the plan is for. Choose Customer experience, the goal for onboarding, support, delivery, billing and service. Keep Balanced if you want to see first what the tickets support most strongly.

Under the goals, The situation lets you describe what you are facing in your own words, and Written in sets the language of the plan. The situation is optional, and it helps Kimola write actions that answer your question.

Example

For an online store: "Refund delays and late deliveries went up after we added a second warehouse, and we are planning next quarter's support staffing."

Click Generate the Action Plan. Writing a plan takes about 5 to 7 minutes, and you can leave the page while it works. See Create an Action Plan for every step of the wizard.

[Screenshot: The What is the plan for? step with Customer experience chosen and the situation field filled in]

Read and Rate the Actions

When the plan is ready, the page shows up to 12 action cards. Each card says what to change, for whom and when, who owns it, how confident Kimola is (High, Medium or Low) and How to See It Worked, with the evidence from your tickets behind it. Kimola drops actions that its checks can't support, and a line under the cards says how many it dropped. See Actions in Reports for every part of a plan.

Rate each action with a verdict: Useful, Already known, Too vague, Wrong or Not for us, with an optional note. See Rate Actions in an Action Plan.

Note

When the evidence doesn't back any action firmly enough, Kimola doesn't write a plan and says "No action passed the checks this time". Click New plan and try a narrower goal than Balanced, or describe your situation.

[Screenshot: An Action Plan with its action cards, confidence labels and How to See It Worked]

What You Get

A support-ticket Report gives you the following, all from your own tickets.

Themes with sentiment. Every ticket labeled with the themes it raises and its sentiment, with the number of tickets and the share behind each theme, on Overview and Content.

A ranking of the worst performing topics. The themes ordered by Dissatisfaction Score, adjusted for size, for all tickets or for the segment and period you filter.

Problems and their causes. The pain points, underlying causes and unmet needs customers describe, each with a summary and quotes in their own words.

Changes over time. Trends that show which topics grow or fade, when your tickets carry dates.

An Action Plan. Up to 12 actions with an owner, a confidence level, a metric and the evidence behind each one, rated by your team.

To share the findings with colleagues who don't use Kimola, export the Report as a PDF file or a PowerPoint file.

Next Steps

A Report analyzes the tickets of one moment. To follow tickets as they keep arriving, a Space in the Enterprise package grows file by file and keeps its NPS, themes and Signals current after every file. How to Analyze Call Center Conversations shows that workflow with transcripts, and it applies to ticket exports in the same way.

To put the tickets next to other customer voices, such as app or product reviews, see How to Analyze Product Feedback for Your Roadmap. For the ways Kimola reads support and call conversations, see Conversation Analysis.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.