How does a team share one campaign plan?
Teammates work on the same brand, so everyone sees the same run: what shipped, what is drafted and what is still empty.
Every slot has a format and an ask before anyone writes, so the plan is decided once rather than argued post by post. Teammates on a brand share that brand's allowance; the planner, the linter, the timeline and analytics are never metered. 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 run in their head: which hashtags have been spent, whether formats really alternated, or whether a figure has already led a post. CampaignFlow keeps that record across the run 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 delivered 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 slot.
- Slack
- Discord
- Telegram
- Webhook
- In-app
How do we stop a draft making a claim we cannot back?
Write your don't-say list into the brief, and every draft is checked against it. The claims that are almost true are caught before a reader catches them.
The same checks track every hashtag and headline figure the run has used, and flag platform limits. The warnings are advisory, 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. A post that is not ready is held back 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 slot 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 run.
- Schedule the run. Pick the weekdays and a time, in your brand's timezone. Preview where every post lands, then confirm.
- Re-checked 15 minutes before. A post with an error is held back and you are told.
- Published, or retried. A platform hiccup is retried; delivered 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. Each link lasts 72 hours and records one decision.
Approval is sign-off, not a gate: it records the decision and does not block a scheduled post. Schedule once the answer is in.
Which platforms does it publish to?
Instagram, Facebook Pages, YouTube and Threads, through each platform's official API. LinkedIn is 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