Quick Answer: Tell the client the result first, explain the most likely cause plainly, bring a specific plan, and invite their questions. Do not bury the news, and do not invent a reason you cannot support.
Every agency has a month where the numbers drop. What matters is how you handle the conversation.
The advice from agency guides, including those from Swydo, DashThis and Reportei, is consistent: be honest, explain the cause, and arrive with a plan. These are vendor blogs, so read them as common practice, not research. This post gives you a structure and scripts based on that common ground.
Before the call: four checks
Do these before you say anything to the client.
- Confirm the drop is real. Check revenue in the client's store or CRM, not just the ad platform. Broken tracking looks exactly like poor performance
- Find the most likely cause. Split the result into its parts: spend, clicks, conversion rate, revenue per sale
- Check the context. Compare with the same period last year, and with your other clients, to see whether it is seasonal or market-wide
- Decide the first action. Do not call without one
The four-step structure
1. Lead with the result
Say it in the first sentence. Clients get more anxious when they sense you are working up to bad news.
2. Explain the cause, honestly
Give the most likely reason in plain language. Say "most likely" when you are not certain. Do not offer a long list of excuses.
3. Bring the plan
Name the specific actions, with dates. A problem with a plan is a very different conversation from a problem without one.
4. Invite questions
The client knows their business. Ask what they have noticed, and whether anything changed on their side.
Five scripts
These are examples to adapt, not lines to read out.
When spend went up and leads did not
"Leads were down 18% this month while spend was about flat. The most likely reason is that two of our campaigns were competing for the same searches and pushing up the cost of each click. This week we are pausing the weaker one and moving the budget to the one converting. I expect cost per lead to ease within two weeks, and I will confirm it in the next update."
When tracking broke
"I want to flag something before you see the report. Conversions show as down 40%, but orders in your store are only down 5%, which tells us our tracking stopped recording some conversions on the 12th. That was on us to catch sooner. It is fixed as of this morning, and I have set up a daily check so we will see it within a day if it happens again."
When it is seasonal or market-wide
"Traffic is down 22% on last month, but it is down about the same on last year's pattern at this time, and the other accounts in your category we manage show the same dip. So this looks seasonal rather than something we did. To make the most of the quiet period, I recommend we test two new offers now, so we are ready when demand returns."
When organic traffic dropped and you do not know why yet
"Organic traffic fell about 15% over the past two weeks. I have ruled out a technical issue in Search Console and a ranking loss on your main terms, and I am still looking at two possible causes. I will have a clearer answer by Thursday, and I will tell you what I find, including if it turns out to be something we should have caught."
Notice that this script does not blame an algorithm update. If you cannot show a cause, say you are still investigating.
When results are fine but the client feels uneasy
"The numbers are on target, but I know the last two weeks felt slower. Here is what changed: the sales you saw were concentrated in the first half of the month. I want to understand if that is a pattern, so I would like to look at your order timing together."
What to avoid
- Hiding the result in an appendix. It reads as avoidance
- Blaming without evidence. "An algorithm update" is the classic version
- Long apologies. One clear statement of what happened is enough
- Promising a fix you cannot guarantee. Say what you will do and when you will report back
- Waiting for the monthly report. Tell them when you have confirmed it
Put it in writing too
After the call, send a short note with the same three points: what happened, the likely cause, and the plan with dates. It gives the client something to forward and gives you a record.
Where tools can help
Finding the cause is the slow part, because the evidence is spread across ad platforms, analytics and the store.
LedgeSpace's RUSHA, the optional AI add-on, is set up to give you an internal version first. It is blunt and states what changed, why and the recommended action, and a separate client-ready version is written alongside it with the numbers locked to match. Its background scans also draft an insight when a client's last 7 days move more than 2 standard deviations from their usual baseline, so you can hear about a problem before the client does. Nothing client-facing goes out until you approve it. It checks every number against your connected data, but it gives likely causes, not certainties, so you still need to read it before you speak.
See how to explain a metric change to a client for the what, why and next structure, or start a 14-day free trial with no credit card.
