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 Analyst
Bulk upload, a queue of up to 5,000 scheduled posts per paid channel, per-network customisation with per-channel previews, audience-based optimal-time suggestions and link shortening with UTM parameters are all documented, with calendar and list views side by side. Recurring republication is in beta for a set number of repeats, stories go out as mobile reminders rather than through the API, and we found no public information on failure notifications with a one-click recovery. 5 5 6 2