A client asking to work with someone else on the team feels like an implicit judgment on whoever they're currently working with, and reacting as if it is one, before understanding why, tends to make an easy fix into an uncomfortable situation. The request itself is rarely as loaded as it feels in the moment.
Handling it well isn't about defending the current contact or immediately assuming they did something wrong. It's finding out what's actually behind the ask.
A delicate signal, not necessarily a complaint about the person
A client requesting a different contact might be reacting to a personality mismatch, a scheduling conflict, or simply wanting someone with different expertise, none of which reflect poorly on the current person. Resist the instinct to read it as a verdict before you actually know what's behind it.
Ask directly what actually prompted the request
A vague or general request, "can we work with someone else," deserves a direct, low-pressure follow-up about what's driving it. The actual reason shapes whether this is a simple logistics fix or a signal about something that needs addressing more broadly.
In Stelaah, a client's assigned team members and communication history stay on the record, so a contact change can happen cleanly with full context carried forward. See how clients works.
Make the switch cleanly without an awkward public postmortem
Once the reason is understood, make the change efficiently, briefing the new contact on the relevant history, without turning it into a drawn-out internal investigation. Most of these requests are logistical, not disciplinary, and should be handled with that proportionate weight.
Protect the outgoing person's standing on the team
How the switch is communicated internally matters, framing it as a routine reassignment protects the outgoing team member's standing, while framing it as a failure damages morale over something that's often not their fault at all. Be deliberate about the internal narrative.
Look for a pattern if it happens more than once
A single request is usually just circumstance; the same request happening repeatedly, across different clients, about the same person, is worth examining as an actual pattern rather than a series of unrelated coincidences.
A simple checklist
If you do nothing else, do these five things:
- Ask directly what prompted the request before assuming the worst.
- Handle the switch efficiently, without an unnecessary internal investigation.
- Frame the change internally as routine, not as a failure.
- Carry the relevant history forward to the new contact.
- Watch for a repeated pattern across multiple clients, not just one instance.
Do that, and a request for a different contact becomes a straightforward logistics fix, not an incident that damages trust on either side.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
