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
Scheduling days, weeks or months ahead across all the networks, with evergreen recycling on custom weekly time slots, bulk import, Edgar Links with UTM parameters, and images, stories, carousels and video is documented — the queue-and-recycle engine is clearly real. What I could not find on any captured page is what happens when a post fails: no failure notification and no retry are described, and best-time suggestions appear only as a vague instruction to optimize post timing. 2 4 5 6