What is different about running WhatsApp support where WhatsApp is the internet

In markets where WhatsApp is the default way to reach a business, the channel behaves differently: media is the message, voice notes are normal, languages mix mid-sentence, and data costs. Support tooling built on the assumption of short typed English messages fits badly.

Media is the message, not an attachment

A customer sends a photograph of the broken part, a screenshot of the payment confirmation, a picture of the label. This is not laziness; it is the most information-dense and least error-prone thing they can do, and it is free where typing a long reference on a small keyboard is not.

The practical consequences are concrete: an inbox that shows [image] instead of the image is unusable, media has to be searchable and downloadable months later, and media handling is a core feature rather than a nice-to-have.

Voice notes are normal

For a lot of people a thirty second voice note is faster and clearer than typing, particularly across languages. Two things follow: your team needs to be able to listen to them without downloading anything, and replying with a voice note is often the right answer rather than an informality.

Languages mix inside one sentence

"Nataka kujua if the order imefika" is one sentence and it is normal. Keyword matching built for one language fails on it, and so does sentiment analysis, and so does anything that routes on detected language. Build auto-replies on unambiguous keywords the customer is told to use, and let people handle the rest.

Data costs money

A customer on a daily bundle counts megabytes. That reframes several decisions: compress images hard, do not send a 40 MB video when a photo does, do not send five messages where one would do, and never make somebody load a web page to read something you could have said in the chat.

Phones are shared, and numbers move

One handset may be used by several people, and numbers change hands more often than in markets with long contracts. Two rules follow: do not treat a phone number as a durable identity for anything sensitive, and make sure a returning "customer" who is actually a new person on a recycled number does not see the previous holder's order history.

Payment happens in the chat

Mobile money confirmations arrive as forwarded messages and screenshots, and the conversation is where the transaction is reconciled. That makes the message history a financial record in practice - which is an argument for it belonging to the business rather than to somebody's personal phone, and for exports that actually work.

What this adds up to

Support tooling designed for email-shaped conversations - subject lines, tickets, statuses, canned responses in one language - fits this badly. What works is closer to a shared chat window with memory: fast, media-first, multilingual by not caring, and honest about who answered.