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 Brand Governance Officer
The composer customises text and media per network with per-channel previews, and the calendar and list views, bulk upload, queue-based scheduling up to 5,000 posts on paid plans, suggested posting times, and link shortening with UTM parameters are all documented, alongside first comments, threaded posts and reminders for stories. We found no public information on how a failed post is surfaced or recovered, which is what keeps this short of dependable-at-volume. 5 5 6 2