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 at 3am.
0 — One post to several networks at once with no per-network variation and no calendar.
3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.
5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.
8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.
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 Analyst
The publishing page shows queues, a visual calendar, CSV upload of up to 200 posts, per-post custom text, first comments and threads, post previews and Reels/Stories support, with UTM tracking reaching Google Analytics — the shape of dependable scheduling at volume. But the support article states Publish & Respond is being retired from Mention with Agorapulse as the official recommended replacement, so the captured pages position the publish surface with the sister product; we also found no public information on failure notifications or retry when a scheduled post fails. 2 3