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
The publishing story is well evidenced: bulk import, evergreen recycling through a content library that retains posts until the customer deletes them, custom time slots, stories and YouTube Shorts, and link shortening with UTM parameters, all scheduled weeks or months ahead across ten networks. What the captured pages do not show is failure notifications with a retry, and best-time recommendations drawn from the account's own history, so this falls short of dependable publishing at volume. 1 2 4 5 6