If the Customer Has to Find the Right Department, Your Org Chart Has Leaked Into the Experience.

There is a sentence customers should almost never need to say: ‘Who do I need to speak to?’ It sounds harmless. In reality it is often the moment your internal organisation chart becomes the customer’s problem. A guest has a billing issue and gets sent from reception to reservations. A retail customer is told online orders belong to another team. A spa client who wants to change a package is bounced between front desk, therapist and manager. None of those customers bought departments. They bought one business.

Most companies are structured vertically because management needs clarity over expertise, budgets and accountability. Customers move horizontally. They cross marketing, sales, booking, operations, finance, service and aftercare without caring where one function stops and another starts. When the seams are visible, the customer has to do the integration work the business failed to do. That is not a communications problem. It is an operating design problem.

The customer should not need your internal vocabulary

Businesses teach themselves a private language. Revenue management. Guest services. Ecommerce. Membership. Operations. Customer care. Finance. Those labels are useful internally, but they become dangerous when customers are expected to route themselves correctly. A customer asking for a refund should not need to know whether the transaction sits with a venue, central team or payment provider. A hotel guest asking to extend a stay should not have to understand the boundary between front office and reservations.

The better design principle is simple: the business accepts the request wherever the customer naturally raises it, then routes it backstage. The customer-facing employee does not need to solve everything personally, but they do need to own the next step. ‘That is not my department’ hands the work back to the customer. ‘I can take that from here and get it to the right person’ keeps the responsibility inside the business.

Ownership matters more than handoff

A handoff is not automatically bad. Complex businesses need specialists. The failure begins when ownership disappears during the transfer. The customer repeats the story, chases for an update, wonders whether anyone is still dealing with it and eventually discovers that each department believes somebody else owns the outcome. The organisation has technically processed the request while commercially damaging trust.

This is closely related to service recovery. If every unusual customer problem needs a manager, the frontline has too little authority. If every cross-functional problem needs the customer to coordinate several teams, the business has too little ownership. We have written before about why a service recovery model breaks when every problem needs managerial intervention. The same principle applies here: the system should absorb complexity before the customer has to.

Good ownership has three visible behaviours. Somebody accepts the issue without deflecting it. Somebody is responsible for the next movement, even if another team must act. And somebody closes the loop with the customer. Those behaviours sound obvious until you test them against real journeys and discover how many requests sit in shared inboxes, unresolved ticket queues, manager WhatsApp groups or vague ‘I have passed it on’ territory.

Design one front door, not one giant department

The answer is not to flatten the company into a single customer service team. Specialism still matters. The answer is to create a clear front door and disciplined backstage routing. For each common customer need, define where it can be raised, who owns acknowledgement, which team performs the specialist work, the expected response time and who confirms resolution. That turns customer experience from goodwill into an operating standard.

This is particularly important in multi-site hospitality, leisure, events and premium retail. Growth multiplies contact points. A customer may discover you through one channel, buy through another, visit a third location and contact a central team afterwards. If ownership is designed around departments rather than journeys, scale does not simply add complexity. It exports complexity directly to the customer.

The same issue appears when strategy is open to departmental interpretation. In our recent article on alignment, we argued that a strategy is not aligned if every function can interpret it differently. Customer ownership works the same way. If five teams can reasonably assume another team owns the outcome, nobody truly owns it.

A useful leadership test takes twenty minutes

Pick five ordinary customer requests: change a booking, dispute a charge, ask for an exception, report a poor experience, and request something that crosses two departments. Do not ask what the policy says. Ask what actually happens. Where can the customer raise it? Who becomes accountable at first contact? How many times might the customer repeat themselves? What happens when the request arrives at 7pm on a Saturday rather than 10am on Tuesday? Who tells the customer it is finished?

If those answers are fuzzy, your org chart is probably leaking into the experience. The cost shows up as longer handling times, duplicated work, frustrated staff, avoidable escalations and customers who describe the business as difficult even when each individual employee was perfectly polite. Politeness cannot compensate for an operating model that keeps handing responsibility sideways.

For CEOs, the standard should be higher: customers can move across your business without needing to understand how your business is organised. Brand promises are made horizontally, across the whole journey. Your operating model has to work the same way.

If you want to see where Brand, People and Operations are creating those seams, Q Branch uses FUSION to diagnose the gaps between promise, behaviour and delivery. You can start from Q Branch and work from the customer journey backwards into the system that has to support it.