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 Skeptic
A content calendar, mass-scheduling across seven networks, bulk duplicate and move, live previews, and link shortening with UTM tags are all documented. What I count on the heavier side of the scale is only two items — bulk scheduling and UTM links — with no best-time suggestions, no queue or CSV import, and nothing on stories or reels anywhere we read. And what happens when a post fails matters to me: the only failure handling captured is a manual X reconnection guide, not a notification with a retry. 3 4 8 10 11