The first 3 interviews are free · Start free or see the prices

Support Ticket Analysis: Contact Reason Codebook

Use this codebook to code support tickets, chats and support emails by contact reason. Then tag each ticket as preventable or not, so the product team sees which tickets it can remove.

Analyze a transcript free

Use it for

  • An export of tickets for a fixed period with the subject, the first customer message and the resolution note.
  • The tags and categories that agents set, if any, so you can compare them with your codes.
  • For each ticket: the plan, the account age and the product area, where your help desk records them.

Steps

  1. Take a random sample

    If you have more than 500 tickets in the period, take a random sample of 300 to 400. Do not take the newest tickets only. One bad release can fill a week of tickets.

  2. Code the first customer message

    Code the reason the customer first gave for the contact, not the reason the agent found later. Write the agent's finding in a separate field. The gap between the two shows where customers misread the product.

  3. Give each ticket one contact reason

    A ticket gets one code. If the customer asks two unrelated things, split it into two records. Agent tags are often wrong or missing, so do not copy them.

  4. Tag preventability

    For each ticket, add one of three tags: preventable by product, preventable by help content, or not preventable. A how-to question about a hidden setting is preventable by product.

  5. Add the product area

    Record the area of the product the ticket is about, for example billing, import or reports. Count codes per area to find the area with the most preventable tickets.

  6. Read the resolution notes for the top codes

    For the 3 most common codes, read 15 resolution notes each. Write down the fix that agents repeat. A repeated fix is a candidate for a product change or a help article.

Codebook

Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.

How-to question

The customer asks how to do something that the product can already do.

Include
The customer cannot find a function or does not know the steps, and the function works.
Exclude
The function works as designed, but the customer expected a different result. Use Works as designed for that.
Example
“How do I add a second admin to our workspace?”

Defect

The product does not work as designed and the agent confirms a bug.

Include
The customer reports an error or a wrong result, and the agent confirms or escalates it as a bug.
Exclude
The agent finds that the product behaves as designed. Use Works as designed for that.
Example
“The CSV export has every date one day off since yesterday.”

Works as designed

The customer reports a problem, but the product behaves as designed and the customer expected something different.

Include
The agent explains that the behavior is intended, such as a limit or a default the customer did not know.
Exclude
The customer asks for the behavior to change in the future. Use Feature request for that.
Example
“Why did my archived projects disappear from search? I need to find them.”

Account access

The customer cannot sign in or reach their account.

Include
The ticket is about passwords, two-factor codes, single sign-on, locked accounts or email changes.
Exclude
The customer can sign in but cannot see a page because of their role. Use Permissions and roles for that.
Example
“My authenticator app was on my old phone and now I am locked out.”

Permissions and roles

The customer cannot see or do something because of user roles or access settings.

Include
The ticket is about who can view, edit, invite or approve, inside an account the customer can reach.
Exclude
The customer cannot sign in at all. Use Account access for that.
Example
“My manager says she shared the folder but I still get access denied.”

Billing and plan change

A question or problem about charges, invoices, refunds, plan upgrades or downgrades.

Include
The ticket is about money, an invoice, tax details, a card that failed or a change of plan.
Exclude
The customer wants to close the account. Use Cancellation for that.
Example
“We were charged for 12 seats but we only have 9 users.”

Data import and export

Problems with moving data into or out of the product.

Include
The ticket is about uploads, file formats, import errors, mapping fields, or exports that fail or look wrong.
Exclude
The data moves through a connection to another tool. Use Integration setup for that.
Example
“The import says row 1 has an invalid header but it looks fine to me.”

Integration setup

Problems with connecting the product to another tool or keeping that connection working.

Include
The ticket names another tool, an API key, a webhook or a sync that does not connect or stopped.
Exclude
The customer asks for a connection to a tool that is not supported. Use Feature request for that.
Example
“Our HubSpot sync stopped on Monday and new contacts do not come through.”

Feature request

The customer asks for a function or change that the product does not have.

Include
The customer says what they want added or changed, and the agent confirms it is not available.
Exclude
The function exists and the customer did not find it. Use How-to question for that.
Example
“Can you add a way to schedule a report to send every Monday?”

Cancellation

The customer wants to cancel, close the account or delete their data.

Include
The customer asks to cancel, to stop renewal, or to delete the account or personal data.
Exclude
The customer wants a lower plan but will stay. Use Billing and plan change for that.
Example
“Please cancel our subscription at the end of this term and delete our data.”

Report outline

  1. Volume and period: the number of tickets, the sample size and how you sampled.
  2. Contact reasons by count, with the share that is preventable by product and by help content.
  3. Top product areas by preventable tickets, each with the repeated fix that agents give.
  4. Works as designed tickets: the expectations that the product does not meet, and where the design could change.
  5. Differences between agent tags and your codes, if you use agent tags for reporting today.
  6. Recommended changes, each with the expected drop in tickets and the owner.

Mistakes to avoid

  • Do not trust agent tags as the analysis. Agents tag fast at the end of a ticket, and tags drift over time.
  • Do not code the agent's diagnosis as the contact reason. Code what the customer asked. The gap is a finding.
  • Do not mix how-to questions with defects. One needs a design or help change. The other needs a bug fix.
  • Do not report only volume. A small code with long resolution times can cost more support hours than the largest code.

Guides that use it

Questions

Give each ticket one contact reason from a fixed codebook, based on the first customer message. Then add a preventability tag and the product area.

A ticket is preventable when a product change or a help article would have stopped the contact. How-to questions and works as designed tickets are often preventable.

A random sample of 300 to 400 tickets is usually enough to find the main contact reasons. Code more if you need counts for each product area.

Tickets show what went wrong and how often. Interviews show why. Pick the top preventable code and interview customers who opened that kind of ticket.

Ask real people your question

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Start free