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 Community Manager
Scheduling is the strong suit: content goes out to ten networks days to months in advance, with bulk import, an evergreen library that recycles on weekly time slots, up to five variations per post, images, stories, carousels and video, and shortened Edgar Links that take UTM tags. We found no public information on best-time suggestions or on what happens when a post fails — no failure notification or retry is described on any page we read, which is the first thing I would ask about. 1 2 4 5