Publishing & calendar
How this is scored
Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails at 3am.
0 — One post to several networks at once with no per-network variation and no calendar.
3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.
5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.
8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.
10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.
The Skeptic
Scheduling with per-profile limits and auto-publish across all eight networks is evidenced, and the Access Groups copy admits a calendar exists as an object — but the evidence never shows it as a working surface, shows no per-network variants, no drafts, and nothing at all about what happens when a post fails. The coexistence of 'Auto Publish' with 'notification publishing' for Instagram and TikTok is the tell: a manual phone-notification workaround is exactly what you keep when the API can't be trusted, and the vendor says nothing about which is which. 2