Client approvals on WhatsApp without losing track

Gulf clients approve work on WhatsApp because that is where they actually answer. The fix is not to fight it, but to make sure the yes ends up somewhere you can find it.

4 September 20264 min readBy the Wiro team, Dubai
Hands holding a smartphone in warm, low light

Every agency in the region has tried, at some point, to move a client off WhatsApp. The client agrees in the meeting, logs into the new tool once, and a week later sends a voice note from the car saying the second post is fine but can the colour be warmer. The agency replies on WhatsApp, because that is where the client is.

This is not a failure of discipline. It is how business communication works in the Gulf for a lot of clients, and the agencies that do well accept it and build around it.

Why clients approve on WhatsApp

For many senior people in the region, WhatsApp is the channel they actually read. Email is where formal documents go and where things wait. WhatsApp is where decisions happen, often between meetings, often on a phone, often from someone who would not open a laptop to look at a caption.

It also reflects how relationships work here. Clients expect to reach the people they work with directly, and a quick reply from the account manager is part of the service they believe they are buying. Asking them to log into a system to say yes can feel like the agency putting a process between itself and the client.

So the question is not how to stop WhatsApp approvals. It is how to stop them disappearing.

The problem is not the channel, it is the record

An approval in a WhatsApp thread has three weaknesses. It sits on one person's phone. It is buried under everything else said in that thread. And it often refers to something ambiguous, such as the second one or the new version, which made sense at the time and means nothing six weeks later.

Voice notes make it worse. They are quick for the client and impossible to search, and a verbal yes with conditions attached is easy to remember differently from the person who said it.

An approval nobody can find is not an approval. It is a memory, and memories get disputed.

Choose one source of truth, and say so

The fix is a simple rule, agreed internally and ideally mentioned to the client: WhatsApp is where conversations happen, but the approval lives in one other place. That might be the project record, the content calendar or the client portal. It does not matter which, as long as it is one place and everyone on the team knows it.

Then treat any approval that arrives on WhatsApp as unfinished until it has been copied there. The same day, not at the end of the week. Record what was approved, the exact version, who approved it and when, and any conditions the client attached.

  • Write back a one line summary after every voice note: noted, post three approved with the warmer colour, going live Tuesday. The client sees it, and if the summary is wrong they will say so.
  • Refer to work by a name that will still mean something later, not by position in the thread.
  • Screenshot text approvals and attach them to the record, so the evidence survives a lost phone or a person leaving.
  • Never let the only copy of an approval live on a personal number.

Send links, not files

Much of the confusion comes from sending the work itself into the chat. A video forwarded on WhatsApp is compressed, a PDF is hard to read on a phone, and the moment a revision goes out there are two files with similar names in the same thread. The client approves one of them, and nobody is quite sure which.

Sending a link to the work instead keeps the file in one place. The client taps it, sees the current version as it will appear, and approves or asks for changes on the page rather than in the chat. The approval is recorded against the work automatically, with their name and the time, so there is nothing to copy across afterwards.

The link has to open without an account. A login screen on a phone, between meetings, is where most approval tools lose the client. If the link works in one tap, WhatsApp becomes the delivery route for the approval rather than the place the approval is stored.

Groups, numbers and who is in the thread

A client WhatsApp group feels efficient and often becomes the opposite. Five people from the client side, four from the agency, and nobody clear on who has the final word. Contradictory feedback arrives from two directors within minutes of each other.

Name one approver at the start of the relationship, and make sure that person's word is the one recorded. Keep agency participation in groups to the people who genuinely need to be there, and use a shared business number rather than personal ones where you can, so the relationship does not walk out of the door with an employee.

What good looks like

In an agency that handles this well, the client still messages on WhatsApp whenever they like, and the account manager still replies quickly. The difference is that work is shared as a link, approvals are confirmed in writing, and anyone on the team can open the project and see what was approved, by whom and when, without asking to borrow a phone.

In Wiro, that link is a review link from the project or the client's page: the client opens it without logging in, approves or asks for changes, and their answer is recorded on the work. Send it on WhatsApp, by email or anywhere else. The channel stops mattering once the record lives somewhere else.