What the WhatsApp Business App Can't Do With Your Records
The WhatsApp Business app is genuinely good at what it's for: a small business, one or two people, a catalogue, quick replies, away messages. Free, and it works.
It was never designed to be a system of record, and the gap shows up at a predictable point in a company's growth. Here's exactly where.
1. The other party controls your copy
The one most people never think about until it costs them.
When a customer uses "delete for everyone", your copy is deleted too. The only copy was on your phone, and the delete instruction reaches it. Your record of a conversation with your business can be edited by the person you'll be arguing with.
No other business channel works this way. Email, tickets, call recordings — all deliver to infrastructure you control. See when a customer deletes a message.
2. No attribution on a shared number
If three people answer the same number, every outbound message looks identical. There is no record of which human sent which reply.
So when a customer says "your team promised me a refund", you can't establish who promised it, whether it was within policy, or whether it happened at all.
3. No access control
The app has no roles. Whoever has the phone or the linked device can read every conversation, send anything, and delete anything — with no log.
That's not a permission model. It also means offboarding an employee involves a physical device rather than revoking a login. See an employee deleted messages.
4. Records live on a handset
The history belongs to a phone, which means:
- Phone lost or stolen → records gone
- Employee leaves with it → records and relationships gone
- Backup restored to fix something else → months of messages gone
- New phone set up without restoring → gone
None of these require anyone to act badly.
5. Search is almost unusable at volume
You can search within the app, but there's no cross-conversation view, no contact history, and no way to answer "everything we hold about this person" — which is exactly what a subject access request asks for. See exporting a conversation.
6. No retention policy
You cannot set a retention period, apply it by category, or demonstrate you've applied it. Records persist until someone clears a chat for space. That's not a policy, and it's a weak answer in an audit. See compliance and record-keeping.
7. Limited linked devices
The app supports a small number of linked devices, which caps how many people can genuinely work the number at once. It's the constraint most teams hit first, usually before they've thought about any of the above. See WhatsApp Business app for teams.
When these actually start to matter
Roughly in this order:
| Stage | What breaks first |
|---|---|
| 1–2 people, low volume | Nothing. The app is fine |
| 3+ people on one number | Device limits, then attribution |
| Regular disputes | Deleted messages, no proof of what was agreed |
| First staff departure | History leaves with the phone |
| Regulated industry or an audit | Retention, access control, subject access requests |
| Real volume | Search — the history exists but is unusable |
If you're at the first row, the app is the right tool and this article is premature. Most businesses discover the other rows one incident at a time.
What changes with a connected workspace
Connecting your existing number to a platform that stores messages server-side changes the substrate rather than the channel. Customers message the same number and see a normal WhatsApp chat.
| Business app | Connected workspace | |
|---|---|---|
| Customer deletes a message | Your copy goes too | Kept, tagged "Deleted on WhatsApp" |
| Who replied | Unknowable | Named agent |
| Access control | Whoever holds the phone | Per person, per role |
| Staff departure | History leaves | Revoke a login |
| Search | Within a chat | Across all conversations |
| Retention | None | Your policy |
| Team size | Device-limited | Whole team |
Tenashi does this on your existing number, with a shared inbox, chat assignment, CRM pipeline and permissions.
Scope: chats with your own connected business number, from the date you connect it.
Pricing is flat, from $18/mo.
Get started → · See every feature
FAQ
Does the WhatsApp Business app keep deleted messages?
No. When a customer deletes a message for everyone, your copy is removed as well, because the only copy was on your phone. The app has no server-side record and no way to retain what was deleted.
Can I see which team member sent a WhatsApp reply?
Not in the Business app. Every outbound message from a shared number appears identically, so there's no way to attribute a promise or a quote to a specific person. Individual agent logins on a connected platform are what provide this.
How many people can use the WhatsApp Business app on one number?
Only a small number of linked devices, which is the constraint most growing teams hit first. Beyond that you need a platform that supports the whole team working the same number.
What happens to WhatsApp records if an employee leaves?
On the Business app they typically leave with the phone, along with the customer relationships. There's no way to revoke access without taking the device, which is why server-side storage with individual logins matters at that point.
Can I set a retention policy in the WhatsApp Business app?
No. There's no retention setting, no way to apply periods by category, and no way to demonstrate consistent application — which becomes a problem in any regulated context or audit.
When should a business move off the Business app?
Usually when a third person needs the number, when disputes about what was agreed start recurring, or when the first staff departure takes history with it. Below that, the free app is genuinely adequate.
The Business app is a good messenger. It just isn't a record. Know which one you need. Get started.