Public-facing contact in the UK public sector operates under a constraint commercial organisations rarely face: the person ringing usually has nowhere else to go.
A dissatisfied broadband customer switches. A council tax payer, a housing association tenant, a benefits claimant and a patient awaiting an appointment cannot. That asymmetry changes everything about how the contact function should be designed, and it is the reason approaches imported wholesale from retail service tend to disappoint.
Who is actually calling
The caseload in local government, social housing and public services skews heavily toward people in difficulty.
Repairs reporting, arrears and rent accounts, housing applications, benefits and council tax queries, adult social care enquiries, complaints about services that have already failed. A meaningful proportion of callers have a disability, a language need, a mental health condition, caring responsibilities, or a combination. Many have tried the website first and found it did not cover their situation.
This produces a contact profile that is longer, more complex and more emotionally demanding than almost any commercial equivalent — handled, typically, by teams under acute budget pressure. It is why consultants who evaluate offshore public service delivery treat public sector contact as a discipline in its own right rather than as a variant of retail service.
“The public sector queue is the hardest work in UK contact handling and it is almost always the worst resourced,” said Ralf Ellspermann, founder and chief strategy officer at PITON-Global. “Every caller has already tried to solve it themselves, and most of them are ringing about something that has gone wrong in their housing, their money or their health.”
The digital-first assumption, examined
Channel shift has been public sector orthodoxy for over a decade: move transactions online, reserve the telephone for those who need it.
The logic holds for straightforward transactions and breaks for everything else. A tenant reporting a leak can do it online. A tenant reporting a leak that has been reported twice already, is now affecting a neighbour and has damaged belongings cannot — and the online form will capture it as a third repair request rather than as the escalating failure it has become.
The useful distinction is between transaction and situation. Transactions digitise well. Situations require a conversation, and the organisations that have pushed hardest on channel shift have frequently done so without separating the two, producing an online estate that handles the easy half beautifully and funnels the hard half into a reduced telephone service.
What can be outsourced, and what sits awkwardly
A good deal transfers, and the boundaries are different from commercial work. A substantial share of the transactional volume now sits with Philippine contact centre services handling public-facing work, which is less controversial in practice than it is in procurement.
“The question is never whether the offshore team can handle the call,” said John Maczynski, chief executive of PITON-Global. “It is whether they can reach the right person in the organisation inside two minutes when the call turns out to be about something else entirely.”
Transfers with care: anything touching safeguarding, homelessness, adult social care or domestic abuse. Not because the work is technically difficult but because the escalation routes must be immediate, correct and locally connected — an offshore agent needs a route to a named duty officer, not a case note.
Does not transfer: statutory decisions, anything requiring a local officer’s discretion, and casework where continuity with a named individual is part of the service.
Several housing associations and councils now run a split model — digital and offshore handling the transactional volume, a smaller retained team handling situations — and the design question is where the boundary sits rather than whether to use one.
Transfers well: repairs reporting and scheduling, general enquiries, appointment booking, account and rent balance queries, out-of-hours cover, overflow and surge capacity during a service disruption or a billing cycle, and the back-office processing behind all of it.
Procurement is its own obstacle
Public sector buying runs on frameworks, evaluation panels and scoring matrices, and the process rewards attributes that do not predict service quality.
Three practical consequences. Price weighting frequently dominates even where the specification claims otherwise. Social value requirements, which are legitimate, are sometimes interpreted in ways that disadvantage any offshore component regardless of outcome. And specifications tend to describe volumes and service levels rather than the situations the service actually handles.
A specification built around situations — what happens when a vulnerable tenant reports a repair that has failed twice; what the escalation route is at seven in the evening — produces far better bids than one built around average handling time and abandonment rate.
Buyers who get this right tend to spend their effort on the escalation design rather than on the volumetrics, because the volumetrics are the part every bidder will answer identically.
Accessibility is a requirement, not a feature
Public bodies carry duties that commercial organisations do not, and they reach the contact centre directly.
Reasonable adjustments have to be available and recorded, so that a caller does not have to request the same adjustment every time. British Sign Language provision, text relay and translation need to work in practice rather than existing in a policy. And where a caller is supported by an advocate, a family member or a caseworker, the operation needs a lawful and practical way to deal with them.
These are design requirements for the system and the training, and they are the elements most often discovered to be inadequate after go-live rather than specified before it.
Measuring what matters here
Abandonment rate and average speed of answer tell you about the queue. They tell you almost nothing about whether the service worked.
More useful: resolution without repeat contact within a defined window, which captures whether the situation was actually dealt with. Proportion of contacts that are chasers, which measures whether the organisation is keeping people informed. And escalation accuracy — of the contacts routed to a specialist or safeguarding route, how many were correctly identified, and how many were missed and surfaced later.
That last measure is the one with genuine consequences attached, and it is the one least often reported.
See also: How Crypto Is Changing Global Commerce
The underlying point
Public service contact is not customer service with a different customer. The obligation is different, the alternative-free position of the caller is different, and the cost of getting it wrong falls on people with the least capacity to absorb it.
Designing for that — rather than importing a retail model and adjusting the scripts — is what separates the operations that work from the ones that merely answer quickly.
