The Ticket That Shouldn't Exist: A Playbook for CX Leaders Who Are Done Absorbing Product Problems

There is a question most CX teams never ask

Every CX leader knows the drill. Average handle time is up. CSAT is holding steady. The queue is moving. The team is working hard.

And yet contact volume stays stubbornly high. Month after month, the same categories appear in the reports. The same frustrations come through in the transcripts. And the same cross-functional meetings end with product nodding along and nothing changing.

The underlying assumption, usually unspoken, is that support volume is a given. Something to be managed, not eliminated.

Fiona Green, Director of User Success at KOHO, spent several years proving that assumption wrong. In a recent Birdie webinar, she shared the full playbook: the dead ends, the reframe, the diagnostic approach, and the three questions she now puts to any CX leader who wants to do the same.

This article is that playbook.

Want the full KOHO story?

The KOHO case study covers the complete journey (the diagnostic process, the cross-functional fix, and all the results) in a format built for sharing with your team. Read the KOHO case study →

‍

The reframe: stop optimizing for handling, start questioning existence

Most CX improvement efforts focus on handling contacts better: faster, cheaper, more consistently. The implicit assumption is that the contact needed to happen.

The more powerful question is whether it should have happened at all.

"Most CX teams track how well they handle contacts. We started asking which contacts should never have existed." Fiona Green, KOHO

This isn't a small semantic shift. It changes the entire frame of the problem:

• It moves support volume from a CX metric to a product and operations metric
• It positions every ticket as a signal of upstream failure, not just a task to complete
• It creates a mandate for cross-functional action, not just internal optimisation

‍

When KOHO's leadership challenged Fiona's team to scale without band-aid solutions, this reframe was what made the difference. Not new tooling. Not more headcount. A different question.

Two approaches that don't work, and why

Before arriving at the model that worked, KOHO tried two things that many CX leaders will recognise.

A dedicated CX development team

The idea: give CX its own tech resource, so friction points can be fixed without competing for product roadmap space. In practice, this created a new bottleneck: product and marketing began routing their own unresolved problems through the CX team, turning it into an overflow drain rather than a strategic fix engine. After six months, the pilot was scrapped.

The lesson: a dedicated resource without shared ownership doesn't solve the root problem. It just relocates it.

Regular product meetings

Monthly cross-functional meetings with product sounded like progress. But without a shared language and a clear prioritisation framework, they became a one-way reporting exercise. CX flagged issues; product noted them; nothing reliably made the roadmap. The cadence was also wrong: monthly check-ins kept missing the windows where product roadmaps were actually being set.

The lesson: access to the room is not enough. You need to arrive with the right framing.

Key insight: the data is rarely the problem. The framing is. Support volume doesn't resonate with product partners. Churn risk, revenue impact, and brand damage do.

‍

The framework that works: three pillars for getting product to act

Fiona's team rebuilt their cross-functional model around three principles. Together, they transform CX insights from an internal report into a shared business agenda.

1. Align around a shared outcome

Stop presenting contact volume as a CX number. Start connecting it to outcomes the rest of the business already cares about.

The shift looks like this: instead of telling a product manager that 1,500 users contacted support about login this month, you say that users who cannot log in are unable to fund their accounts, and that is showing up in soft churn data. The number is the same. The framing lands entirely differently.

Revenue, retention, and brand risk are the languages of the business. CX has been speaking in a dialect that only CX understands.

2. Drive specific customer behaviours

Vague problems don't get prioritised. "Users are having login issues" is not a product spec; it is a category. Product managers need something they can scope, build toward, and measure.

The reframe is to define the customer behaviour you want to enable: not "fix login" but "enable users to recover account access without agent intervention." That is a clear success state. It can go into a sprint. It has an owner. It gets done.

3. Deliver measurable business impact

Assign a cost to every contact. If it costs X pounds per conversation, and you have 1,500 login contacts per month, that is a number the finance team recognises. Layer on the cost of churn from users who tried and abandoned (contacts you never even saw), and the business case becomes undeniable.

Connecting CX data to financial outcomes is what converts a product team from passive recipients of feedback into active co-owners of the problem.

‍

The diagnostic gap that holds most CX teams back

Even with the right framing, most CX teams hit a wall when product asks the inevitable follow-up: "Can you be more specific?"

Manual tagging systems, the default for most support operations, are too broad and too inconsistent to answer that question well. "Login issues" is a bucket, not a diagnosis. Inside that bucket might be five or six distinct failure points, each with a different cause, a different fix, and a different owner. Without the ability to surface that granularity, CX stays stuck presenting symptoms instead of root causes.

The diagnostic layer changes this. When conversations are analysed at scale, not sampled or manually tagged but systematically read, patterns emerge that human review misses. Sub-issues become visible. Frequencies become comparable. The journey from "we have a problem" to "here is exactly what is broken and what it costs" becomes navigable.

That is the difference between bringing a complaint to a product meeting and bringing a brief.

"After making progress on the larger levers, Birdie helped us identify and get traction on stubborn contact drivers we had historically struggled to move: the ones that kept showing up but never got prioritised." Fiona Green, KOHO

The cross-functional room: how to actually get there

With the right framing and a precise diagnosis in hand, the next challenge is getting the right people to act. This is where most CX improvement efforts stall, not because the insights aren't compelling, but because the ask is too vague or the business case isn't in the right language.

Fiona's approach was to build the case in three layers:

1. The product problem: not 'we're getting too many contacts' but 'here is the specific failure point in the user journey, and here is where it is in the flow'
2. The customer behaviour impact: who is failing, what they cannot do as a result, and how many of them aren't even raising a ticket
3. The business cost: contact cost per conversation, churn signal from abandonment, brand damage from app store reviews and social posts

‍

When a CX team arrives at a product meeting with all three layers, the question shifts from 'should we fix this?' to 'when do we fix this?'

And when the fix is designed, CX should be in the room, not as a reviewer after the fact, but as a co-designer. At KOHO, User Success now has sign-off on every product proposal. Support requirements are built in from the start, not retrofitted at the end.

Three questions to take back to your team today

Fiona closed the webinar with three questions she would ask any CX leader right now. They are worth sitting with seriously, not as exercises but as diagnostics for where the work actually is.

‍

1. Where is product friction your team is papering over?

Go through every user journey where a "contact support" prompt appears. Ask whether it needs to be there, or whether it is a design shortcut: a UX journey that was never fully resolved, with support absorbing the consequence.

A practical starting point: audit every entry point that generates support contacts and ask, for each one, whether the customer should have needed to contact support at all.

2. Which contacts should never have existed?

This is the sharper version of the same question. Not which contacts are hard to handle. The question is which ones reflect a failure that the product or operations team should have prevented upstream.

These are your biggest levers. They are also usually the ones that have been on the 'known issues' list for years without movement, because they have never been presented with sufficient diagnostic specificity or business urgency to get prioritised.

3. What would it take to get cross-functional partners in the same room?

Not for a monthly check-in. For a focused session with a specific problem, a specific diagnosis, and a specific outcome to design toward. What does the business case need to say? Who needs to hear it? And what would make this the most urgent thing on the product roadmap this quarter?

The answer to that question is your action plan.

‍

CX as a product function, not a downstream cost centre

The most significant shift in Fiona's story is not the 75% reduction in contact volume, remarkable as that is. It is what the team had to become to get there.

A CX team that asks which tickets should never have existed is not a support team. It is a product intelligence function. It brings precision, not just volume. It speaks business language, not CX metrics. It sits at the design table, not just the review table.

That shift is available to any CX leader. It does not require new headcount or a platform overhaul. It requires a different question and the diagnostic capability to back it up.

‍