Recovering Service After Repeated Transfers

An insured administrator who calls in after being bounced between three departments is not upset about the original problem anymore. They are upset about retelling it a third time. As the account manager, your job is to stop the bouncing, take ownership of the coordination, and give the customer one voice to follow until the issue actually closes.

Why this conversation goes wrong

Transfers happen because billing and certificate issuance usually sit with different teams, and each rep can only answer the piece that belongs to them. A billing rep hears a certificate question and routes it away. A certificate rep hears a billing question and does the same. No single person ever owns the whole request, so the customer ends up doing the coordination work themselves, explaining the same background three or four times to three or four different people.

By the time the call reaches you, the administrator is not just frustrated about an invoice or a document. They are testing whether your agency can actually manage anything, or whether every request turns into a maze. If you respond by trying to solve both issues yourself on the spot, you often make a promise you cannot keep, since you do not control billing adjustments or certificate issuance directly. If you respond by explaining why the transfers happened, you sound like you are defending the process instead of fixing it. Either move confirms the customer's fear that no one is actually in charge.

How to prepare

Before you call the administrator back, pull the account and read whatever notes exist from the earlier transfers. Do not make the customer repeat details that are already sitting in your system. Identify which team owns the billing question and which team owns the certificate, and confirm you have a specific contact in each queue rather than a general inbox that might sit for days.

Write down the customer's deadline in your own words before you pick up the phone. If a certificate is due to a vendor on Friday, know that cold. Decide in advance what you can commit to today, which is usually a documented request sent into each queue with the deadline attached, and what you cannot commit to, which is a finished action by a person you do not supervise. That distinction matters once you are on the call, because it keeps you from promising something on someone else's behalf.

What to say

Open by naming the pattern the customer just lived through, and apologize for it without over explaining it. You say, "I know you have already explained this more than once, and I am sorry for that. I am going to take this from here so you do not have to repeat it again."

The administrator answers, "I just need to know if my certificate will be ready before the vendor deadline on Friday, and I still do not understand why my invoice went up this month."

You separate the two issues out loud so the customer hears that you caught both of them. You say, "Those sit with two different teams internally, but you should only have to deal with me. The certificate team owns your Friday deadline, and I am sending them your request right now with that date attached. Billing owns the invoice change, and I am sending them a separate request today. I will call you Thursday afternoon with whatever both teams have confirmed by then, even if one of them is still working on it."

The administrator pushes back a little, "So nothing is actually fixed yet."

You say, "Not yet, and I want to be straight with you about that. What is different now is that one person is tracking both pieces instead of three people who each see only part of it. I will not tell you something is done until the team that owns it confirms it to me directly."

That exchange does three things. It names the issue in plain language so the customer knows it was heard. It assigns each piece to the team that actually owns it, instead of pretending you can resolve either one yourself. And it gives one specific time for the next update, so the customer is not left guessing when to call again.

Mistakes to avoid

Do not promise an outcome that belongs to another team before that team confirms it. Saying "your certificate should be fine" or "your invoice will probably drop" sounds reassuring in the moment, but if either statement turns out wrong, you have now burned the trust you were trying to rebuild.

Do not criticize the other departments in front of the customer, even if the transfers really were mishandled. Comments like "billing should have caught this sooner" make the agency look disorganized rather than making you look helpful, and they do nothing to move the request forward.

Do not try to do another team's work yourself just to avoid coordinating with them. If you attempt to issue a certificate you are not authorized to issue, you create a version that may not match what the certificate team eventually produces, and now there are two conflicting documents in circulation.

Do not close the call without a specific date and time for your next update. A vague "I will follow up soon" puts the burden back on the customer to guess when to check in, which recreates the exact frustration you are trying to fix.

How to practice and score it

This kind of recovery call is hard to get right the first time you try it live, so rehearsing it with a colleague or manager first is worth the time. Have someone play the administrator with two separate issues and one real deadline, then run the call and score three things afterward. First, did you summarize the issue accurately without asking the customer to repeat details already on file. Second, did you name the specific team that owns each piece instead of implying you would resolve it personally. Third, did your closing commitment include an exact date and cover only what you actually control.

A tool like DealSpeak lets you run this scenario against an AI counterpart as many times as you need, so you can adjust your phrasing before you ever use it on a real account. The Insurance practice conversations hub has more scenarios built around the same kind of internal handoff problem, including Rebuilding Trust After a Disorganized Renewalwhich covers a related situation where a customer has lost confidence in your timeline rather than your coordination. If you handle discovery calls as well, Starting a Subcontractor Discovery Conversation works through a different kind of handoff, where you are the one gathering scattered information instead of untangling it.

Recovering trust after repeated transfers does not require fixing everything on the first call. It requires proving that one person is now accountable for the whole request, with a specific plan and a specific date attached. Get that part right, and the customer will wait for the actual resolution without calling back three more times to ask about it.