QueueTempo

Product

Consistency with the controls left in.

Define each brand once. Build exact recurring schedules. Review what comes next, publish through supported official APIs, and see every outcome.

Start freeCheck integrations

The operating system around the draft

Ten parts. One visible publishing loop.

The durable value is not a prompt box. It is reusable context, exact timing, approval, delivery, history, and recovery working together.

Organizations

Keep every brand, client, domain, member, Connection, Tempo, and queue inside a strict tenant boundary.

Brand profiles

Save audience, voice, offers, factual claims, required phrases, prohibited topics, and trusted Knowledge sources.

Tempos

Create recurring automations with a destination, Content recipe, timing, timezone, and approval policy.

AI drafting

Generate platform-specific Variants from approved brand context, then see the source and profile versions behind each draft.

Queue and calendar

Inspect an agenda anywhere, use a calendar on larger screens, and filter by Organization, Channel, Tempo, state, or date.

Approvals

Choose Review required or explicitly consent to Auto-publish. Material edits can trigger approval again.

Official Connections

Authorize eligible accounts with OAuth. QueueTempo never asks for a social password or hides browser automation behind a button.

Clear balances

Track AI credits separately from successful publishing allowance, with a visible reset date and auditable usage.

Reliability

Use idempotent delivery, bounded retries, reconciliation, and safe skips to avoid duplicate or stale posts.

Team roles

Give Owners, Admins, Publishers, Approvers, and Analysts only the controls their work requires.

Interactive demo · no account neededNorthstar Garden
AI credits 276/300
Tuesday, Jul 28 · America/New_York

Next in your queue

09:30
Needs reviewWeekday garden tip

Your herbs tell you when they are thirsty. Check the top inch of soil before you reach for the watering can.

12:00
Needs connectionNew arrivals

New arrivals are on the bench this week: compact tomatoes, three basil varieties, and the terracotta we keep selling out of.

Later this week · 3 more occurrences from 2 Tempos

Demo · nothing is published

Try it: approve a draft, repair the Instagram connection, or switch the brand voice.

Start with the next action

The queue is the product’s home base.

Upcoming Queue items show the exact scheduled time and timezone, Channel, source Tempo, draft state, and what a member can do next. Published history stays immutable.

  • Approve, reject, edit, reschedule, cancel, or copy to a new draft
  • Agenda fallback keeps the calendar usable on mobile and with assistive tech
  • Bulk actions state their exact Organization and selection scope
  • External post link appears only when a provider returns one

Tempos

Recurring schedules without calendar guesswork.

Each Tempo uses an IANA timezone and shows its next exact occurrences before activation. Daylight-saving behavior and missed slots follow explicit rules.

Frequency modes

IntervalEvery N hours
DailyN times inside a posting window
WeeklySelected weekdays and exact local times
MonthlyExplicit day or last day of month
One-timeExact date and time

Before activation

Preview the schedule and the cost.

  • See the next ten occurrence times in the selected timezone
  • Estimate AI-credit and publishing-allowance use
  • Generate a sample without silently activating the Tempo
  • Confirm Review required or record express Auto-publish consent
  • Check start, end, posting-window, and excluded-date rules

Two kinds of meter

Generation and delivery are counted separately.

One AI credit creates one usable platform-specific text Variant. Publishing allowance is charged only when an external platform accepts a destination target.

AI AI credit

One generated X draft uses one credit. One Instagram caption uses one. Adapting one Post for both Channels uses two. Manual writing and editing use zero.

↗ Publishing allowance

Each provider-accepted target uses one publish. Cross-posting to two Channels uses two. Failed, canceled, skipped, and manual-handoff targets use none.

See plan balances and limits

Failure recovery

Visible state beats hopeful retrying.

Before delivery, QueueTempo rechecks approval, schedule, connection health, balances, content validity, and the global pause state. After delivery, it records the normalized provider outcome.

  • Rate limits wait for the provider reset rather than hammering the API
  • Ambiguous timeouts reconcile before another publish attempt
  • Expired Connections prompt a safe, scoped reauthorization
  • Downtime does not produce a backlog burst
Ready

Valid, approved, inside the selected window, with a healthy Connection.

Ready
Needs review

The exact Variant is waiting for a permitted member to approve it.

Needs review
Outcome unknown

The provider response was ambiguous. QueueTempo will reconcile first.

Unknown
Skipped

No eligible content was ready, so nothing was published.

Skipped

Roles

Let people do their work without handing over everything.

Permissions are enforced by the server inside each Organization. Hiding a button is never treated as authorization.

Owner & Admin

Manage Organization settings, members, Connections, content rules, and safety controls.

Publisher

Create and manage posts and Tempos, with publishing controls that match the Organization policy.

Approver & Analyst

Approve exact Variants or inspect operational history without gaining billing or Connection authority.

Set the next beat

Build the first Tempo. Keep every step visible.

Start on the Free plan without a card, or read how Organizations, Brand profiles, schedules, and approvals work first.

Start freeRead the docs