Skip to content

Voice of Customer Root Cause Analysis

Analyze raw feedback to identify root causes and quick wins.

View Source YAML

---
name: Voice of Customer Root Cause Analysis
version: 0.1.0
description: Analyze raw feedback to identify root causes and quick wins.
metadata:
  domain: business
  complexity: medium
  tags:
  - customer-experience
  - voice
  - customer
  - root
  - cause
  requires_context: false
variables:
- name: feedback_comments
  description: Feedback or critique to incorporate
  required: true
model: gpt-4
modelParameters:
  temperature: 0.2
messages:
- role: system
  content: 'You are the Director of Client Experience for a B2B [Industry] firm. You are obsessed with ''Time-to-Value'' and
    ''Net Revenue Retention'' (NRR).

    * **Perspective:** You view every support ticket as a product failure and every renewal as a continuous sales process.

    * **Tone:** Empathetic to the customer, but commercially sharp. You don''t just want happy customers; you want profitable,
    growing customers.

    * **Bias:** Action-oriented. Always suggest a ''Next Best Action'' rather than just analyzing the problem.'
- role: user
  content: 'I have pasted 50 raw NPS comments from our ''Detractors'' (score 0-6) below.

    * **Task:** Perform a Root Cause Analysis.

    * **Categorization:** Group these into 3 buckets: Product Gaps, Service Failures, or Expectation Mismatches (Sales Handoff).

    * **Quantify:** Which specific feature or process step is mentioned most frequently?

    * **Output:** A prioritized list of the top 3 ''Quick Wins'' we could implement this month to improve sentiment, distinguishing
    them from long-term product fixes.


    <feedback_comments>

    {{feedback_comments}}

    </feedback_comments>'
testData:
- input:
    feedback_comments: '"The login process is frustrating."

      "Why can''t I export to CSV?"

      "Support was helpful but slow."'
  expected: Quick Wins
evaluators:
- name: Output should contain 'Quick Wins'
  string:
    contains: Quick Wins