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 is genuinely documented — 500 posts by CSV or in one API request, recycle mode for evergreen content, RSS automation, optimal-time scheduling and a drag-and-drop calendar — and a failed Facebook post is explained by cause, with a manual Publish button or reschedule as the recovery. But we found no public information on link shortening with UTM tags, stories or reels, or failure notifications as such, and recurring posts are stated as not supported in bulk, so the evidence stops short of dependable-at-volume. 4 5 13 1