Gorgias logo
Gorgias logo

All articles

Measure helpdesk performance: Ticket attributesUpdated an hour ago

Who can use this feature?

 
All roles can view this report — only admins and agents can save filters or add a chart to a dashboard
 
Can be used with any connected store

The Ticket attributes report shows what your customers are contacting you about. It ranks ticket volume by intent, tag, and ticket field value, and shows how those volumes move over time, so a rising contact reason becomes a product or ops fix instead of a hunch.

Open the Ticket attributes report

When you select the Overview category from the menu, you can access the Ticket attributes report from the third tab along the top of the page.

  1. From your helpdesk, select  Analytics in the product switcher at the top of the left sidebar.
  2. In the menu, locate  Helpdesk performance, then click Overview.
  3. At the top of the page, click the Ticket attributes tab.

Charts

The Ticket attributes report has no metric cards. Everything in it measures ticket volume, sliced by one of three attributes:

  • Intents are the contact reasons Gorgias detects on a ticket. They are hierarchical, so a ticket carries a top-level intent and can carry two further levels of detail beneath it. Tickets with no detected intent are grouped under No Assigned Intent.
  • Tags are the labels your team and your rules apply to tickets.
  • Ticket field values are the values of one ticket field you choose.

The report contains two types of charts to help you visualize your data. The first chart ranks values from most to least used on a bar chart, and the second graphs volume over time on a trend chart, stacked by value. The following attributes can be displayed in each chart:

Ticket attributes
• Intents
• Tags
• Ticket field values
Ticket attributes over time
• Intents
• Tags
• Ticket field values

Change what each chart displays

You can change the data that each chart shows in the report by selecting from the attributes listed above.

  1. From the Ticket attributes report, scroll to the Charts area.
  2. Click the title at the top of either chart.
  3. Select an attribute from the dropdown menu.
Note: Ticket field values only appears once you've chosen a ticket field. Click the Ticket Field filter at the top of the page and select the field you want to report on.
Tip: Compare the two charts before acting. A contact reason that's big but flat is a cost to design out; one that's smaller but climbing week over week is usually a new problem worth investigating now.

Compare performance in the breakdown table

The Performance breakdown table at the bottom of the Ticket attributes report allows you to see how each value contributes to your overall ticket volume. You can use the buttons at the top of the table to switch between three breakdowns:

Intents shows the three intent levels side by side, so you can see not just that "Returns" is your biggest reason, but which specific return problem drives it:

• Intent L1
• Intent L2
• Intent L3
• Tickets
• Share of total
• Trend

Tags compares volume per tag:

• Tickets
• Share of total
• Trend

Ticket field values compares volume per value of the ticket field you selected in the Ticket Field filter:

• Tickets
• Share of total
• Trend
Tip: Add the Satisfaction score filter at the top of the page and open the Intents table to find which contact reasons produce your worst ratings.

Show or hide metrics in a table

All of the metrics listed above can be added as a column to the table.

  1. In the Performance breakdown section, select a performance breakdown table.
  2. Click Edit table.
  3. Click the toggle to add or remove a column.
  4. Drag the rows to order more important metrics first.
  5. Click Save.

FAQ

Why is the Ticket field values option missing from the chart?

Because no ticket field is selected. Pick one in the Ticket Field filter at the top of the page and the option appears in both charts and in the Ticket field values table.

What does "No Assigned Intent" mean?

Those are tickets where no intent was detected. A large share usually means a lot of your volume arrives through channels or in formats where intent detection didn't apply, so treat the rest of the intent distribution as a sample rather than the whole picture.

Why do the shares in a table add up to more than 100%?

A ticket can carry more than one tag, so tag shares can overlap. Intent levels don't overlap in the same way, because each ticket carries one intent path.

Was this article helpful?
Yes
No