The Single Point of Contact That Users Route Around
FinBridge, a 4,200-employee financial services firm, runs a 26-agent internal service desk across Leeds, Manila and Dallas, covering 07:00–22:00 with no overnight shift. Monthly volume is around 9,600 contacts. First contact resolution is 62%, average handle time is 11 minutes, and average satisfaction is 3.4 out of 5. The practice's stated aim is to be the 'single point of contact', but 34% of contacts reach an agent as a direct Microsoft Teams message rather than through the portal or phone queue, and none of that demand appears in reporting. Six shift leads exist on paper; each spends roughly 80% of the shift taking contacts, and none has tooling permission to reassign work between agents or to place a ticket into a second-line queue without that team's agreement. Second-line teams will not accept direct calls from the desk: they require a ticket in their own queue and routinely return it if the description is incomplete. Attrition is 31% a year and the desk is carrying seven vacancies.
1. Leadership wants to 'reassert the single point of contact'. Explain what is actually broken, and identify the organisational changes - not communication campaigns - that would make the single point of contact real.
Read the worked answer
The slogan is not the problem; two design facts are.
First, the cheapest way for a user to get help is a personal Teams message. When the supported channel is slower or feels more formal than messaging a named agent, users route around it, and the desk loses both the record and the ability to prioritise. That is a channel-design and accountability problem, not an awareness problem.
Second, the desk cannot own an interaction end to end because it does not control routing into second line. Second-line teams set the terms - their queue, their completeness rules - and can return work, while shift leads have no tooling rights to reassign. Commitment without control is why 'single point of contact' reads as a claim rather than a service.
Changes that would matter:
- Publish the supported channels and make the portal or phone queue genuinely easier than a DM: faster resolution, visible status, named owner.
- Give the shift lead explicit dispatch accountability - queue ownership, reassignment across agents, priority override, authority to place a ticket in a second-line queue - and matching permissions in the tool.
- Negotiate an interface model with second line: what a complete handover contains, return criteria, a named contact route, and mutual measures so returns are visible to both sides.
- Log Teams-originated contacts under their own channel category so shadow demand becomes a number.
- Reduce shift leads' queue work so dispatch is a real job rather than an interruption.
Communication campaigns alone shift the cost onto users and second line, and will fail.
2. A manager proposes creating a dedicated major incident manager role, staffed 24/7 by three new hires, sitting alongside the shift leads. Volume is about five major incidents a month. Assess the proposal.
Read the worked answer
Test the workload before the headcount.
Five major incidents a month is roughly one a week. Even generously allowing four hours of coordination each, that is under 20 hours a month of dedicated work. Three full-time posts is around 500 hours a month of capacity for roughly 20 hours of demand - and it would be filled while the desk carries seven vacancies and 31% attrition, so the marginal agent is far more valuable in the queue.
What is genuinely missing is accountability, not bodies. Today nobody is empowered to pull second-line engineers onto a bridge, or to take priority decisions away from a shift lead who is also handling contacts.
A cheaper design: designate a major incident coordinator from the existing shift-lead pool on a rota, with an on-call tier for nights, a documented trigger (severity criteria), explicit authority (declare, convene, set communication cadence, commit resources), and the service desk manager as fallback.
One caveat worth raising: major incident management is a distinct practice, and nothing requires the coordinator to sit in the service desk. What matters is that the accountability is named, staffed for the actual volume, and does not collide with the shift lead's dispatch role - one person cannot credibly do both during a major incident.
3. Shift leads are held accountable for queue performance but have no formal authority, and second-line teams refuse to cooperate. What practical mechanisms would you put in place?
Read the worked answer
Formalise decision rights rather than hoping for cooperation.
- Write down what the shift lead can decide - priority changes, reassignment between agents, holding a ticket in a second-line queue, escalating - and configure the tool so those rights are executable. Authority that exists only on an org chart gets ignored at 03:00.
- Create an escalation ladder with names: shift lead to service desk manager to service owner for the affected service. The service owner is usually the person who can settle cross-team disputes, because the resolver groups sit in the same value stream.
- Convert vague SLAs into operational-level agreements with each resolver group: turnaround, what constitutes a complete handover, and return criteria. Returns should count against both parties, which changes the conversation from 'your tickets are poor' to a shared measure.
- Use the newly captured shadow-channel and returned-ticket data in a monthly review with second-line managers. Evidence, not anecdote.
- Fix the capacity that makes authority unusable - a shift lead at 80% queue work cannot dispatch.
What not to do: do not give the desk authority to force work onto teams without an agreed interface. That converts a coordination problem into a conflict, and the desk will lose it.