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 Data Protection Officer
Per-network customisation with separate text boxes, list and calendar views, bulk upload, queue-based scheduling with per-day posting times, suggested optimal times based on audience engagement, link shortening with UTM parameters, and per-channel previews are all documented, plus carousel, threaded-post and first-comment support. Recurring posts are a beta that cannot repeat indefinitely, and we found no public information on what happens when a scheduled post fails or how a failure is recovered, which keeps this below the dependable-at-volume level. 5 5 6 2