Fix the mandate before you fix the queue

In short. You do not need a six-month diagnostic to know where your contact volume comes from. You need one week, a tally sheet and one person with the reach to change something outside the contact centre. Everything you decide after that, platform included, gets easier.

We sit in these projects across Europe, and the pattern repeats. An organisation has left its contact centre alone for ten or twelve years, then tries to repair a decade of accumulated decisions in a single migration. Six or nine months of comparing suites, a careful choice, and then angry agents in week one.

Our senior consultant CX and Voice, Stephan Kuurstra, puts it plainly. Most of the time it is not the solution that fails, it is the choices you made inside it.

Where this article sits in the series

This is the first of four connected articles about moving from queue management to journey ownership. The four run in the order you would actually do the work, and each one hands something concrete to the next.

This part produces two things: a named owner with reach beyond the contact centre, and a one-week log of what is actually causing your contact volume. Part two uses that log to decide which contact reason belongs on which channel. Part three uses it again to decide whether automation is even the right fix, or whether an upstream change would remove the contact altogether. Part four runs the log a second time to check whether you removed work or merely moved it.

So if you read only one part, read this one. Everything downstream inherits the decisions made here.

Log causes, not subjects, for one week

Your reporting already tells you what people called about. It rarely tells you why the call existed at all. Wrap-up codes are a step, but they stop one question short.

So run a small version yourself. One week, one tally sheet, the next fifty to one hundred contacts. For each one the agent notes the cause, not the subject: unclear invoice, delivery later than promised, a confusing step in the order process, information missing from the confirmation email. Paper is fine. This is half a day of work spread across a week.

Then count. In most organisations three to five causes explain more than half the volume, and most of them are owned by another department. The queue is where the problem becomes visible. It is rarely where it becomes solvable.

That list is your business case, and it beats an ambition slide every time. It also names the departments you need in the room. In DMG Consulting's 2026 research, only 27.9% of organisations plan to align customer experience across the enterprise, which is roughly the share that will reduce volume rather than move it around.

"Wrap-up codes tell you what the call was about. They do not tell you why the customer had to call at all."

The distinction sounds small and it changes the whole project. A subject log produces a staffing conversation. A cause log produces a list of departments. Only one of those two lists can actually reduce volume, and it is never the first one.

Ambition first, then anything technical

Before the requirements document, answer one question. Is it important to this organisation that the phone gets answered, or is there a real ambition for customer contact?

If nobody has answered that, every later decision defaults to cost. And when a project is owned by IT alone, that is exactly where it lands. The cheapest option wins and nobody asks what the customer got out of it.

IT belongs in the room for the technical checks and for fit with the wider technology strategy. What is usually missing is operations, plus a mandated voice of the customer at C-level. Once someone in that room starts from we want to be easy to deal with, the cheapest option stops winning by default, because there is finally a case for operational value.

Five people, half an hour a week

Keep the team small. A sponsor who controls budget. One ambassador. The operational lead for the contact centre. Someone from IT or telecom. And one representative from the department that causes the most volume, picked from your tally sheet.

The ambassador is one named person, not a steering group. Job title matters less than reach. They need to be able to get something changed outside the contact centre. Without that they can only manage the queue, and you are back where you started.

Half an hour a week beats two hours a month. Short and frequent keeps decisions small enough to actually make.

Budget for year two

Licences are the smallest line. Implementation, integration, the data work, training, and structurally half to one FTE for ongoing optimisation. In the DMG research, AI cost is a joint top concern at 37.1%, largely because organisations budget the licence and discover the rest later.

There is a second reason to get the numbers right early. Gartner reported in February 2026 that 91% of customer service leaders are under pressure to implement AI, and pressure of that kind tends to produce underfunded pilots rather than working services. Gartner also puts the cost of contact centre downtime at roughly 5,600 dollars per minute, which is the figure that makes resilience a board conversation rather than an operations one.

Set the ambition in one sentence someone on the floor could repeat back. Then write down what you are explicitly not doing this year. That second sentence prevents most of the scope arguments. And before you add heads, check the tally sheet and ask why it is so busy.

Do this week

• Print a tally sheet and brief your team at Monday's stand-up
• Book a thirty-minute weekly slot for the next eight weeks
• Ask your sponsor one question: what can this project change outside the contact centre?

Checklist, part 1

• Sponsor with budget mandate named
• One named ambassador, with reach beyond the contact centre
• Team of six or fewer, including one department that causes volume
• One week of causes logged, not subjects
• Top five causes handed back to their owners
• Budget covers implementation, data, training, and years two and three
• Ambition in one sentence, plus what you are not doing this year

Next in this series

With the mandate settled and a week of causes on paper, the next decision is which channels you run and which contact reason belongs on each of them. That is part two, Know your customer, then pick your channels. It also covers the list of things you should never automate, and the EU transparency rules that came into force on 2 August 2026.

Read the full series

These four articles are written to be read in order. Each one produces something the next one uses.

• Part 1. Fix the mandate before you fix the queue (you are reading this one). Who owns the problem, and how far does their mandate reach.
• Part 2. Know your customer, then pick your channels. Which contact reason belongs on which channel, and what you will never automate.
• Part 3. Start with your data, not your bot. Whether your data can support what you want to automate, and where to start.
• Part 4. Turn it on, measure it, and be willing to turn it off. The loop that keeps the first three parts alive after go-live.

Source: DMG Consulting LLC, 2026 CX AI Playbook: Strategic Outlook and Investment Priorities, February 2026, sponsored by Five9. Additional market data from Gartner, Zendesk and public analyst commentary, retrieved August 2026.