How does a team share one campaign plan?
Teammates work on the same brand, so everyone sees the same campaign: what is published, what is drafted and what is still empty.
Every post has a format and a call to action before anyone writes, so the plan is decided once rather than argued post by post. Teammates on a brand share that brand's plan limit: AI features carry a plan allowance, while planning, Campaign Guard's rule checks, the timeline and analytics have no limit. See the features page for the whole flow.
The shared record is the point. When several people write for one brand, nobody holds the whole campaign in their head: which hashtags have been reused, whether formats really alternated, or whether a figure has already led a post. CampaignFlow keeps that record across the campaign and checks each draft against it, whoever wrote it.
Feedback works the same way for everyone. Say what is wrong in plain English and only that part changes, and every earlier version stays one click away, so a colleague's edit never quietly overwrites yours.
Where do the alerts go?
To Slack, Discord, Telegram, email, a webhook or the in-app feed. Pick the channel your team already watches.
Alerts cover a post published or failed, a connected account's access about to expire, and an approval answered. A failure reaches the people who can fix it without anyone watching a dashboard.
An expiring connection is the alert teams most often wish they had had. Platforms end access after a while, and the first sign is usually a post that did not go out. Hearing about it ahead of time means someone reconnects the account on the platform's own sign-in screen before the next post.
- Slack
- Discord
- Telegram
- Webhook
- In-app
How do we stop a draft making a claim we cannot back?
Add the claims to your Don't say list in Brand Studio → Brand Brain, and Campaign Guard checks every draft against it. Each entry has a reason and a 'Say instead', so a match is flagged with the wording to use; it does not stop the post. The claims that are almost true are caught before a reader catches them.
The same checks track every hashtag and headline figure the campaign has used, and flag platform limits. The warnings are not a compliance guarantee: they point at what is worth a second look, and a person still reads every draft. The claims checklist helps you decide what goes on the list.
What happens just before a post publishes?
Each post is re-checked 15 minutes before it goes out, and checked again just before it is sent. A post that is not ready is held back at sending time rather than published.
If a platform hiccups at the moment of publishing, the post is retried. CampaignFlow publishes only what you scheduled, when you scheduled it, to the accounts you connected, and a failure comes back to you as an alert.
Holding a post back is the safer failure. A post that goes out late can be rescheduled; a post that went out broken has already been seen. The check runs close enough to the publishing time to catch a problem that appeared after you scheduled the campaign.
- Schedule the campaign. Pick the weekdays and a time, in your own time zone. Preview where every post lands, then confirm.
- Re-checked 15 minutes before. A post that is not ready at sending time is held back and you are told.
- Published, or retried. A platform hiccup is retried; published and failed posts both raise an alert.
Can someone outside the team sign off a post?
Yes. Send a link, and the reviewer approves or asks for changes without an account. The quick link from a post lasts 72 hours and records one decision. For sign-off in stages, an approval workflow runs up to six, each with named teammates, a role or outside reviewers by link, and a deadline with reminders; its links last 14 days.
Approval is sign-off by default; turn on 'require approval before publishing' and an unapproved post can't go out. With it on, an unapproved post can't be scheduled, and a scheduled one is held back if its approval is withdrawn.
Which platforms does it publish to?
Instagram, Facebook Pages, YouTube and Threads, through each platform's official API. LinkedIn and Pinterest are pending platform review.
Accounts connect on the platform's own sign-in screen, tokens are encrypted at rest, and disconnecting revokes and deletes the credential.
Questions