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.
0 — No publishing or scheduling; the product is a listening, analytics or inbox tool only.
3 — Posts scheduled to several networks from one composer, with a list or calendar of what is planned.
5 — A content calendar with scheduling across the main networks, per-network text and media variants, drafts, and post previews.
8 — Bulk upload or CSV import, queue or evergreen scheduling, best-time suggestions, link shortening with UTM tags, stories, reels or shorts where the API allows, and failure notifications with a retry.
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
Bulk scheduling to 350 posts at once, a calendar and list view over organic, paid, published and scheduled content, best-time heat maps and a suspend-all switch are all documented, alongside scheduling for Facebook, Instagram and Bluesky. But I count what happens when a post fails and find only a vendor-side fix note for failing Facebook scheduled posts — we found no public information on failure notifications with retry, link shortening with UTM tags, or stories, reels and shorts publishing. Dependable at volume is asserted nowhere, so this sits below the top. 4 13 13 4 5