Schedule every post, in one place.
BAT publishes natively to 8 platforms through real OAuth and a dedicated publisher per network, not a generic relay. A scheduled-publish worker fires due posts on time and refuses to send the same post twice. Each platform still needs its own app credentials connected.
A scheduler that actually ships posts.
Most of what BAT does for scheduling comes from real product code: per-platform OAuth, a worker that claims and fires due posts, and one calendar that spans every connected network.
Real publishers, not a relay
Dedicated OAuth and publisher code for all 8 platforms, not a generic relay.
A worker that can't double-send
A scheduled-publish worker that atomically claims due posts and fires them, preventing duplicate sends from retries or races.
One calendar, every platform
One calendar across every connected platform, with AI-suggested send times.
One idea, every native format
Schedule a single idea out to multiple platforms, each in its native format.
How the scheduled-publish worker works.
Scheduling is only as good as the thing that fires the post when the clock hits. BAT runs a background worker so a queued post goes out whether or not anyone is looking at the app.
- Queue a post for a time. An approved post lands in the schedule with a target time per platform, in its native format (a LinkedIn document, an Instagram reel, an X thread, a TikTok video).
- The worker claims it atomically. When a post is due, the worker atomically claims it before publishing. That claim is what prevents a retry or a race from sending the same post twice.
- It fires through the native publisher. Each platform has its own OAuth connection and publisher code, so the post goes out through the real API for that network, not a lowest-common-denominator bridge.
- You see the result on the calendar. Status flows back to the one calendar that spans every connected platform, so scheduled, published, and failed posts all live in a single view.
Schedule across eight networks.
LinkedIn, Instagram, Facebook, X, TikTok, YouTube, Threads, and Pinterest, each with its own connection and native post types. Schedule one idea out to all of them, or tailor per network.
AI send times from your own history.
BAT does not guess at generic best times. It reads your own engagement-by-hour history and suggests when to post, falling back to a platform-canonical default only when there is not enough of your own data yet.
Learned from your engagement
Suggested posting times derived from your own historical engagement-by-hour, with a platform-canonical fallback.
Per-platform, not one-size-fits-all
Send-time suggestions are computed per network, because what works on LinkedIn at 8am rarely matches when a TikTok lands. Each platform gets its own read.
A sensible default to start
On a brand-new workspace with little history, BAT uses a platform-canonical fallback time so the calendar is useful from day one, then sharpens as your data accrues.
Two tools, two premises.
BAT: strategy, draft, and schedule in one
BAT drafts the post from your brand brain, gates it through review, then schedules and publishes it natively. The scheduler is the last step of a workflow that also decides what to post and writes it in your voice.
Best for
Teams that want the post written on-strategy and the calendar filled, not just a queue to paste finished copy into.
A standalone queue you fill yourself
A pure scheduling utility takes copy you have already written and lines it up. It is fast and cheap at that one job, but it has no opinion about what to post, no brand memory, and no review gate before things ship.
Best for
Creators who already write everything themselves and only need a dependable queue across channels.
Review before it ships, not after.
Scheduling without review is how the wrong draft goes live. BAT puts a real approval gate in front of the scheduler, so only signed-off posts ever reach the worker.
- Post drafts move DRAFT → PENDING_REVIEW → APPROVED/REJECTED, with rejection notes and resubmit; approved posts go to the scheduler.
- Five brand roles (Owner, Admin, Manager, Creator, Member) with a fine-grained capability matrix.
- Role hierarchy with privilege-escalation guards: you can only grant roles below your own.
Where this is honest about the limits.
Each platform needs its own app credentials configured; Pinterest in particular is pending app approval.
Instagram publishing requires a Business account linked to a Facebook Page (a platform rule, not a BAT limit).
There is also no post-publish recall. Approval and cancellation happen before a post goes live, never after. If you need to stop something, you stop it in review, not by pulling it back once it is on the network.
Where to go next.
The scheduler is one face of the same calendar and brain. These pages go deeper on the multi-platform publishing surface and the planning view.
Schedule to all platforms
See the full cross-platform publishing surface: which native post types each of the 8 networks supports, and how one idea fans out. Read the schedule-all-platforms breakdown at /schedule-all-platforms.
Plan on the content calendar
The same posts, viewed as a calendar you plan against weeks ahead. See how drafting, approval, and scheduling sit on one timeline at /social-media-content-calendar.
See the whole product
Scheduling is one capability inside a chat-first AI social manager with a brand brain, analytics, and competitor benchmarking. Start at /features or compare plans at /pricing.
Frequently asked questions.
How many platforms can BAT schedule and publish to?
Eight, natively: LinkedIn, Instagram, Facebook, X, TikTok, YouTube, Threads, and Pinterest. Each one has its own OAuth connection and publisher, so posts go out through that network's real API rather than a generic relay. You connect 8 platforms once and schedule across all of them from one calendar.
Will the same post ever get published twice?
No. The scheduled-publish worker atomically claims a due post before sending it, so a retry or a race cannot fire the same post a second time. Double-publish prevention is built into how the worker claims work, not a setting you have to remember to turn on.
How does BAT decide the best time to post?
It suggests send times derived from your own historical engagement-by-hour, computed per platform. On a new workspace with little history, it falls back to a platform-canonical default so the calendar is useful immediately, then sharpens as your own data builds up. These are suggestions you can always override.
Do I need my own app credentials for each platform?
Yes, that is the honest limit. Each platform needs its own app credentials configured to publish, and Pinterest in particular is pending app approval. Instagram also requires a Business account linked to a Facebook Page, which is a platform rule rather than a BAT limitation.
Can I cancel a post after it goes live?
No. BAT is approval-gated before publish, not after. A post moves through review (DRAFT to PENDING_REVIEW to APPROVED) and only an approved post reaches the scheduler, so you catch problems before anything ships. There is no post-publish recall once a post is on the network.
Is there a free plan for scheduling?
There is no free tier. BAT starts with a 14-day free trial and 200 credits with no card required, then Brands Starter at $100/mo for one brand workspace. Pricing is flat per workspace, not per seat, so adding teammates to the schedule does not raise the price.
Fill the calendar, publish on time.
Connect your platforms, schedule across all eight from one calendar, and let the worker fire every approved post on time, exactly once. Start free, no card required.