Early access. The queue is being built and opens on accounts as it rolls out.
The Content Queue is one list of every page job on the account: briefs, new pages, repairs, link passes and Autopilot runs. Each row shows the keyword or title, page type, status, who asked for it, who it is assigned to, the due date, the last Content score, Rankability and originality, and the WordPress draft or live link once there is one. Rows are created and updated by the jobs themselves, so the queue always matches what the writer and scanner are doing.
Statuses. Idea, planned, briefed, writing, review, changes, approved, scheduled, published, failed, dismissed. A failed write never charges credits.
Three views. The client queue is one site, for everyone on the account who can see that site. The agency queue is every site on the account, with filters for site, status, assignee, kind and date, counts at the top for waiting on approval, writing, failed, published this month and credits short, and bulk approve, reassign, reschedule and dismiss. Vertical Web sees an all accounts view for support.
Row actions. Open the brief, open the draft, approve, request changes with a note, send to WordPress, publish by the site’s publish mode, assign, set a due date, dismiss. A change request moves the row to changes; the writer’s repair path can run on the note as its action plan item (3 credits) once someone with spend rights confirms.
Clients. A client login sees the queue for their site only and never sees credits, prices, other clients, API keys or settings. By default a client reads; the agency can allow approving drafts and leaving notes per client user.
Digest. A weekly email to owners and admins lists items waiting on approval, failures, and what was published with its score. It is on by default on agency plans and off on single site plans; change it under Settings, Notifications.
Related: Content Ideas; Users and roles; Autopilot and publish modes; Connect WordPress.
