The slow part of agency work is rarely the work. It's waiting on the client. Screenshots pasted into Slack, a spreadsheet of captions, four email threads with the same subject line, and a yes you have to go dig for. A client review batch puts the posts behind one link. They click it, see every post the way it will actually publish, and approve or ask for a change. No account, no password, no seat on your plan.
3 days free. Cancel anytime.
When a client wants a different photo, they say so on the post itself, and your reply sits underneath it. The whole back-and-forth stays attached to the thing being discussed, so when you come back a week later there is no hunting through email to work out which crop she meant. They can react with an emoji when a comment would be overkill, and attach a screenshot when words aren't enough.
Approve and Request changes sit right below the thread. Ask for changes and the post flips state, your team fixes it, and the new version goes back up on the same link.
Clients read the email on a phone, in a queue somewhere, and they will decide right then or not at all. So the link works there: the batch is a list they can thumb through, every post shows what it's waiting on, and Approve all sits pinned to the bottom of the screen. Four taps and the campaign is signed off from a bus stop.
Send the posts straight to the client, or make the team clear them first so the client only ever sees work you already stand behind. From the same box you choose whether one yes is enough or everyone has to agree, put the approvers in a fixed order when the sequence matters, and gather the posts into a batch the client gets as a single link.
Every batch you have out sits in one list: how many posts are approved, how many need changes, how many the client hasn't touched, when they last opened the link, and the date it expires. When someone swears they never got the email, resend it from that row. When the campaign changes underneath them, cancel the batch and the link stops working.
Enough to give you a real answer, and nothing that lets them wander into the rest of your workspace.
The client gets a link. You keep the rules about what that link can do, who it belongs to, and how long it lives.
Client review is one stage of the publishing workflow. The post you draft in the Composer is the post the client sees, and the batch you send is what shows up on the calendar.
Set the client's expectations before the first batch goes out, and close the loop after the campaign runs: free, no account needed.
A set of draft posts you send to a client through one shareable link. They open the link, scroll through every post laid out the way it'll publish, and either approve, request changes, or leave a comment. Your team stays in Maeve. The client doesn't have an account.
No. The link uses a per-batch token. Clients land on the review page, identify themselves with the email address you invited, and they're in. No password, no signup, no extra seat on your plan. The most-upvoted complaint we kept hearing about competitor tools was "my client can't get into yet another platform." The review link exists to skip that.
Team approval is for staff who already have a Maeve login signing off internally. Client review is for the people outside your team. Most agencies run both back to back: the team approves, then the batch goes out to the client. That's the internal_client mode.
Per post: approve, request changes, leave a comment up to 2,000 characters, attach a screenshot or markup, or react with one of five emojis. They see the real native preview for each platform plus the scheduled time, and they can scroll the post list without opening each one. Internal-only notes stay hidden.
Yes. Approve all pending clears every post still waiting on that reviewer in one action, after a confirmation step that lists exactly what is about to be approved. When they'd rather go post by post, each one has its own approve and request-changes buttons.
Yes, and that's how most clients open it. On a phone the batch becomes a scrollable list of posts, each one tapping through to the full preview and the comment thread, with the approve-all bar pinned to the bottom of the screen.
Either. Each batch has a policy: any (one approval is enough) or all (every invited reviewer must approve before the post is signed off). Useful if a single brand contact is fine for one batch, but a multi-stakeholder launch needs all of them on the record.
The post flips to changes_requested and the client's comment attaches to it. Edit the post, resubmit, and the link surfaces the new version. Earlier decisions are kept with a version number, not overwritten, so the decision a client made always points at the exact version they saw.
Admins can. Override flips the post to admin_overridden and you have to type a written reason that gets recorded against the batch. Editors and viewers can't. It's an admin-only escape hatch for the days a client goes silent and the campaign is going out anyway.
Per-batch expiresAt timestamp. After that date the link stops working. Useful for time-sensitive approvals you don't want sitting in someone's inbox three weeks later for someone else to find. Default is no expiry.
Resend link from the batch list mails the reviewer a fresh copy. If the batch shouldn't be live at all any more, cancel it from the same row and the link stops working immediately.
Approval History under your workspace. Every resolved batch shows who reviewed, who approved, who requested changes, when each decision happened, and the comment thread. Internal team approvals are in the same view, so the chain of accountability is one place per workspace.
Standard and Premium. Internal team approvals (no external client) come on Basic and above; the external-client batch flow is the Standard-tier feature. Pricing page has the comparison.
Reviewers see real native-style previews for Instagram, Facebook, Threads, LinkedIn, X, TikTok, YouTube, and Pinterest, including Reels, Stories, carousels, threads, and pinned-comment fields. The preview is what publishes.
Not yet. The review page is unbranded and clean, with no Maeve header and no "powered by" stripe, but a custom logo and brand colors on the link itself isn't shipped. It's a known request and on the roadmap. Honest scope.