How to handle client feedback on social media posts
Client feedback on social posts is rarely wrong, but it is often unclear. “Can it be more exciting?”, “my partner doesn’t like the photo”, “actually, can we change the whole caption?” two hours before the post goes out — each of these is a reasonable thing for a client to feel and a hard thing for a team to act on.
This guide is about the conversation, not the process: how to ask for feedback so it arrives usable, how to decode what arrives, how to handle more than one voice, and when and how to push back. The approval workflow guide covers the process around it — deadlines, rounds and decisions.
Ask for feedback so it arrives usable
The way you ask shapes what you get back. “Any thoughts?” invites opinions about everything; a specific question invites a specific answer.
- Ask for a decision per post — approve, request changes or reject — not general impressions
- Ask them to say what to change and, ideally, why
- Remind them of the goal and the brief, so feedback is measured against something
- Ask them to leave feedback on the post itself, or on the specific slide, rather than in a separate email
Feedback attached to the post it is about is half-decoded already: you know which post, which image and which version it refers to.
Decode vague feedback
Vague feedback is usually a real reaction the client doesn’t have the vocabulary to name. Your job is to translate it into something you can change — and to check your translation before you make the change.
| What they say | What it often means | What to ask |
|---|---|---|
| “Make it pop” | It doesn’t stand out in the feed | “Is it the image, the colours or the first line that feels flat?” |
| “It doesn’t feel like us” | The tone or visual style is off-brand | “Is there a past post that feels right? Which part of this is furthest from it?” |
| “Not sure about this one” | Something bothers them but they can’t name it | “If you could change one thing about it, what would it be?” |
| “Can it be shorter?” | The point is buried | “Is the first line clear on its own?” |
| “Something more exciting” | The post explains but doesn’t persuade | “What would make you stop scrolling for this?” |
One clarifying question, asked quickly, is worth more than a guessed revision. A wrong guess costs a round; a question costs a minute.
When feedback conflicts
Two people at the client want opposite things: the marketing lead wants the bold version, the founder wants the safe one. Don’t pick a side, and don’t try to merge both into a post that satisfies neither.
- 01Name the conflict back to the approver, neutrally: “We have two directions here”
- 02Ask the named approver to decide — that is what the approver role is for
- 03If there is no named approver, this is the moment to agree one
- 04Record the decision on the post, so it isn’t reopened next week
Hi [Approver], We’ve had two different steers on the launch post: [Person A] would like [direction A], and [Person B] would prefer [direction B]. Both are fair, but they pull in opposite directions, so we’d rather not blend them. As the approver, could you let us know which way to go? We’ll update the post as soon as we hear. Thanks, [Your name]
Late changes
A change request an hour before publishing is a small emergency. How you handle it depends on what kind of change it is.
| Kind of change | What to do |
|---|---|
| A factual error — wrong date, price, name | Fix it, always. A wrong fact published is worse than a late post |
| A small wording change | Make it if there is time to send it back for approval; otherwise move the post |
| A new direction for the post | Move the post to a later slot and treat it as a new brief |
| A change to an approved post | Unlock it, change it, and get a fresh approval — never edit it quietly |
The rule underneath all four: whatever goes live should be what someone approved. If a change can’t be reviewed in time, the post moves rather than going out unreviewed.
How to push back
Sometimes the client is asking for something that will make the post worse, break a network’s rules, or contradict what they asked for last month. Pushing back is part of the job — done well, it is why clients trust you.
- Push back on outcomes, not taste: “this will be cut off after the first line on Instagram”, not “we don’t like it”
- Offer an alternative, not just a no
- Use evidence where you have it: last month’s top posts, a network’s limits
- Pick your moments. Concede on taste, hold on facts, brand rules and platform limits
- If they still want it, do it their way and note the decision on the post
Hi [Name], Happy to make that change — one thing worth knowing first: moving the offer to the end of the caption means it’ll sit behind “more” on Instagram, where most people won’t see it. Could we keep the offer in the first line and move the story after it instead? I’ve put that version on the post so you can compare. If you’d still prefer the original order, just say and we’ll go with it. [Your name]
Stop the endless revision loop
When a post comes back for a third or fourth round, the problem is rarely the post. It is usually one of these:
- The brief was never agreed, so each round is really a new brief — go back and write one
- Too many people are giving feedback — narrow it to the named approver
- The client doesn’t like the idea, not the execution — ask directly, and replace the post
- Feedback is arriving in pieces — ask for all changes in one pass
Agreeing a number of included revision rounds at the start of the relationship makes this conversation much easier: the fourth round isn’t a favour you are refusing, it is outside what was agreed.
Turn feedback into rules
Every piece of feedback tells you something about the client’s taste. Write it down. After two or three months, “no puns”, “never show the old logo”, “the founder doesn’t appear in videos” add up to a brand rules page that stops the same change being requested again.
Keep those notes where the team will see them while writing, but where the client won’t — an internal note on the workspace or on the posts they affect.