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 Brand Governance Officer
The publishing API covers a wide service list — Facebook, LinkedIn, TikTok, YouTube, Pinterest, Google+, Sina Weibo and VK — with a calendar surface, an endpoint returning messages posted or scheduled, draft and error states in the message lifecycle, and content types from carousels to Instagram reels. Approval and native-scheduling states sit in the same flow. We found no public information on bulk upload, best-time suggestions, link shortening or retry after failure, which is what the higher rungs describe. 2 3 4