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 Agency Lead
Automated queue-based scheduling is real — an Autofeed with a Schedule Queue, immediate sharing, and per-network automation on Facebook and Instagram covering image-versus-link proportions and daily story counts — and the algorithm picks timing from the account's own performance data at serious volume. But I found no public information on a calendar as a working surface, drafts, per-network text variants, bulk import or link handling, and overnight failure handling is evidenced only as automatic reconnection of disconnected Facebook pages, not post-level failure notices with a retry. 1 2 8 9