Review-first publishing
Every new Tempo starts in Review required. Drafts wait in the queue with their exact publish time; a permitted member approves the precise text and media, or rejects and regenerates.
Automation earns trust; it should not demand it upfront. Review required blocks publishing whenever approval is missing, even if that means a visible skip instead of an unreviewed post.
Approvers see the destination Channel, the scheduled local time and timezone, the source recipe, warnings, and remaining balances. Deciding takes seconds because the context is already assembled.
When a pattern proves reliable, flip that Tempo to auto-publish with an explicit acknowledgement. Review history remains intact either way.
Straight answers
Credits are spent generating usable variants, not approving them. Review itself is free; regeneration costs a credit per new variant.
The occurrence is skipped visibly rather than published unapproved, and members are notified. The cadence continues untouched.
Yes, per-Organization membership means an agency reviewer can hold the Approver role in each client workspace they serve.
Keep reading
Set the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
Set the next beat
Start free, describe your brand once, and watch the next ten post times appear before anything goes live.