The same issue creates another interaction.
Customers return because the first process, answer or communication did not resolve their need.
A practical operating playbook for defining the customer problem, diagnosing the missing step and turning relevant evidence into an owned action.
Survey responses, calls, emails, chats, support cases and operational reporting can all contain useful signals. When they remain fragmented or are reviewed in isolation, recurring friction becomes difficult to compare, explain and prioritise.
The exact issue differs between organisations. The pattern is that a customer problem creates work across functions while the evidence remains difficult to assemble.
Customers return because the first process, answer or communication did not resolve their need.
A digital step may be unclear or incomplete, creating questions that move into customer service.
The conversation occurs in customer service, while the relevant process may sit elsewhere.
Customers may contact the organisation when information, responsibility or the next step is unclear.
Without comparable evidence, urgency, volume and customer impact can be difficult to weigh together.
The organisation changes something but cannot clearly assess whether the intended customer improvement occurred.
Recurring friction can influence contact demand, workload, complaints, digital adoption and the customer experience. The purpose of the playbook is not to assume the cause. It is to create a disciplined route from observation to investigation, action and follow-up.
Repeated or preventable contacts can add pressure to operational teams.
Customers may need several attempts or channels to complete the same task.
The symptom can appear in one team while the relevant process sits in another.
Priorities can be shaped by isolated examples rather than a shared evidence base.
Without a defined outcome, it is difficult to know whether an intervention helped.
Functions can interpret the same customer problem differently when the evidence is fragmented.
Select one signal route and one operating gap. Together they become the input to the next section — not a score that sits on its own.
[ ASK / UNDERSTAND / CONNECT ] × [ SIGNAL / EVIDENCE / EXPLANATION / ACTION / FOLLOW-UP ]
The same diagnosis labels continue here. The example below is illustrative and does not represent a customer case, a confirmed cause or a promised result.
The products support different information needs. TMN Survey and TMN Insight are independent ways to begin. TMN Insight+ extends Insight and is in development.
| Product | Use when | Customer signal | What it supports | Status |
|---|---|---|---|---|
| TMN Survey | You need to ask customers a focused question after a selected event or interaction. | Responses collected by SMS or email. | Response volume, distribution, trends and comments for follow-up. | Available today |
| TMN Insight | The answers may already exist in customer conversations. | Supported calls, emails, chats and support cases. | Move from the overall picture to themes, sentiment, stories and underlying conversations, then towards decisions and actions. | Available today |
| TMN Insight+ | Leadership needs Insight evidence considered with a wider set of agreed information. | TMN Insight plus agreed business data and relevant internal information. | A wider decision context within the agreed scope and governance framework. | In development |
This keeps the analysis useful without turning a recurring pattern or plausible explanation into an unsupported causal claim.
The exact answers depend on the agreed setup. The playbook should make these decisions visible rather than imply that they are automatic.
Enter your email address to access the complete playbook as a portrait A4 PDF.