Explain satisfaction over time
Read NPS or CSAT with the customer’s service stage and original comments. Compare themes and segments alongside the score, checking question versions and response coverage.
See what may explain the score change.Customer Experience
Your customers checked in.
What happened next?
Collect check-ins, service notes, documents and follow-up throughout the customer relationship. Connect them with a consistent customer ID, understand what changed and prepare a Decision Brief with sources.
WHO IT’S FORCustomer success and service operations leaders collecting recurring feedback across teams, locations and delivery partners.
WHEN IT MATTERSYour team collects check-ins but rebuilds spreadsheets to explain cancellations, repeated issues and incomplete follow-up.
The question behind the workflow
Which concerns returned after follow-up—and what happened to those accounts?
Read the feedback, action and later result together.
Illustrative workflow · adapt the sources, analysis and access to your team.
A continuing recordILLUSTRATIVE
DAY 30A concern is reported
Keep the score and original comment together.
DAY 45An action is completed
Preserve the owner, action and date.
DAY 60The concern returns
Review the later response against the earlier action.
DAY 90An outcome is recorded
Check retention, cancellation and observation coverage.
Three decisions to support
Understand the change.
Keep the evidence close.
Close the loop while the context is fresh
Apply your criteria as a response arrives. AI can suggest issue type and urgency; agreed routing rules direct it for review. Keep the next interaction on the same customer record.
Give each concern an owner and a follow-up.Prepare a decision the team can examine
Draft a Decision Brief across scores, comments and follow-up. Include supporting records, conflicting signals, missing evidence and a next step for your team to review.
Review the answer and its evidence.Use persistent Contact IDs where feedback is identified and permitted. Review uncertain matches; keep anonymous feedback unlinked.
How the workflow runs
One workflow.
A record that keeps growing.
Choose a stage to explore its data, context and next decision. Examples use illustrative data.
01
Collect
Collect the missing part of the story.
Gather check-ins, interviews, service notes and relevant documents through the relationship. Keep source, date and service episode attached.
Illustrative recordA score and a concern
The rating is positive. The comment still describes a service problem.
02
Connect
Follow the customer across service episodes.
Connect agreed service and cancellation exports to the feedback you collect. Review uncertain identities before linking their histories.
Illustrative recordOne continuing record
A location transfer or second service episode should not overwrite the earlier history.
03
Understand
Read new evidence against what came before.
AI can identify recurring themes across comments, notes and follow-up. Review the source evidence alongside the scores.
Illustrative recordDid the concern return after the fix?
Work marked complete is different from confirmation that the experience improved.
04
Follow up
Make the next check-in count.
Collect missing follow-up and record the owner, action date and customer response. Keep unanswered check-ins visible.
Illustrative recordNo response is still no response.
Distinguish eligible customers, respondents and incomplete observation windows.
05
Learn
Investigate retention with the history in view.
Compare equivalent cohorts and service types. Read earlier feedback alongside later retention or cancellation events, with dates and sources available.
Illustrative recordWhich concerns preceded cancellation?
A pattern supports investigation; it does not establish that a concern or intervention caused the outcome.
From source to decision
From a single response
to a Decision Brief.
Set your collection fields and identity rules. AI analysis adds structure while keeping the original evidence available for review.
Read the evidence
Analyze a specific answer or field while preserving its original source.
Understand the response
Read the response with its record history. Suggest categories and review flags.
Compare a measure
Examine the same question or metric across records, retaining scale and version.
Synthesize the decision
Bring measures, themes and history into a Decision Brief with sources.
Decision Brief
Which concerns may explain the score change, and where is follow-up missing?
Focus
Investigate recurring setup problems in one service cohort.
Interpretation to review
Scores and later comments point to a concern worth reviewing together.
Evidence
Check-ins, approved service notes and follow-up responses.
Limits
Response coverage differs between periods; the pattern does not establish causation.
Next step
Review affected records, confirm the service owner and collect the missing follow-up.
Inspect the evidence trail
Illustrative brief. Review each finding against the permitted source record, collection date and relevant definition.
The record behind the answer
Keep the relationships.
Keep the meaning.
01Customer + service episode
02Check-in + source date
03Action + later feedback
04Outcome + observation window
Source and time · Shared definitions · Permitted identity · Appropriate access
Your data dictionary
Agree the fields.
Preserve their meaning.
A starting point to adapt with your data owner.
| Record | Fields to agree | Rule that preserves context |
|---|---|---|
| Identity | Customer ID, account, service episode, location, effective dates | Keep multiple episodes; review uncertain matches. |
| Sources | Check-in stage, original text, document, event date, received date | Distinguish a late upload from a new event. |
| Measures | Question version, scale, service type, cohort, response status | Compare equivalent questions and show nonresponse. |
| Follow-through | Concern, owner, action date, customer confirmation | Separate action completion from confirmed recovery. |
| Outcome | Retention status, cancellation date, observation cutoff | Exclude not-yet-eligible records from full-window comparisons. |
| Access | Role, client or region, purpose, retention rules | Apply access rules to sources, answers and exports. |
Keep learning
Practical guides for your next step.
Read scores and comments together
Keep original evidence, question definitions and response coverage in view.
Read the guide ↗FAQ
Before you get started
Do we need more than satisfaction scores?
A score shows one part of the relationship. Connect permitted check-in feedback with service events, follow-up and later outcomes to investigate what changed and what the evidence can explain.
Can we ask about the same customer over time?
Use an agreed identifier to connect identified responses and relevant service records across time. Keep the collection date, question definition and outcome window attached so comparisons remain interpretable.
Does a recurring issue prove the cause of a cancellation?
No. Linked feedback and outcomes can reveal patterns for investigation. Review timing, response coverage and other explanations before making a causal claim or deciding an action.