When a Customer Sends Abuse and Then Deletes It
An agent takes an abusive message — threats, slurs, something sexual. Ten minutes later the customer thinks better of it and deletes it for everyone.
The agent is shaken and wants it escalated. You open the chat and find a grey placeholder. The incident is now one person's account of something that officially didn't happen.
This is a staff welfare problem before it's a records problem.
Why this pattern is so common
Abuse sent in anger is frequently regretted. The delete window is just over two days, which is ample. Many abusive messages are withdrawn within the hour.
That produces a specific harm: the agent experienced it, and the organisation has no evidence it occurred. If your process requires evidence to act — to ban a customer, refuse service, or report to police — the agent is told, in effect, that what happened to them can't be actioned.
Do that twice and people stop reporting.
What it costs beyond the incident
- Staff trust. An agent who reports abuse and watches it go nowhere learns not to report.
- Repeat offenders. Without records, a customer who abuses agents monthly looks like a first-time incident every time.
- Legal exposure. Employers have duties around workplace harassment including from third parties. "We had no evidence" is a weak answer when the reason is that your system discards it.
- Escalation options. Police reports, platform reports and legal action all need the content.
What to do in the moment
Regardless of tooling, train agents on this:
- Screenshot immediately. Before anything else. It's the fastest permanent copy available.
- Check notification history on Android, if it's enabled — the text may be in the system log for about 24 hours. See the Android method.
- Write it down at once. What was said, as close to verbatim as possible, the time, and who saw it. Contemporaneous notes are far weaker than the message and far stronger than a recollection given a week later.
- Tell a manager the same day, even if nothing formal follows yet.
- Don't reply in kind, and don't delete the conversation.
Point 3 is the one to drill. A note written within minutes carries real weight; the same account given in a meeting two weeks later carries much less.
The structural fix
The reason the evidence vanishes is that your only copy is on a phone the delete instruction reaches.
When your number is connected to a platform that stores messages server-side on arrival, the message is saved when delivered. A deletion afterwards reaches the handset, not the stored copy. In Tenashi it stays in the conversation tagged "Deleted on WhatsApp" — the content, the timestamp, and the fact that the sender tried to withdraw it.
That last part matters in an escalation. Someone who sends abuse and immediately deletes it is demonstrating awareness that it was wrong.
Related capabilities that help here:
- Attribution, so you know which agent received it — chat assignment
- Internal notes on the conversation for the contemporaneous record — internal notes
- Search across conversations, so a repeat offender is visible as a pattern rather than a series of isolated incidents
- Contact records, so a flag on that customer persists — contact management
Scope: chats with your own connected business number, from the date you connect it.
Make it policy, not improvisation
Write down what happens when abuse arrives:
- The agent is not expected to continue the conversation
- Screenshot and internal note, immediately
- Reported to a named person the same day
- A decision recorded: warning, service refusal, block, report
- The contact flagged so any future contact is visible
- The agent checked in on afterwards
Having the record is what makes steps 4 and 5 possible. Without it, every incident restarts from zero.
Pricing is flat, from $18/mo.
Get started → · See every feature
FAQ
A customer sent an abusive message and deleted it — can we still act?
If the number is connected to a platform storing messages on arrival, the message is retained and tagged as deleted, so it can be escalated normally. Otherwise you're relying on a screenshot, Android notification history within about 24 hours, or a contemporaneous note.
What should an agent do immediately after receiving abuse?
Screenshot it before anything else, write down what was said and when while it's fresh, and tell a manager the same day. A note written within minutes carries far more weight than an account given weeks later.
Does a deleted abusive message still count as harassment?
The deletion doesn't undo the fact that it was sent and received. What deletion removes is your ability to evidence it, which is why capturing it immediately — or storing messages server-side — matters for any subsequent action.
Can we ban a customer based on a deleted message?
That's a business decision, but it's far easier to defend when you can show what was sent. A stored record with a deleted tag supports the decision; a recollection alone leaves it open to challenge.
How do we spot repeat offenders?
Search across conversations and a flag on the contact record. Without stored history, a customer who abuses agents regularly appears as a new incident each time, because nobody connects it to previous ones.
Is there an employer duty here?
In many jurisdictions employers have obligations regarding harassment of staff by third parties, including customers. A system that discards the evidence makes those duties harder to discharge — take local advice on what applies to you.
An agent who reports abuse should not be told there's no proof it happened. Keep the record so the incident survives the sender's regret. Get started.