The Half-Built Communication Protocol

Your status updates are perfect. Your feedback loop doesn't exist.

You can run a flawless ticket – fast response, clean resolution, zero errors – and still lose that client six months from now, because somewhere in the middle of all that good work, you never once asked them how it actually felt to be your customer.

The System Working As Designed

Most companies build a communication protocol that only runs in one direction. Status goes out. Updates go out. "We're working on it" goes out. And if you've done the work right, someone even confirms receipt (which matters more than people think). Closed-loop confirmation isn't optional on anything above a low-priority ticket. If you send an update and get no acknowledgment, you don't actually know if it landed. "I emailed them" is not the same as "they got it and understood it." Build that discipline into your protocol: who's included, what gets said, what detail level, when the loop opens and closes, where the record lives, and how it travels (phone, email, portal, whatever fits the moment). Match the weight of the communication to the weight of the issue. A priority-three ticket doesn't need the same audience as a priority-one outage.

That's the system working exactly as designed. And it's still incomplete, because a status update, even a perfect one, only reports on the ticket. It never asks about the relationship.

The Question Nobody Volunteers

Your client has an experience of working with you that's running the whole time, quietly, underneath every ticket you close. And if nobody from your company ever asks them directly what that experience feels like, they don't just keep it to themselves. They talk about it – to their own team, and eventually to someone outside your company entirely. Think about how that plays out anywhere else in life. Someone who feels a little neglected, a little unheard, doesn't usually sit with that feeling quietly. They mention it. To a coworker, a friend, whoever's willing to listen. And the moment your competitor gets even one conversation with that person, they're going to ask the exact question you never did: "What's missing?" That's not a hard sell. That's just someone paying attention where you weren't.

The Slow Goodbye

The client who leaves feels sudden, even though it never was. It's never one bad ticket. It's a slow accumulation of expectations nobody surfaced, because your protocol was built to report status, not to solicit the truth. "Are you happy with us?" and "Would you refer us?" are not CEX questions; they're temperature checks that let people say yes without saying anything real. The question that actually protects the relationship is narrower and harder: “What do you expect from us that you're not getting right now?” That's the one people don't volunteer. You have to go get it.

Close the Other Loop

This is the piece that was always missing from a protocol built purely around reporting: a deliberate, closed-loop channel for pulling feedback, not just pushing updates. Same discipline, same rigor… you just point it in the other direction. If you're rolling out a new process – say, for example, you’re implementing my Agile Service Delivery™ (ASD) methodology – or if you’re just running steady-state service, that ongoing conversation with your clients must be scheduled and owned the same way status reporting is. Not, "Reach out if there's a problem," but rather a defined cadence, a specific person accountable for asking, and a real question instead of a Yes-or-No.

Build it the same way you'd build any part of your system, one piece at a time, not all at once. Take your last five closed tickets and check two things: 1) Did anyone confirm they received the final update? And 2) Did anyone ask, separately, whether the experience matched what they expected going in? If the answer to either is NO, you don't have a communication protocol. You have half of one. And the missing half is the one that actually keeps clients from talking to someone else.

Start This Week

Pick one client relationship you haven't checked on lately and ask them the real question. Not, "Are you happy?" not, "How are we doing?" Ask what they expected from you that they're still not getting. You already know what level you've delivered. That's your number. The number that keeps a client is the gap between what you delivered and what they expected walking in. Go find that number before your competitor does.

_{Image by iLixe48 | Envato}