The Second Customer: Designing UK Service Channels for Delegated Enquiries

A contact centre in the Midlands receives a booking request at 02:14. The request is well formed, correctly formatted and generated entirely by software acting for a named policyholder who is asleep. The reply — a confirmation with two alternative slots — will be parsed by that same software and summarised to the customer over breakfast. No human read the original. No human will read the response. The transaction is nonetheless real, committal and, should a complaint follow, discoverable.

That scenario is no longer exotic. Assistants embedded in phones, browsers and messaging applications now draft enquiries, compare quotes, chase refunds and escalate grievances on behalf of UK consumers. For most organisations the volume remains modest, the value uneven and the reporting almost non-existent. That is precisely the point at which a channel is usually allowed to develop badly — quietly, outside the service blueprint, until it is load-bearing.

Delegation changes the shape of the conversation

There is a temptation to treat delegated traffic as a front-end problem: publish cleaner FAQ pages, add structured markup, ship a chatbot, wait for the wave to break. This is the equivalent of widening a doorway for a visitor who arrives with a different set of limbs entirely. The intermediary does not want a better page. It wants a bounded, verifiable way to transact, and it will judge the organisation on whether that exists.

A channel engineered for a human reading at human pace fails an agent that arrives with an objective, a deadline and a willingness to guess. Humans tolerate ambiguity; they ask a clarifying question and wait. Software either infers the missing constraint or abandons the journey. Inferred constraints, repeated at volume, stop being a user-experience quirk and become an operational and regulatory exposure.

Three properties a delegated channel must carry

Machine-readable intent. Free-text correspondence is an acceptable transport for a person and a poor one for an intermediary. A service interface designed for delegated traffic should accept a declared action, subject, scope and constraint — not a paragraph from which these must be excavated. The practical corollary is that organisations must publish their service catalogue as structured capabilities: what can be requested, what it costs, what evidence is required, what response time applies and what the permissible variations are. Without that manifest, every assistant in the market is reverse-engineering the organisation from its own help pages.

Verifiable agency. The intermediary must be able to demonstrate on whose authority it acts and how far that authority extends. Delegated authority is not a login. A scope-token model is more honest: permission to enquire but not to purchase; to book but not to cancel; to raise a complaint but not to settle one; valid for a defined window and revocable without a phone call. Under UK GDPR the familiar tests still apply — lawful basis, specificity, data minimisation — and an assistant granted blanket permission to "handle my affairs" satisfies none of them. Consent that cannot be evidenced at the granularity of the action is consent in name only.

Reconstructable decisions. When a complaint follows six weeks later, the organisation must be able to show the state of the system at the moment of the decision, the inputs it received, the rules and policy version it applied, the alternatives it offered and the accountable human behind the policy. A decision log that records only the outcome is a receipt, not an audit trail. The distinction matters most in regulated sectors, where the regulator will ask why rather than what.

Where the current estate gives way first

Four failure points recur. The FAQ cliff arrives at the third turn, when the intermediary asks a compound question with a condition attached; the organisation falls back either to a human queue it has not staffed or to a generated answer it cannot defend. The identity gap appears because most verification journeys assume a person who can recall a previous address or read a one-time code aloud. The escalation vacuum is the absence of a defined route from agent to human at the correct moment — intermediaries tend to escalate either far too early, inflating load, or far too late, after harm. And the consent blur sits in terms and conditions written for a reader, with no machine-readable statement of what a delegate may and may not do.

None of these is solved by procurement alone. They are design decisions about the service interface, the identity model and the record, and they sit with the same teams that own channel strategy today.

A readiness checklist

1. Can the organisation state, in structured form, which actions an external assistant may perform on a customer's behalf?
2. Is delegated authority scoped to the action, time-boxed and revocable?
3. Does the interface accept declared intent, or demand free text?
4. Is the service catalogue published as capabilities with costs, evidence requirements and response commitments?
5. Can a delegated session be interrupted by a human at a defined point, with context transferred?
6. Does the decision log capture inputs, policy version, alternatives offered and accountable owner?
7. Is there monitoring for variance — unusual volumes, repeated retries, systematic misreads of policy?
8. Are terms of service accompanied by a machine-readable statement of permitted delegation?
9. Is there a route to register, sandbox and rate-limit known intermediaries rather than blocking them at the perimeter?

Governing the intermediary without freezing it

The instinct in many UK organisations is defensive: detect automated traffic, add friction, treat assistants as a nuisance to be filtered. That position is difficult to hold and expensive to maintain. Open Banking taught UK institutions a durable lesson — a structured, permissioned interface is cheaper than a protracted war with screen-scrapers, and it yields better data in the process. The same logic applies here, with the difference that no mandated standard yet exists to force the pace.

Early movers therefore have a narrow advantage: they can define the contract on their own terms, observe how intermediaries behave against it, and adjust the service catalogue before volume makes adjustment costly. The work is unglamorous — a capability manifest, a scoped authority model, a decision record that can survive a subject access request — but it is the same work that makes a human channel defensible, expressed in a form software can use.

The channel map used to show people at both ends. It now shows a node marked, awkwardly, software acting for a person. Teams that design for that node deliberately will find the traffic legible and the governance tractable. Teams that treat it as noise will meet it anyway — at 02:14, unlogged, and with a deadline attached.