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
Bulk upload, list and calendar views, per-network customization with per-channel previews, audience-based time suggestions, and link shortening with UTM parameters give me a working surface I could run twelve brands on, with queues up to 5,000 posts per channel on paid plans. Recurring posts are in beta for a set number of repeats and the pages say a post cannot be set to repeat indefinitely. We found no public information on failure notifications with a retry. 5 5 6 2