Okay, so. Tuesday. A client opens their approval link on their phone, scrolls to post seven and types: “Can we change the colour, the blue looks off.”

Here is exactly what happens next in my agency. Nobody phones me. Nobody phones a designer. This is the chain.

1. The link knows what it is looking at

Every client gets a private link. A long random token, no login. Each post on it shows the design and the full caption, with two choices: Approve, or Request changes.

Approve is not a thumbs up. It claims the next free posting slot, 09:00, 13:00 or 19:00, and writes a row in the calendar. That matters later.

Request changes opens a box. They type in their own words. “Change the colour.” That is it. They do not need to know what a brand palette is.

2. The request lands in a table, not an inbox

The moment they submit, the note lands in a change-requests table in the Hub, my own software, which runs on Cloudflare. Every request has a status: open, in progress, uploaded, QA passed, redo, escalated. And every request is kept. Nothing is overwritten. If a client changes their mind three times, I can see all three.

Nobody replies “noted”. That was a rule I had to make. A “noted” message is a human pretending to be a system. The system should just do the thing.

3. A watcher picks it up within two minutes

On my server a change-request watcher runs every two minutes. It sees the new open row and asks one question: does this go to an agent or a human?

Each post on the link has a small toggle: AGENT or HUMAN. By default it is AGENT. For a client with a human designer on the account I flip it to HUMAN, and the request routes to that person instead. The client never sees the difference. They typed one sentence either way.

4. The agent reads the brief, not just the note

“Change the colour” on its own is useless. So the agent reads three things: the client’s note, the original creative brief on that post, and the client’s brand file. I named him Ibrahim. He runs content and graphics. There are eleven of them, one department each, and the names are not decoration; a name is a job description the whole system can read.

Blue looks off? The brand file says which teal is theirs. He re-renders with the right one, uploads the new design to the same card, and the status moves to uploaded.

5. QA before the client sees it

Then a check. Real logo, nothing cut off, no text over a face, right size. Pass: QA passed, and the updated post goes back to the same link, same card. Fail: redo, and it goes round again. Keeps failing: escalated, which means me, in my WhatsApp. That is the only point I enter the chain, and only when it has gone wrong.

6. The nudge

If the client goes quiet, the nudger reminds them. It arms itself the moment the link is sent. First nudge after five hours, then every three to five hours, only between 08:00 and 18:59. Nobody should get a bot at 23:00.

7. Approve, and the slot is claimed

The client opens the link, sees the new colour, taps Approve. That tap claims the next free slot and writes the calendar row. At that time the publisher on the server posts it to Facebook, Instagram, stories, X and LinkedIn, and fifteen minutes later YouTube, TikTok, Threads and Google Business.

A guard refuses to overwrite a card once it has posted. So a late “actually, change it back” becomes a new revision, not a silent edit of something already live.

What this replaced

A voice note to me. Me forwarding it to a designer. The designer asking “which post?” A screenshot. A day gone. Me chasing. The client chasing me. One sentence from a client used to cost four people a day. Now it costs one agent two minutes, and me nothing, unless it escalates.

The honest part

The agent still gets it wrong sometimes. That is why there is a QA step and an escalate status, and why I am still the human behind the agent. You do not remove the human. You move the human to the end of the chain, where judgment is needed, instead of the middle, where forwarding is needed.

Try it on your own chain

Take one request your customers make every week. Write the chain as it is today, every hand it passes through. Count the hands. That count is your number. Every hand that only forwards is a hand you can give back to the person.

Send us the process that is wasting your team’s time. WhatsApp: https://wa.me/27797327231

Want to build the prompt for it yourself first? Two minutes: prompts.socialzip.co.za