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

NPS Comment Coding: Codebook for Net Promoter Score Verbatims

Use this codebook on the comments that follow an NPS score question. Each comment gets up to three topic codes, and each code gets a positive or negative tag.

Analyze a transcript free

Use it for

  • An export of NPS responses with the score from 0 to 10 and the open comment.
  • For each response: the date, the plan, the tenure and the customer segment.
  • The previous NPS wave, if you have one, coded with the same codebook.

Steps

  1. Split the responses into three groups

    Sort responses into detractors (0 to 6), passives (7 and 8) and promoters (9 and 10). Code all three groups. Passive comments often name the one problem that keeps a customer from a 9.

  2. Remove empty comments, keep short ones

    Remove blank comments and comments such as "n/a". Keep short comments like "great". Code them as General sentiment, because they show how many people gave no reason.

  3. Give each comment up to three topic codes

    Most NPS comments name one or two topics. Give each topic one code. Stop at three codes, or long comments will count for more than short ones.

  4. Tag each code as positive or negative

    Add a sentiment tag to each code, not to the whole comment. "Easy to use but support is slow" gets Ease of use positive and Support negative.

  5. Compare code rates across the groups

    For each code, calculate the share of detractors and the share of promoters who mention it. A code that is common among detractors and rare among promoters is a likely driver of low scores.

  6. Read the comments behind the top codes

    Before you report a driver, read 10 comments under it. Write what the customers mean in one sentence. "Reliability negative" can mean slow pages for one segment and lost data for another.

Codebook

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

Ease of use

How simple or hard it is to learn and use the product for daily tasks.

Include
The comment says the product is intuitive, simple, clunky, confusing or hard to learn.
Exclude
The comment is about the first setup only. Use Setup and onboarding for that.
Example
“Super easy, my whole team picked it up in a day.”

Core function quality

How well the main function of the product does its job.

Include
The comment judges the quality of the main output, such as its accuracy, results or design.
Exclude
The comment says a function is missing. Use Missing capability for that.
Example
“The forecasts are spot on, better than what our analyst used to do.”

Missing capability

A function, option or integration that the customer wants and that the product does not have.

Include
The comment names something to add, or says the product cannot do a task.
Exclude
The function exists but fails or is slow. Use Reliability or Speed for that.
Example
“Would be a 10 if I could export to PDF.”

Reliability

Whether the product works without bugs, outages or data errors.

Include
The comment mentions crashes, errors, downtime, lost work or wrong data.
Exclude
The product works but is slow. Use Speed for that.
Example
“It keeps logging me out and I lose what I typed.”

Speed

How fast the product loads, responds and finishes tasks.

Include
The comment says the product is fast, slow, laggy or takes too long to load.
Exclude
The comment is about how fast a person replies. Use Support for that.
Example
“Loads in a second even with all our projects in it.”

Support

The help that the customer got from the support team or account manager.

Include
The comment mentions response time, how helpful a person was, or a named support agent.
Exclude
The comment is about help articles or in-product tips. Use Setup and onboarding for that.
Example
“Anna from support fixed my problem in ten minutes on a Sunday.”

Price and value

The customer's view of the price, or of the value they get for the price.

Include
The comment mentions cost, plans, discounts, or says the product is worth or not worth the money.
Exclude
The comment is about a billing error or an invoice task. Use Account and billing admin for that.
Example
“Great tool but the price went up again and it is hard to justify.”

Setup and onboarding

The experience of starting with the product: setup, import, tutorials and help articles.

Include
The comment mentions the first days, importing data, the tour or the documentation.
Exclude
The comment is about ease of use after the first days. Use Ease of use for that.
Example
“Importing our old data took two weeks and three support calls.”

Integrations

How the product connects with other tools that the customer uses.

Include
The comment names another tool and how well the product works with it.
Exclude
The comment asks for a new integration that does not exist. Use Missing capability for that.
Example
“The Slack connection is the best part, everyone sees updates without logging in.”

Account and billing admin

Tasks to manage the account: invoices, seats, payment methods, permissions and cancellation.

Include
The comment mentions a billing mistake, a hard way to add users, or trouble to change a plan.
Exclude
The comment is about the price level. Use Price and value for that.
Example
“Took me forever to find where to download invoices.”

General sentiment

A comment that gives a feeling about the product but no reason.

Include
The comment is only praise or complaint with no topic, such as "love it" or "meh".
Exclude
The comment has a feeling and a topic. Code the topic and tag the sentiment.
Example
“Love it!”

Not about the product

A comment about something outside the product, or about the survey itself.

Include
The comment is about the company in general, the survey frequency, a sales email or another product.
Exclude
The comment is about a person in support or account management. Use Support for that.
Example
“Stop sending me this survey every month.”

Report outline

  1. The score and the number of comments in each group, compared with the last wave.
  2. Drivers of low scores: codes that detractors mention much more often than promoters, with quotes.
  3. Reasons for high scores: what promoters value, so the team does not change it by accident.
  4. What keeps passives from a 9: the top negative codes among scores of 7 and 8.
  5. Changes since the last wave: codes that grew or fell, and the product changes that can explain them.
  6. Actions, each linked to one code and one owner.

Mistakes to avoid

  • Do not report the share of all comments for each code. Compare detractors with promoters, or you will not see what moves the score.
  • Do not tag the whole comment as positive or negative. Many comments praise one thing and criticize another.
  • Do not change the codebook between waves without recoding the old wave. If you do, the trends are not comparable.
  • Do not treat a code with five comments as a driver. Read the comments and call it a signal to check, not a finding.

Guides that use it

Questions

Code each comment with topic codes and a sentiment tag. Then compare how often detractors and promoters mention each code. The codes with the largest gap are the likely drivers of the score.

Yes. Passives gave a 7 or 8, so they like the product but something holds them back. Their comments often name the most fixable problem.

Yes, but check it. Give the model this codebook with the include and exclude rules. Then code a sample of 50 comments by hand and compare. Fix the rules where the two differ.

Pick the top driver of low scores and interview 8 to 10 detractors about it. A comment shows the topic, and an interview shows the cause.

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