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
The calendar is a real working surface — every scheduled post for every connected profile in one view, drag and drop between slots and days, live character counts against each network's real limit, and each network given its own version of the caption. Bulk upload is claimed at up to a thousand posts per minute, RSS feeds queue automatically, and the engine suggests peak engagement hours trained on audience data. We found no public information on what happens when a post fails — nothing on notifications or a retry — and nothing on link shortening with UTM tags or stories, which is why I stopped short of the top. 1 3