Deleted WhatsApp Messages in Agencies: Scope Creep, Approvals and Client Disputes
Agency work is defined by two questions: what was in scope, and what did the client approve.
Both get answered on WhatsApp, because that's where clients actually reply. And both can be deleted by the person you'll eventually be arguing with.
The scope creep pattern
The classic sequence:
- Statement of work signed, scope defined
- Client adds a request in chat: "while you're at it, can we also do X"
- Your team does X
- Invoice includes X as additional work
- Client: "X was always part of the brief"
- You scroll back — the message asking for X is a grey box
The deletion isn't usually malicious. Clients tidy chats, or delete a message they thought was badly worded and re-send. The effect is identical: the moment scope expanded is undocumented, and you wrote it off.
Across a year of projects, that's a meaningful share of margin.
The approval pattern
Worse, because it's more expensive.
A designer sends a proof. The client approves in chat. Print runs, campaign launches, the site goes live. Then the client says they never approved that version — and the approval message is gone.
For anything with production costs, an unverifiable approval is a direct loss.
The "we discussed it on a call" pattern
Related and just as costly. Most agency decisions happen on calls and get half-confirmed in chat. If the chat half gets deleted, you have nothing at all.
Why agencies are structurally exposed
Multi-channel chaos. The same project lives across email, Slack, a project tool, and WhatsApp — and the binding decisions land in WhatsApp because that's where the client is fastest.
Long projects, late disputes. A scope argument surfaces at final invoice, months after the message. Phone-based recovery expired long ago.
Account manager turnover. The AM leaves and the client history goes with the phone.
Client-side turnover. The person who approved the work leaves the client. Their replacement has no knowledge of it and no reason to accept your recollection.
That last one is underrated: often nobody deleted anything, the approver simply left, and your only evidence is a chat on a phone.
The habits that protect margin
Make approvals explicit and structured. Not "looks good?" but:
APPROVAL — Project 118, Homepage v3
Approving: layout, copy, imagery as attached
Cost if changed after approval: £850 rework
Reply APPROVED to proceed to build.
Your message, an explicit reply, a stated consequence. This single habit resolves most approval disputes.
Log scope changes as change requests. When a client asks for something in chat, respond with a one-line change note: "Noted — adding X. This is outside the current SOW and will be quoted at £Y. Confirm to proceed?" Now scope creep is a decision, not a drift.
Summarise calls into the chat. "Confirming from our call: we're proceeding with option B, delivery 30th, additional £1,200." Sent immediately after, it becomes the record.
Canned replies make all three of these a few seconds of work rather than a discipline problem.
Keeping the trail
The habits fail on one point: the client can delete their APPROVED.
When your agency number is connected to a platform that stores messages server-side on arrival, the message is saved when delivered. A later deletion reaches the phone, not the stored copy. In Tenashi it stays in the thread tagged "Deleted on WhatsApp" — the approval, plus the fact it was withdrawn.
For an agency this also solves the adjacent problems:
- Per-account-manager attribution, so you know who promised what
- History stays when an AM leaves, instead of walking out on a handset
- Search across every client conversation, so project 118's approval is findable in March
- Contact and deal records per client rather than a chat list — CRM pipeline
Scope: chats with your own connected agency number, from the date you connect it.
See also WhatsApp CRM for agencies.
Pricing is flat, from $18/mo.
Get started → · See every feature
FAQ
A client deleted the message approving our work — what can we do?
From the WhatsApp Business app, nothing — their deletion removed your copy. With a connected inbox storing messages on arrival, the approval stays in the thread tagged "Deleted on WhatsApp". Going forward, structure approvals as an explicit reply to your own message.
How should agencies record client approvals on WhatsApp?
Send a structured approval request naming exactly what's being approved and the cost of changing it afterwards, and ask for a specific word like APPROVED. That produces one artefact rather than an ambiguous "looks good" buried in a thread.
How do we stop scope creep over chat?
Respond to every additional request with a change note stating it's outside the current scope and what it will cost, and ask for confirmation before proceeding. That converts a casual ask into a decision with a price attached.
What happens to client history when an account manager leaves?
On phone-based setups it leaves with them. With server-side storage and individual logins you revoke access and the conversation history — including approvals and scope changes — stays with the agency.
The client's approver left and their replacement disputes the work. What helps?
A complete, timestamped thread showing who approved what and when. Nobody needs to have deleted anything for this to be a problem — it's simply that recollection doesn't transfer between people, and a record does.
Should approvals happen on WhatsApp at all?
They happen there whether or not you intend it, because that's where clients reply fastest. Better to structure them properly and store them reliably than to pretend the decision was made somewhere more formal.
Agencies don't lose money on the work. They lose it on the approval nobody can find. Get started.