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 Agency Lead
Six networks publish from one dashboard into a shared calendar with drafts, colour-coded campaign labels, bulk scheduling, best-time hints, first-comment scheduling and UTM tags — that is my weekly client grind handled. Their own YouTube pages state you can only moderate comments and track stats there, and we found no public information on queue or evergreen scheduling, per-network text variants, or failure notifications with a retry, so I cannot yet call it dependable at volume. 2 3 10 2 1