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
The evergreen engine is genuinely deep — bulk import, weekly time slots that post automatically, categories, up to five variations per tweet, images, stories, carousels and videos, and Edgar's own shortened links that accept UTM parameters. That covers most of what I need to run queues at volume for a dozen brands; on failure notifications and retry I found no public information, which keeps this just below the dependable-at-volume level. 2 4 5 6