Exact data schema to collect across channels to attribute deflection lift to knowledge base updates

In my experience, one of the trickiest measurement problems in digital support is proving that knowledge base updates actually cause deflection lift. Teams often have the intuition—searches drop, contact volume falls—but without a consistent event schema across channels it's nearly impossible...

Exact data schema to collect across channels to attribute deflection lift to knowledge base updates
Jan 06, 2026 • by Claire Moreau

Featured

Latest News from Customer Carenumber Co

stepwise guide to implement sentiment analysis in your ticketing system and act on the results

stepwise guide to implement sentiment analysis in your ticketing system and act on the results

When I first started experimenting with sentiment analysis in a ticketing system, I expected a quick win: drop in manual triage, faster escalations, happier customers. What I found was more nuanced and, ultimately, more valuable. Sentiment isn't a magic wand — it's a signal. Done well, it helps your team prioritize, improve coaching, and spot trends before they become crises. Done poorly, it...

Read more...

how to run a vendor trial for an AI assistant: objectives, scoring rubric and red flags to watch

how to run a vendor trial for an AI assistant: objectives, scoring rubric and red flags to watch

Running a vendor trial for an AI assistant is one of those projects that looks deceptively straightforward until you’re three vendors in and your inbox is full of demo recordings, feature matrices, and slippery promises about “human-like” understanding. I’ve run more than a few trials like this, and the difference between a trial that leads to a successful deployment and one that wastes...

Read more...

how to run a quarterly CX retrospective that surfaces actionable experiments, not just complaints

how to run a quarterly CX retrospective that surfaces actionable experiments, not just complaints

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...

Read more...

practical framework for deciding when to automate vs when to route to a human in customer journeys

practical framework for deciding when to automate vs when to route to a human in customer journeys

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...

Read more...

how to reorganize your team around customer outcomes instead of channels in four practical steps

how to reorganize your team around customer outcomes instead of channels in four practical steps

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...

Read more...

a compact guide to choosing the right escalation workflow when you support regulated industries

a compact guide to choosing the right escalation workflow when you support regulated industries

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...

Read more...

how to draft a cross-functional incident runbook that keeps customers informed and reduces escalations

how to draft a cross-functional incident runbook that keeps customers informed and reduces escalations

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 —...

Read more...

the minimal data collection plan that lets you demonstrate ROI from self-service articles

the minimal data collection plan that lets you demonstrate ROI from self-service articles

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...

Read more...

how to design an onboarding support journey that increases trial-to-paid conversion by focusing on signals

how to design an onboarding support journey that increases trial-to-paid conversion by focusing on signals

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,...

Read more...

how to build a one-week experiment to compare intercom flows vs current conversations

how to build a one-week experiment to compare intercom flows vs current conversations

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...

Read more...