Can a client approve a post without a CampaignFlow account?
Yes. You send the reviewer a link, and they approve the post or ask for changes from it without signing in.
The quick share link from a post lasts 72 hours and records one decision. When more than one person has to sign off, an approval workflow runs up to six stages. Each stage is named teammates, a role, or outside reviewers by link, and has a deadline with reminders; links sent through a workflow last 14 days. If the client asks for changes, you revise the post and send it again for the new version. The decision comes back to you as an alert, and posts waiting on a decision sit in the Approvals inbox.
By default approval is sign-off, not a gate. It records what the client said; it does not stop a scheduled post from publishing. Turn on 'require approval before publishing' for the brand and an unapproved post can't be scheduled, and a scheduled one is held back if its approval is withdrawn, for example by an edit after approval. The client approval guide covers how to run it.
- No sign-in for the reviewer
- A quick link lasts 72 hours; workflow links last 14 days
- Workflows of up to six stages, each with a deadline and reminders
- Optional: require approval before publishing
How do I manage several client brands?
Every brand sits under one sign-in, and you switch between them. Each brand has its own brief, its own rules, its own campaigns and its own connected accounts.
A brand's brief is a short one — six required questions, the rest optional: who the brand is, what it offers, who it talks to and how it sounds, with what it must never claim as an optional step. That brief is what drafting and checking run against, so one client's voice does not bleed into another's.
A client's product catalogue can be brought in as a CSV, XLSX or PDF file, and files come in by upload or from Google Drive. Each brand's campaign timeline shows the whole campaign at a glance: what is published, what is drafted and what is still empty. That is the view to open before a client call.
Are the limits per brand or per user?
Per brand. A second brand starts with its own plan limit, and teammates on a brand share that brand's limit.
AI features carry a plan allowance, as does some storage, such as Creative Vault; the rest has none. Planning, Campaign Guard's rule checks, scheduling, publishing, analytics and syncing have no limit on any plan. The Custom plan is for several brands at once, or one brand at a faster pace, and is arranged by email. The current limits are on the pricing page.
How does it stop a client campaign repeating itself?
Every draft is checked against what the campaign has already said, and every post is given a format and a call to action before anyone writes.
Campaign Guard flags reused hashtags, headline figures already used, platform limits, claims to check and phrases on the brand's Don't say list. Most of its warnings point at what is worth a second look, and you decide; only errors, such as a blocked word or an unchecked claim, stop a post being marked ready. The rotation sets format, call to action and audience across the campaign and flags every repeat, and the next-post suggestion names the topic that is furthest behind its share. How the rotation works explains the rules.
- Reused hashtags and repeated headline figures, tracked across the campaign
- Platform limits checked on every draft
- The brand's own Don't say list of claims that are almost true, each flagged with what to say instead
- Feedback in plain English: only what you name changes, and earlier versions are one click away
Will I know when a client's post goes out, or fails?
Yes. Alerts go to Slack, Discord, Telegram, email, a webhook or the in-app feed.
You hear when a post publishes or fails, when a connected account's access is about to expire, and when a client answers an approval link. A post is re-checked 15 minutes before it goes out and held back at sending time if it is not ready, and a platform hiccup is retried.
Which platforms can I publish client posts to?
Instagram, Facebook Pages, YouTube and Threads, each through the platform's official API. LinkedIn and Pinterest are pending platform review.
Accounts connect on each platform's own sign-in screen, so CampaignFlow never sees a client's password. Tokens are encrypted at rest, and client content is not used to train models. The full list is on the features page.
Questions