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 Community Manager
Scheduling spans nine networks from one Smart Compose Box with per-channel captions, hashtags and thumbnails, plus a visual calendar, CSV bulk import, evergreen Smart Queues, best-time suggestions from performance data, and Stories, Reels and Shorts with the per-network quirks documented in print. What I cannot find is the part I care about most: we found no public information on failure notifications or a retry when a post does not go out, nor on link shortening alongside the documented UTM parameters. 4 7 11 12 4 7 13