Customer & service

The join is the product.

Service quality depends on several teams, several systems, and a customer who should not have to know any of that. A fluent front end on a broken path is still a broken path.

Start a conversation How we work

Fig. IContext drops where the organisation hands over.

01 The picture

Customers experience the joins you cannot see.

Three teams, two systems, one person who has to repeat themselves. A chatbot on top of that structure makes the organisation sound fluent and remain incoherent.

We see the journey as a system, including the back-office joins. The damage is rarely in the channel. It is in the handshake: lost context, contradictory answers, re-entry.

Automation helps where the intent is stable and the facts are present. Where judgement under exception is the work, a person still needs an owned path — not a layer that hides the missing fact.

The design has to be staffable. An experience that operations cannot run will recreate the unofficial path by next quarter.

01Start from
The journey including back-office joins
02Typical pressure
Lost context, contradictory answers
03Usual mistake
A front-end layer on a broken path
04Useful output
Fewer handoffs that drop meaning

02 What continues

Fewer handoffs that drop meaning.

The customer should not have to assemble the organisation.

See the journey as a system, including the back-office joins
Judge where automation helps, and where a person still needs judgement
Reduce re-entry, lost context, and contradictory answers
Design a path that operations can staff and technology can support

03 Adjacent situations

The method is the same. The constraint is not.

OperationsWhen the work has outgrown the way it is organised — and tools keep arriving faster than the process can absorb them.Technology leadersWhen the organisation expects a technology answer, and the harder work is choosing which problem is worth solving.Growing teamsWhen informal ways of working no longer scale, and the next system will either create order or freeze the wrong habits.Regulated environmentsWhen a wrong step is expensive, and technology cannot be introduced as an experiment on live operations.

Work that often applies

Systems & operationsDisconnected processes and overlapping tools, made into a way of working that people can actually follow.AI & automationPractical uses of AI and automation — identified against the work, not against the hype.Solution designA complex requirement turned into a structured approach: what is built, what is connected, and in what order.

Questions we are asked

Is this CX design?

It includes the operational system behind the experience, which is where most of the damage sits.

Fig. ZThe conversation is the first artefact.

A conversation

Bring the constraint as it currently stands.

We will help you find the problem underneath — and whether technology should wait.

Start a conversation Who we help