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
The publishing side is genuinely deep: a drag-and-drop calendar across every connected profile, bulk upload of a full campaign or an RSS-fed queue at up to a thousand posts per minute, per-network caption versions with live character counts against each network's limit, and best-time suggestions from audience data. What keeps this short of the top is that I found no public information on failure notifications with a retry, or on link shortening with UTM tags — the safety net I want before queuing work for twelve brands. 1 3