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 Agency Lead
Scheduling is real and broad: a publish endpoint covering Facebook, LinkedIn, Pinterest, YouTube, TikTok and more, drafts and approval states on every message, a calendar listing what is posted or scheduled, and Instagram Reels — enough machinery to run twelve brands' calendars programmatically. What I cannot see is the working surface: we found no public information on previews, bulk operations, queue or best-time scheduling, or retry after a failure; an error status is named but recovery is never described. 2 3 4