Recovering trust after poor relay service support

A customer who relies on relay service and calls in after a string of rushed agents is not upset about hold times. The customer is upset about being treated as an inconvenience because of how they communicate. As a retention specialist, you are often the first person who slows down enough to notice a recorded preference that earlier agents ignored. That noticing is most of the recovery. Handle it well and you can save the account. Handle it poorly and you confirm every frustration the customer already had.

Why this conversation goes wrong

Relay service adds a short delay between what the customer says and what you hear, because a communicator is voicing or typing on their behalf. Agents under pressure to close calls fast often read that pause as disengagement and start talking over it or rushing the customer along. Other agents skip the account profile entirely and ask the customer to restate a communication preference that was already recorded weeks earlier. Each repeat of that request tells the customer that nothing they said actually stuck. By the time the account reaches you, the customer has usually explained the same preference three or four times to three or four different people. Then a real issue shows up, often a billing question, and the customer assumes it will go the same way. You are not just fixing a billing item. You are proving that this call will be different from the last five.

How to prepare

Pull the account before you say a word to the customer. Open the approved profile screen, not just the notes field, and confirm what communication method is already on record. Some systems store the preference correctly but fail to display it on an older screen that other agents still use, so check more than one source if your tools allow it. Know the difference between a customer choosing relay service because it fits their needs and a customer being stuck with a workaround because nobody set up their preferred method properly. Those are different conversations. Also know who actually owns two things before the call ends, the billing team that will review the pending charge and whoever maintains the profile display tool if you find a mismatch. If you cannot name an owner for both, you will end the call with a vague promise instead of a concrete next step, and a vague promise is exactly what got this customer here.

What to say

Open by naming the pattern instead of apologizing in general terms. A flat apology sounds like every other agent this customer has already heard.

Leah said, "Why do I have to explain this every time? I already told you people how I want to talk."

Daniel replied, "You should not have had to repeat that. Your communication preference is already recorded on the account, and I have it open in front of me right now. Before we get to your billing question, I want to confirm it still matches what you want, then make sure billing gets it along with your issue."

Leah asked why it keeps disappearing if it is already recorded. Daniel said, "It is stored correctly on the account, but it is not showing up on one of the older screens some agents still use. That is a display problem on our end, not something you did, and I am reporting it to the team that owns that screen so it stops happening to you."

Leah asked for the billing follow up to come through relay service, the same way this call is happening. Daniel said, "I will note that method on the request and tell you exactly who will contact you and when, so you are not left guessing."

Notice what Daniel did not do. He did not promise every future agent will get it right, because he cannot control that. He named the specific failure, relay service and the display gap, and gave two concrete actions, a profile confirmation and a routed report, plus a third for the billing handoff. That combination is what rebuilds trust, not the apology itself.

Mistakes to avoid

Do not promise a perfect future. Telling a customer that this will never happen again sets you up to be blamed personally the next time an unrelated agent slips, and it also sounds hollow because you cannot actually guarantee it. Do not rush the pacing of the call because relay service takes longer than a standard voice call. Rushing is exactly the behavior that put the customer in front of you in the first place. Do not treat the repeated explanation as a customer complaint to smooth over rather than a system failure to name. If you skip past it with a quick apology and move straight to billing, you leave the real problem unaddressed and it will happen again on the next call. Do not close the conversation without naming who handles the billing item and who handles the display bug. Two different owners, two different fixes, and the customer deserves to know both instead of a single generic reference to a team.

How to practice and score it

Review a completed profile update with a supervisor and physically trace how the preference field moves from the account to the receiving team, so you know where it can drop out before it happens on a live call. In roleplay, practice the acknowledgment line by itself before you ever touch an account detail, because a specialist who jumps straight to the fix without naming the pattern first sounds like every rushed agent the customer already dealt with. A supervisor scoring this call should check for three things, respectful pacing that matches relay service rather than fighting it, a confirmation step that uses the approved profile instead of just taking the customer's word for it, and a clear named owner for both the billing question and the display issue. DealSpeak is built for exactly this kind of rehearsal, letting a retention specialist run this scenario against an AI counterpart and get scored on those same points before facing a real customer. You can find more scenarios like this one among the Contact Centers practice conversationsincluding how to recover a cancellation risk after a promised feature is missing and how to respond when a customer disputes a renewal notice.

A customer who uses relay service is not asking for special treatment. They are asking for the same attention to detail every other customer gets, applied consistently instead of dropped by whichever agent happens to answer. Get the acknowledgment right, confirm the record instead of guessing, and name an owner for every open item, and the account has a real reason to stay.