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
Nine channels publish natively at the exact minute set, with per-channel caption customisation, bulk upload of a month at once, a recurring queue with no cap on scheduled posts, best times surfaced from audience behaviour, and first-comment and carousel scheduling. Failure notifications go to the administrator by default, can be redirected to up to five addresses, and name the cause — an expired authentication token or a network outage. I found no public information on a retry for failed posts or on link shortening with UTM tags, which holds this short of dependable at volume. 3 4 12