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
The content calendar, mass-scheduling with a few clicks, bulk duplication and movement of posts across profiles, live post previews, and link shortening with UTM tags are all documented on the publishing pages. We found no public information on CSV import, best-time suggestions, queue or evergreen scheduling, stories or reels, or automatic failure notifications with a retry — the only failure handling captured is a manual help article on reconnecting X. 3 4 8 10 11