real-world template to calculate the lifetime value impact of improving first response time by X%

I run quarterly CX retrospectives because monthly fire-fighting and weekly stand-ups rarely create the space to learn deliberately. Over the years I’ve seen retros devolve into complaint sessions — a room where every pain point is aired but nothing changes. In this post I’ll share a reproducible template I use at Customer Carenumber Co (https://www.customer-carenumber.co.uk) to run a quarterly retrospective that consistently surfaces...

Read more...

When teams ask me whether they should automate a touchpoint or send a customer to a human, I always push back: the right choice isn’t binary. It’s a sequence of decisions guided by risk, value, frequency, and the customer’s context. Over the past decade I’ve seen the best outcomes come from a practical framework that combines data, customer empathy, and fast experiments. Below I share a framework I use at Customer Carenumber Co to decide...

Read more...

When I started helping support teams shift from channel-based organisation to outcome-focused squads, I expected resistance — but what surprised me most was how often teams hadn’t even agreed on the outcomes they were trying to deliver. Channels are easy to see: you can count phone lines, chat sessions, and inboxes. Outcomes are messier because they require judgement, measurement, and cross-functional collaboration. That messiness is where...

Read more...

Supporting regulated industries — healthcare, finance, telecoms, utilities, and similar — forces you to be precise about escalation workflows. I’ve built and reviewed workflows for teams operating under strict SLAs, audit trails, and privacy constraints, and I still lean on a handful of practical rules whenever I design or evaluate an escalation path. This compact guide walks through what to consider, the trade-offs to balance, and a...

Read more...

I’ve spent more than a decade helping support teams design processes that keep customers calm and teams focused during incidents. One of the most reliable levers I’ve found is a well-drafted cross-functional incident runbook: a living document that defines who does what, when, and how we talk to customers. Done right, it reduces escalations, shortens resolution times, and — importantly — preserves trust by keeping customers informed with...

Read more...

When I help teams prove the value of self-service content, the most common problem I see is an appetite for perfect measurement that never turns into action. Teams design complex tracking schemas, wait for months of noisy data, then decide measurement is "too hard" and revert to opinion-based decisions.I've learned to flip that script: start with a minimal data collection plan that answers the core question stakeholders actually care about —...

Read more...

When I work with product and support teams on onboarding, I stop thinking about "onboarding" as a single linear process and start thinking about a conversation made of signals. Every click, message, error, and delay is a signal that tells you whether a trial user is moving toward activation — or toward churn. Designing an onboarding support journey around these signals is the fastest, highest-leverage way I've found to lift trial-to-paid...

Read more...

I often get asked how to run fast, low-risk experiments that actually tell you whether a new automation or conversational flow is worth rolling out. Recently I needed to compare Intercom’s outbound flow/series approach with our existing live conversation model — and instead of a vague pilot, I designed a one-week experiment that gave clear, actionable results. Below I share the exact approach I used, the decisions to make up front, and the...

Read more...

I run a lot of experiments with chatbots and conversational automation, and one question keeps coming up: how do we prove the bot is actually improving customer satisfaction? It’s tempting to point to a single CSAT score and call it a day, but in practice you need a mix of quantitative and qualitative signals to build a convincing story. Below I share the set of metrics I always track, why each matters, how to measure them cleanly, and a few...

Read more...

When I’ve been in the room asking for budget for a new support platform, the difference between "we need better tooling" and "we deserve investment" always came down to one thing: the dashboard. Leaders don't buy feelings — they respond to clear, measurable impact. Here’s the exact set of metrics I put on a leadership dashboard to win budget conversations for a new support platform, how I explain each metric’s business relevance, and...

Read more...