A social media approval workflow for agencies: stop approving posts in WhatsApp

Most agencies have an approval workflow. It just happens to live in WhatsApp: a screenshot of the post, a voice note from the client, "ok can", then a second screenshot because the price changed, then a thumbs-up on the wrong version. Two weeks later, nobody can say who approved the post that went out with last month's promotion.

A proper approval workflow does not need to be complicated. It needs four things: clear roles, a step that stops unapproved posts from publishing, a way for clients to review without logging in, and a record of decisions. This guide sets up all four.

Why approvals in chat apps go wrong

Chat apps are great for conversation and poor for decisions:

• Versions get mixed up. The screenshot that was approved is not always the file that was scheduled.
• Feedback gets buried under fifty other messages in the client group.
• Nothing stops the post. If the approval never comes, or comes late, the post often goes out anyway because it was already scheduled.
• There is no record. When a client asks "who approved this?", the answer is a scroll through months of chat.

The fix is to move the decision next to the post itself.

Step 1: give everyone the right role

Start with roles, because the approval step depends on them. A typical setup:

The rule of thumb: the people who write posts should not be the only people who can publish them.

Step 2: make approval required, not optional

The most important setting is the one that makes approval required. With it on:

1. An editor writes the post and schedules it.
2. Instead of going on the calendar as scheduled, it waits as pending approval.
3. An owner or admin opens it and either approves it or requests changes with a comment.
4. Only an approved post publishes at its time. A post still waiting cannot go out.

This turns "I think the client said ok" into a step the system enforces. If an approval is missing, the post waits instead of publishing by accident.

Make it fast

Approval steps fail when they slow everyone down. Three habits help:

• Approve in batches. Set a daily slot, for example 11 am, to clear everything waiting.
• Comment precisely. "Change RM39 to RM35 in the first line" gets fixed in minutes; "not quite right" starts a meeting.
• Plan ahead. Approval works best when posts are ready days before they publish, not an hour before.

Step 3: let clients review without an account

Many clients do not want another login. They want to see the post as it will look and say yes or no.

A preview link solves that. You send the client a private link to one post. They see the post as it will appear, can leave comments, and your team is notified. Nobody needs a password, and there is only one version: the one in the calendar.

For clients who want to see the whole month, invite them as viewers. They can browse the calendar and analytics without changing anything.

A good routine for client sign-off:

1. Your team drafts the week's posts.
2. An internal admin approves them for quality.
3. Preview links go to the client for anything sensitive: prices, promotions, festive greetings, anything legal or medical.
4. Client comments come back on the post, and the editor updates it.

Step 4: keep a record of who approved what

A record protects your agency and your client. When a question comes up, you should be able to see who submitted the post, who approved it or requested changes, and when.

Keep that record in the tool rather than in your memory. It also helps when you onboard a new team member: they can see how decisions were made on an account.

Common mistakes

• Everyone is an admin. If juniors can approve their own posts, the step exists only on paper.
• Approving the image, not the post. Review the caption, the link, the tags and the time, not just the design.
• Skipping approval for "small" posts. Typos in a festive greeting are the ones clients remember.
• No backup approver. When the account manager is on leave, nothing publishes. Name a second admin per client.

Setting this up in Watchpost

Watchpost has the four roles above, with approval that a workspace can make required, so editors' posts wait for an owner or admin. Approvers can approve or request changes with a comment, and they are notified in the app and by email. Every post has a private preview link that a client can open and comment on without an account. The workspace activity log records who submitted, approved or requested changes on each post.

For agencies, company folders keep each client's channels together, and Sets save each client's usual channels, times and tags. All of this is on the one plan: RM69 a month for 5 team members and 10 connected accounts.

Read more on the agencies page, or in our checklist on managing many client brands safely.

A one-page workflow to share with your team

1. Editors write and schedule posts by Wednesday for the following week.
2. Admins review every day at 11 am: approve, or request changes with a precise comment.
3. Preview links go to clients for promotions, prices and festive posts.
4. Nothing publishes without approval.
5. Once a month, review roles and remove anyone who has left.

Five rules, one place for decisions, and no more searching through WhatsApp to find out who said "ok can".