woman, phone, phone call, fashion, closeup, talking, outdoors, urban, people
Photo by Surprising_Media on Pixabay

Service Blueprints

Part of Customer effort reduction

Removing unnecessary transfers between service teams

A transfer is useful when a specialist is needed.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Journeys.

A transfer is useful when a specialist is needed. It becomes needless effort when the customer must map your organisation chart, repeat their story or chase an answer no team owns. Fix the ownership path before adding another routing menu.

Examine where transfers occur

Review cases that moved between teams. For each, ask who first received it, why they could not complete it, what information moved with the case and whether the customer had to repeat anything. Separate transfers caused by expertise from transfers caused by permission, unclear policy or an incorrect queue. Not every transfer is avoidable.

Draw a simple map of the case from first contact to confirmed resolution. Include return transfers and cases that disappear between queues.

Look for patterns rather than single bad cases. A cluster of transfers from one queue to another may point to a missing permission, an outdated script or a product the first team was never trained on. Treat each pattern as a question about ownership, and write down who has the authority to change it.

If the first team could resolve a frequent issue with a clear rule or limited system access, test that change with appropriate controls. For genuinely specialised work, assign a visible case owner who coordinates internally and gives the customer one status path.

When a transfer cannot be avoided, tell the customer what is happening. A short explanation of who will pick up the case, what they already know and when the customer will hear back spares the customer from guessing.

Test the hand-off

The receiving team should get a usable summary: customer's objective, checks already performed, evidence supplied, unresolved question and promised response. Test with a case that needs two teams. Can the second team act without calling the customer for the same facts? Does the first owner know the result?

Give the receiving team a way to send a case back with a reason rather than letting it sit. A return with a note shows the first team what was missing, and it keeps the case from becoming nobody's problem. Review those returns regularly so the same gap does not keep recurring.

Measure transfers per resolved case alongside accuracy, time and repeat contact. A lower transfer count can be misleading if agents retain cases they cannot solve. The desired outcome is a correct answer with less work for the customer, not a prettier routing statistic.

More from Service Blueprints