Skip to content

Use case

Fix the cause, not the score.

CSAT tells you something is wrong after the customer has already had the bad experience. Kaizo reads every conversation and tells you what is causing it while you can still act.

Trusted by global support teams

A score is not a diagnosis

When CSAT dips, the honest answer to “why?” is usually a guess. The survey tells you a customer was unhappy; it does not tell you whether that was a broken process, a product problem, or a skill gap, and those three need completely different responses.

Root cause

Trace the dip to the conversations behind it.

Kaizo separates the systemic from the individual, so you know whether to fix a process, escalate to product, or coach a person.

  • Broken process, product friction or skill gap, named
  • Systemic issues separated from one-off outliers
  • Ask questions in plain language
More about root cause

Sentiment

See frustration before it becomes a survey response.

Sentiment and empathy are scored across every message, so the pattern shows up as a trend rather than as a detractor score.

More about sentiment
13%
annual CSAT increase
100%
of messages scored for sentiment
30%
of the workweek saved on reporting

Support leaders who stopped guessing

  • 50%

    less QA time

    “Our tickets can be long and complex. AI has been a life-saver in our experience.”

    SteelSeries

  • 75%

    faster resolution

    “Kaizo is an essential part of finding the root causes of areas we need to improve, then improving on that.”

    Foot Locker

How it works

From a CSAT dip to its cause, in three steps

A survey hears from the customers who choose to answer. QA reads the conversations themselves, which is where the reason for the score sits.

  1. Read every conversation

    Kaizo scores every conversation, including those from customers who churn quietly rather than fill in a survey, so the picture is not limited to the people who replied.

  2. Name the cause

    Root cause analysis separates a broken process, product friction and a skill gap, and tells systemic issues apart from one-off outliers.

  3. Send it to the right owner

    Fix the process, escalate to product, or coach the person, with the conversations behind the dip attached as evidence.

Read more on root cause analysis in customer service, whether QA actually improves CSAT and what bad customer service reviews can teach you. The causes are tracked in Insights & Analytics.

Results

CSAT at teams that run Kaizo

  1. Foot Locker Europe

    13% CSAT increase, alongside 75% faster resolution.

  2. GAMING1

    CSAT up from 70.45% to 77.65%, while ticket processing doubled.

Their own numbers, from their stories: Foot Locker and GAMING1.

FAQ

Frequently asked questions

We already run CSAT surveys. What does this add?

Surveys capture the customers who respond, after the fact. Kaizo reads every conversation, including the ones from customers who churn quietly rather than filling in a survey.

How quickly do we see a trend?

As soon as there is enough volume behind it. Because coverage is complete, a pattern reaches significance far faster than it would from a 3% sample.

Why can't our CSAT survey tell us why the score dropped?

Because it only hears from the customers who answer, and it records how they felt rather than what happened in the conversation. QA reads the conversation itself, so it can show whether a process, the product or an answer pulled the score down.

Where do we start when CSAT drops?

With the conversations behind the dip. Kaizo lets you trace a falling score to the conversations behind it and see whether the cause is systemic or a one-off, so you fix the right thing first.

Security & compliance

SOC 2 Type II, ISO 27001 and GDPR

Audit reports, certificates and policies in one place.

Trust Center ›

Find out what is actually moving your CSAT

We will show you in a live demo how Kaizo finds the causes behind CSAT numbers.

Trusted by global support teams

  • Foot Locker
  • Canva
  • GetYourGuide
  • Instacart
  • BlaBlaCar
  • UiPath