A SaaS customer escalated after three months of double billing, two prior agents who deflected without resolving anything, and a tangible cash-flow impact. They opened the call threatening to leave and post publicly, and were looking for a clear refund commitment and an explanation.
Company protection instincts took over at every decision point, leaving the customer with nothing resolved and a stronger case for leaving.
Across four moments — the opener, the agent defence, the refund hedge, and the close — the instinct was to manage the company's image rather than the customer's problem. The billing explanation before any acknowledgement, the 'subject to review' language on a three-month overcharge, and the vague close all sent the same signal: the company's exposure mattered more than the customer's harm. That signal is precisely what drives churn and public posts — not the original error, but the feeling that escalating made no difference.
The opener moved straight to explaining billing complexity before acknowledging what the customer had been through — a move that raised the temperature rather than lowered it, because it signalled that the company's narrative mattered more than their experience.
The customer communicated three distinct things: a financial harm, a betrayal of trust by two prior agents, and a desire for certainty. The responses addressed none of those specifically — they addressed the company's position on each.
The 'subject to review' and precedent concern on a three-month double-billing overcharge — a verifiable, company-caused error on a customer threatening to churn — shows judgement calibrated to the wrong risk. The reputational and retention cost of not committing to the refund was far larger than any precedent risk.
The close left the customer with no named owner, no committed timeline, and no refund confirmation — which means the call ended in exactly the same place as the two prior agent interactions. From the customer's perspective, escalating made no difference.
Self-awareness was present throughout — at every decision point there was accurate recognition of what the instinct was and why it was problematic. That level of honest self-observation is the foundation any development work needs.
The instinct to explain the billing system, while poorly timed, does reflect genuine product knowledge — the raw material for a good explanation exists, it just needs to be deployed after acknowledgement, not before.
Explaining billing complexity before acknowledging the customer's experience at the opener actively raised the temperature — repeating language the customer had already rejected from two prior agents signalled this call would follow the same pattern.
Defending prior agents with 'I'm sure they were trying to help' directly contradicted what the customer reported experiencing, which is a form of telling the customer they are wrong about their own experience.
Hedging a refund on a verified, company-caused billing error with 'subject to review' and precedent language applied the wrong risk frame — the reputational and churn cost of not committing was larger than any precedent risk.
Under-acknowledging the cash-flow harm because 'admitting it feels like liability' filtered out the most important element of the customer's complaint before it could be reflected back.
Closing with 'we'll get back to you' and no named owner replicated the outcome of both prior agent interactions — from the customer's perspective, the escalation changed nothing.
Accurate self-diagnosis in real time
At each decision point you named your own instinct and identified why it was working against the customer — 'I'd be managing my company's image more than the customer's actual problem.' That precision is not common and it means the gap between what you know and what you do is the thing to close, not the knowledge itself.
Product and process knowledge
The impulse to explain the billing system reflects genuine understanding of why the error happened. That knowledge is useful — it just needs to be deployed after the customer feels heard, not as the opener.
Acknowledge before explaining
The billing system explanation came before any acknowledgement of the customer's experience — the exact sequence most likely to signal that the company's narrative takes priority over the customer's harm.
Why it mattersAt manager level, escalations arrive because the customer already believes the company is not listening. An opener that explains rather than acknowledges confirms that belief immediately. The window to change the tone of the call is the first 60 seconds.
Own the team's failure without defending it
'I'm sure they were trying to help' in response to a customer saying two agents did nothing is a direct contradiction of their reported experience. It signals that protecting the team matters more than acknowledging what happened to the customer.
Why it mattersOwning a failure does not mean throwing prior agents under the bus — it means saying 'that should not have happened and I'm sorry it did' without adding a qualifier that walks it back. The qualifier is what the customer remembers.
Commit to what is already owed
Hedging a refund on a verified, company-caused billing error with policy language applied the wrong risk frame. The customer was not asking for an exception — they were asking for their own money back.
Why it mattersIn a churn-and-post scenario, the cost of not committing to a clear, verifiable remedy is higher than the cost of committing to it. 'Subject to review' on a three-month double-charge signals that the customer might not get back what is already theirs — and that is the statement most likely to end up in a public post.
Close with a named owner and a specific date
'We'll get back to you' with no owner and no timeline replicated the outcome of both prior interactions. From the customer's perspective the escalation changed nothing.
Why it mattersA manager-level close on an escalation must be qualitatively different from an agent-level close. That difference is made concrete by naming who will do what by when — not by seniority alone.
Risk framing defaults to company exposure rather than relationship exposure — even when relationship exposure is the larger risk
The precedent concern on a verified overcharge and the liability concern about acknowledging cash-flow harm both applied a risk frame focused on what the company might have to concede, not on what the company stood to lose by not conceding. In a churn-and-post scenario those are not equal risks.
The instinct to protect the team reads to the customer as the instinct to protect the company from accountability
Defending prior agents with 'I'm sure they were trying to help' was a loyalty instinct — but from the customer's side it was indistinguishable from the company telling them their experience was wrong. The intent and the effect were opposite.
Every decision point in this simulation was shaped by the same underlying pattern: the company's narrative arrived before the customer's experience was named. That sequencing determined the outcome of the opener, the agent defence, the refund hedge, and the close. It is the single lever that, if moved, changes the temperature of every escalation before any other skill is applied.
On the next escalation call, write down the customer's stated harm — in their words — before you say anything. Read it back to them verbatim as your first sentence. Then pause. Do not explain, justify, or qualify until they respond.
The opener set the outcome — billing complexity before acknowledgement put this call on the same track as the two prior agent calls.
The customer had already rejected that framing twice. Repeating it as the escalation opener confirmed the pattern rather than breaking it, and the customer's rising voice in response showed it had that effect immediately.
Defending prior agents contradicted the customer's reported experience — which is a harder trust breach than the original billing error.
'I'm sure they were trying to help' in response to a specific account of being fobbed off tells the customer that the company's version of events takes priority over theirs — and that is the core complaint underneath the billing complaint.
The precedent concern was applied to a case where the customer was already owed the money — that is not a precedent situation.
Precedent risk applies when a customer asks for something outside what they are owed. On a verified three-month overcharge the customer is owed the refund; hedging it with policy language reframes a debt as a favour, which is the most likely trigger for the public post they threatened.
The close was functionally identical to the two prior agent closings — from the customer's perspective, the escalation changed nothing.
No named owner, no committed timeline, and no refund confirmation meant the call ended where it started. The customer's threat to post that evening became more likely, not less, after the escalation.
The gap is not knowledge — it is the distance between what you diagnosed and what you did.
At every decision point you accurately named your own instinct and identified why it was working against the customer. The development task is closing the space between that diagnosis and the action in the moment.
What this is: A structured assessment produced through guided conversation with Ren, Renatus's AI analyst, in a live simulation. Observations come from specific moments in the conversation, not from a psychometric test.
What’s in it: An overall read, dimension-by-dimension scores with evidence, and recommended next steps tailored to your patterns.
Go deeper: See Foundation for the frameworks Ren draws on, Methodology for how each score was calculated, and the Honesty Statement for how to interpret and use these results responsibly.
These are the named frameworks Ren draws on when interpreting your responses. They shape how evidence is read, not how it is scored.
The phenomenon where a well-handled complaint can produce stronger loyalty than if the failure had never occurred. Tests whether recovery moves built trust or merely closed the issue.
A generic service-recovery construct — recognising the complaint, acknowledging the customer's experience, taking responsibility, resolving the issue, and learning from the cause. Used as a calibration reference for whether the response covered the full arc, not as a script. Grounded in established service-recovery research, including the service-recovery paradox (McCollough & Bharadwaj, 1992).
Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.
Each scored dimension has a published rubric with five behavioural anchors at 90, 70, 50, 30, and 10 — each describes what someone operating at that level visibly does. Ren reads the evidence in the conversation against these anchors and assigns a score from 0 to 100. The anchor numbers mark the threshold of each level: your score sits at or above the highlighted anchor and below the next one up. The band the score falls within is highlighted on each rubric below. Read the full methodology →
The structured recovery arc — acknowledge, understand, act, follow up — used in service recovery research holds that the temperature of a complaint exchange falls when the customer feels heard before the company responds. Scored on whether the subject lowered the temperature before defending or resolving.
Lowered the temperature before responding to content. Acknowledged the customer's experience in its own terms, without minimising or defending. The customer's posture visibly shifted before any solution was discussed.
De-escalated effectively in most of the exchanges. Occasionally moved to resolution one beat before the customer was ready, but read the signal and stepped back when the temperature didn't drop.
De-escalation tools were present but applied inconsistently. The subject acknowledged the easier complaints well and defended on the harder ones. Temperature rose in places it needn't have.
Defended before acknowledging. The subject's first instinct was to correct the customer's framing or explain the company's position. Temperature stayed high through most of the scenario.
Escalated rather than de-escalated. The subject's responses raised the temperature further — through defensiveness, dismissal, or mismatched tone — and the customer left the exchange in a worse state than they entered it.
The structured recovery arc treats listening not as a preliminary courtesy but as the substantive first act: customers signal whether they have been heard by what the responder reflects back. Scored on the evidence in the subject's responses that they had actually heard the complaint.
Reflected back the substance and the feeling of the complaint in the customer's own terms, including the parts that were uncomfortable. Asked questions that surfaced what the customer had not yet said. The customer felt heard before they felt fixed.
Listened well in most exchanges. Occasionally paraphrased into company language rather than the customer's, but caught and adjusted when the customer's response indicated the paraphrase had lost something.
Heard the headline complaint but missed the secondary one underneath it. Responses addressed what the customer said first more than what they actually wanted resolved.
Listened to respond rather than to understand. Replies were prepared before the customer had finished. Significant elements of the complaint went unacknowledged.
Did not listen meaningfully. The subject's responses were templated and disconnected from the specific complaint. The customer would have received the same reply regardless of what they said.
Service recovery research (Smith, Bolton & Wagner 1999; Hart, Heskett & Sasser 1990) shows that skilled recovery judgement balances the cost of the remedy against the lifetime value and goodwill implications, and distinguishes the cases that warrant exception from those that don't. Scored on the subject's calibration.
Judged each case on its specifics. Held the policy line where it mattered, made the right exception where it didn't, and could articulate the reasoning for both. The subject's discretion was used deliberately, not indiscriminately.
Judgement was sound across most cases. Occasionally extended a remedy slightly larger than the case warranted, or held a line slightly harder than it needed to be held, but the calibration was close.
Judgement defaulted to one mode — either consistently generous or consistently strict — regardless of case specifics. The reasoning for any given decision was harder to articulate than the decision itself.
Judgement was reactive to the volume of the customer's pressure rather than to the merits of the case. The loudest customers received the most; the quieter ones with stronger cases received less.
Judgement broke down. Either over-applied the policy to the point of damaging the relationship or over-conceded to the point of training future behaviour. Discretion was used without discernment.
The Service Recovery Paradox (McCollough & Bharadwaj 1992) is that well-handled complaints can leave the customer more loyal than if nothing had gone wrong. Scored on whether the subject's resolution actually delivered that recovery — close the loop, make whole, follow up.
Closed the loop fully. Resolved the immediate issue, made the customer whole in a way proportionate to the breach, and set a follow-up the customer could rely on. The exchange ended with the relationship stronger than it began.
Recovered the situation well. Resolution was timely and proportionate; follow-up was named but slightly less specific than it needed to be. The customer left satisfied, not delighted.
Resolved the surface issue without addressing what made it sting. The customer was placated rather than recovered. Follow-up was implied rather than committed to.
Resolution was partial. Either the substantive remedy or the emotional repair was missing. The customer would leave the exchange unconvinced the issue had been taken seriously.
No effective recovery. The complaint was processed rather than resolved; the customer left in a worse position than they would have been had they not complained. The Service Recovery Paradox operated in reverse.
Each dimension is scored continuously 0–100 and combined using the weights below to produce the overall. Dimensions that carry more of the skill's outcome are weighted higher; dimensions that are enabling inputs or secondary qualifiers are weighted lower.
| Dimension | Score | Weight | Weighted |
|---|---|---|---|
| De-escalation | 22 | 25% | 5.5 |
| Listening | 28 | 20% | 5.6 |
| Judgement | 28 | 25% | 7.0 |
| Recovery | 18 | 30% | 5.4 |
| Overall | 24 | — | — |
This assessment is a structured analytical tool, not a clinical diagnostic. Results reflect patterns in your responses and should be interpreted as a starting point for reflection, not as fixed or absolute truths about you. Outputs depend on the depth and candour of the conversation that produced them: a brief or guarded session yields a thinner read; a fuller, more reflective session yields a richer one. The frameworks Ren draws on shape interpretation, they do not produce a verdict — two thoughtful readers could weigh the same evidence differently. Treat the report as one informed perspective among several, alongside your own experience, feedback from people who know you in context, and any formal assessments you trust. Do not use these results as the sole basis for employment, promotion, performance management, or any consequential decision about another person.
