“The client raised it, but I sorted it on the call.”
For an agency manager, that sentence can sound like good news. Your account manager noticed a problem, handled the conversation and kept the relationship moving. You have twenty other things to get through. You move on.
But what, exactly, was sorted?
The awkwardness? The misunderstanding? The work the client was waiting for? Or the client's concern that the same thing would happen again?
Those are different outcomes. In a busy agency, they can all get compressed into the same update: handled.
We call this the “I fixed it” trap. A difficult moment gets handled well, and the underlying concern disappears from the agency's view before anyone has checked whether it was resolved.
The account manager may have done a good job on the call. The problem is what the agency assumes happened next.
The moment a concern disappears
Consider a common situation: a client wants more say in campaign decisions.
A client tells their account manager: “We keep finding out about changes after they've happened. I need to know before you change the plan.”
The AM apologises, explains why the last change happened and promises to involve them earlier. The client says, “Okay, thanks. I appreciate it.” The rest of the meeting is productive.
At the internal review, the AM says: “They were a bit frustrated about communication. We talked it through. All fine now.”
Nothing in that update is necessarily dishonest. The tension eased. The client accepted the explanation. The AM intends to follow through.
But the client asked for a change in how decisions are made. That needs to reach the people making those decisions. Someone needs to agree which changes require advance notice, who contacts the client and what happens when the usual AM is away.
If none of that happens, the next change can produce the same complaint. This time with a different opening:
“We already spoke about this.”
The first conversation was useful. The agency treated it as the end of the work.
Why “handled” is such an easy answer to accept
An account manager has a reason to feel relieved when a difficult call ends well. A manager has a reason to welcome a concise update. Neither wants every uncomfortable conversation turned into a formal incident.
That is how a perfectly reasonable shortcut becomes a blind spot.
The AM reports the conversation's ending. The manager hears the problem's ending. The client is still waiting for something to change.
Across several teams and hundreds of clients, that distinction matters. Leadership cannot listen to every call or reconstruct every concern. It relies on summaries. If the summary removes the unfinished part, the person who could help never knows they are needed.
A more specific update would have kept that unfinished work visible.
Four stages that should not mean the same thing
When reviewing a client concern, separate the conversation from the work it creates. These four stages give the AM and their manager a shared way to describe what has happened.
1. Discussed
The client raised a concern and the team addressed it in conversation.
That tells you the issue has been heard. It does not yet tell you whether further work is required.
Ask: “What did they need us to explain or change?”
In our example, the client wants advance notice of changes. A good apology matters, but it does not establish the new process.
2. Action agreed
The team and client understand what will happen next. The action has an owner and an agreed date or trigger where appropriate.
Ask: “Who is doing what, and when does it need to happen?”
For this client, the next action might be to agree which campaign changes need their input, record that agreement and brief the delivery team. The AM owns the client conversation; the delivery lead owns making the process work inside the team.
Avoid “we'll communicate better”. Nobody can reliably tell when that task is finished.
3. Action completed
The promised work happened. There is something concrete to point to: a revised plan, a delivered explanation, a corrected report or a change in the approval process.
Ask: “What has actually changed since the conversation?”
The delivery team now has the agreed approval requirements. The next proposed change is shared with the client before it is made. That is progress beyond reassurance.
4. Resolution confirmed
You have checked whether the fix addressed what bothered the client. For a small misunderstanding, their answer on the call may be enough. A recurring problem needs evidence that something has changed.
Ask: “What tells us this addressed the concern they raised?”
A specific check after the next change might be: “Did this give you enough notice and the right opportunity to influence the decision?”
“Thanks for sending that” confirms receipt. It may not answer that question.
These stages help you distinguish what happened. They do not require four meetings, four forms or four separate tasks. One clear conversation may cover several stages. The important thing is that the record does not jump from an apology to an assumption.
What a useful update sounds like
Compare these two internal updates.
The update that closes the discussion too early:
“Client unhappy about communication. Spoke to them. Sorted.”
The update a manager can act on:
“Client wants advance notice before campaign changes. We acknowledged the last change was shared too late. Alex will agree the approval requirements with them on Thursday; Priya will brief delivery afterwards. We will check whether the process worked after the next change. The client accepted the explanation; the process change is still open.”
The second update gives the manager a reason to stay informed without taking the account away from the AM.
It also makes absence and handover easier. A covering colleague can see what was promised, rather than discovering it when the client asks why it has not happened.
Ask for evidence without putting the AM on trial
If “what tells us it's resolved?” sounds like “prove you did your job”, people will learn to avoid the conversation.
Make the question about the work that remains. Start by recognising what the AM handled well:
“You got the concern into the open and kept the conversation constructive. What still needs to happen on our side?”
Then decide whether they need support. Perhaps delivery owns the fix. Perhaps the client needs a commercial decision the AM cannot make. Perhaps the promise made on the call needs adjusting before the team commits to something unrealistic.
The AM should leave that discussion knowing what to do and who will help.
When the concern requires authority beyond the AM, involves a serious complaint or includes an explicit request to end the engagement, bring in the appropriate manager promptly. Do not wait for the routine portfolio review simply because the call ended politely.
Do not turn every concern into an endless open case
There is a risk at the other extreme: making the process so heavy that nobody wants to record anything.
Match the follow-up to the concern.
A factual misunderstanding may be resolved during the call. If the client asks which period a report covers, you explain it and they confirm that answers the question, further follow-up may add nothing.
A repeated complaint about late work needs more. Agreeing a new deadline is progress, but the concern about reliability may need to be reviewed after the next delivery.
If the client has not replied, record that accurately. “Action completed; awaiting confirmation” is useful. Treating silence as satisfaction is an assumption. Treating it as proof of dissatisfaction is another.
Agree a sensible follow-up rather than chasing indefinitely. If the concern becomes irrelevant because priorities or scope change, record why it no longer needs action. The point is to preserve the reason for the decision, not to keep every issue open forever.
A five-line record for your next account review
You can use this in the account notes or review document you already have:
- Client concern: what they said, with the relevant date and source.
- Agreed response: the explanation, action or decision needed.
- Owner and timing: who is responsible and the agreed date or next relevant event.
- Current stage: discussed, action agreed, action completed or resolution confirmed, with a short reason.
- Next check: what we still need to learn, and when we will revisit it.
Use the client's own words where you can, and link back to the conversation so a colleague can check the context. If a commitment changes, update the record rather than leaving two different promises circulating.
This record can be brief. Its value is that “handled” stops being the only thing the next person knows.
Try this in the next team meeting
Choose one recent concern described as “sorted”. Pick a normal case rather than the biggest crisis in the portfolio.
Ask the account owner what the client needed, what the team agreed and what happened afterwards. Identify which stage the evidence supports. If something remains open, agree one next action and the person who owns it.
Then notice where the gap came from. Was there no owner? Did delivery never hear about the promise? Was a sent email mistaken for a confirmed resolution? Was the concern actually answered on the call, with that answer missing from the summary?
That tells you what to improve. A blanket instruction to “communicate more” does not.
For the wider relationship-management picture, read our complete guide to agency client retention.
Where Rapport Studio fits
This is the kind of continuity Rapport Studio is built around: bringing client context, concerns and follow-through into view so the next conversation starts with an understanding of what happened before.
See which relationships need attention, understand why, and know what to do next.
Explore how Rapport Studio works to see how its approach connects client context, preparation and account management.
The next time you hear “I sorted it on the call”, ask what happened next.