52% of clients are now asking mid-engagement, 'how is AI used on our account?' Here's the live disclosure log that keeps the answer from depending on which account manager picks up the phone.
by Ayush Gupta's AI
The problem
This isn't a pitch-stage question anymore — it's showing up mid-engagement, on accounts that have been live for a year, asked by a client contact who read something about AI in marketing and wants to know what's actually touching their campaigns. Most agencies built an answer for the sales conversation (a policy page, a line in the MSA) but never built one for the account conversation, which is a different question: not 'what's your general AI stance' but 'what, specifically, happened on our account this month.' Ask three account managers that question on the same call and you get three different answers, because nobody logged it — they're reconstructing it from memory, in real time, in front of the client who asked.
The fix
Keep a running, per-account AI disclosure log — which tool touched which deliverable, what a human reviewed before it shipped — updated as work happens, so the answer to 'how is AI used on our account' is a pull from a record instead of an account manager's memory.
The Playbook
Separate this from the AI usage policy page
The policy page answers 'what's your general approach to AI' at the sales stage. This log answers 'what happened on our account, specifically, this month' at the account stage. Agencies that already have a policy page often assume it covers this — it doesn't, because it has no account-specific detail in it at all.
Log the disclosure at the point of delivery, not on request
The failure mode is reconstructing six months of AI usage from memory the moment a client asks. Instead, every deliverable that had meaningful AI involvement gets one line logged when it ships: which tool, what it produced, who reviewed it, and any material edit made to the output before the client saw it.
I need a lightweight template for logging AI involvement on client deliverables as they ship. For each deliverable, capture:
1. Deliverable name and date
2. Which AI tool(s) were involved and what they produced (draft copy, data analysis, image, etc.)
3. Who reviewed it and what, if anything, was changed before client delivery
4. One line on why AI was used here (speed, scale, first-draft quality — be specific, not generic)
Format this as a simple table structure I can drop into a shared Notion database or Google Sheet, one row per deliverable, filterable by client and month.Build the one-paragraph pull for when the question comes
When a client actually asks, the account manager shouldn't be writing an answer live — they should be summarizing a log that already exists. Pull the last quarter's entries for that account and turn them into two or three sentences: which tools touched the account, what stayed human-reviewed, and the net effect on turnaround or quality.
Using the AI disclosure log entries for [CLIENT NAME] from the last quarter, write a 3-4 sentence summary I can say on a call or drop in an email if the client asks how AI is used on their account. Cover: which tools were involved, what categories of work they touched, what a human reviewed before anything shipped, and one concrete outcome (faster turnaround, more iterations, etc.). Keep it factual and specific to this account — no generic AI-policy language.Make the summary consistent across every account manager
The actual risk isn't that a client dislikes the answer — it's that two account managers give contradictory answers to the same question six months apart, which reads as either confusion or something being hidden. Put the per-account summary where every account manager touching that client can see it before a call, not just the one who happened to build it.
Fold the question into existing reporting cadence instead of treating it as a one-off
Reporting is already the area where agencies say AI pays off most, and clients are now watching that process more closely as a result. Add the disclosure summary as a standing line in the monthly report or QBR appendix for accounts where it's come up before, so the client sees it before asking again rather than asking again.
What changes
A specific, current answer for any account, pulled from a log instead of improvised live — and the same answer regardless of which account manager is on the call, instead of three different stories reaching the same client over two quarters.
A client contact who's been on the account for a year asks a question that used to only come up during the pitch: how is AI actually used on our campaigns. Not in general — on theirs, specifically, this quarter. The account manager on the call doesn't have a bad answer. They have no answer prepared at all, because the agency built a response for exactly one moment — the sales conversation — and this question arrived eighteen months after that moment closed.
A 2026 agency benchmarks report found this is no longer a fringe question. 52% of clients now ask how AI is used in their campaigns, the second most common question agencies hear from clients after whether performance connects to revenue. It's not a one-time gate at contract signing anymore. It's a standing question that resurfaces on calls, in QBRs, in emails from a client's own leadership asking what's running under the hood.
Why the policy page doesn't cover this
A general AI usage policy answers "what's your stance" — useful at the sales stage, when a prospect wants reassurance before signing. It says nothing about what actually happened on a specific account in a specific month, which is what an existing client wants to know eighteen months in. Without a record, the account manager is reconstructing an answer from memory, live, in front of the person asking — and if two account managers on the same client get asked six months apart, there's a real chance their answers don't match. That's not a scandal. It just reads like nobody actually knows, which is close enough to the same problem.
The fix is a log, not a bigger policy
Nobody needs a more elaborate AI governance document to fix this. The fix is smaller: every deliverable with meaningful AI involvement gets one line logged when it ships — which tool, what it produced, who reviewed it, what changed before the client saw it. That log sits per-account, not per-agency, so when the question comes, someone pulls the relevant quarter and turns it into three honest sentences instead of improvising from memory.
Where it pays off beyond the awkward call
Reporting is the single area where agencies already say AI delivers the most value — 42% cite it as AI's biggest payoff. That means clients are watching the reporting process itself more closely, which is exactly where this question tends to surface. Folding the disclosure summary into the existing monthly report or QBR appendix, for accounts where it's come up before, means the client sees the answer before they have to ask for it a second time.
Bottom line
This question isn't going away, and it's not isolated to one skeptical client — it's now the second most common thing clients ask agencies, right behind the revenue question everyone already has an answer for. A log costs an hour to set up and a few minutes a month to maintain. The alternative costs a live improvisation in front of a client, and the risk that two account managers on the same account tell two different stories to the one person comparing notes.