Billing Account is different
The Billing Account owns the subscription and pooled entitlements for one or more Organizations. It does not merge content visibility or weaken tenant isolation.
Documentation
Keep the whole workflow in view.
Learn the nouns, build the first Tempo safely, and know exactly what QueueTempo will do before you enable automatic publishing.
Browse by task
From setup to recovery.
QueueTempo uses product-specific terms so schedule, content, destination, and billing state remain unambiguous.
Quick start
Your first safe publishing rhythm.
Nothing should publish merely because you opened the builder. Activation is an explicit final step after schedule, sample, balance, and approval checks.
- 01Create Account
- 02Add Organization
- 03Define brand
- 04Connect Channel
- 05Preview Tempo
- 06Confirm activation
1. Create an Account and verify the email address
Verification is required before publishing, billing, invitations, and sensitive Organization changes. Keep recovery access current and review active sessions from account security.
2. Create an Organization for one brand or domain
Set its name, primary website, timezone, locale, and posting defaults. Use a separate Organization for each client or brand whose content and member access must stay isolated.
3. Add trusted brand context
Record the audience, products or services, voice traits, required and prohibited phrases, factual claims, calls to action, and Knowledge sources. Review imported URL facts before treating them as approved.
4. Connect an eligible destination
Read the provider requirements before OAuth. After connecting, confirm the exact provider identity, Channel, granted scopes, health, post types, and limit observation date.
5. Build and preview a Tempo
Select the Channel, Content recipe, recurrence, IANA timezone, start and end conditions, posting window, exclusions, and approval policy. Review the next ten exact times and the expected credit and publishing use.
6. Generate a sample and activate deliberately
A sample does not activate the Tempo. Confirm Review required or record express Auto-publish consent, then activate. The dashboard will show the next concrete action.
Organizations
The content and authorization boundary.
An Organization represents one brand, company, client, project, or primary domain. It owns its Brand profile, Knowledge sources, members, Connections, Channels, Tempos, queue, posts, files, audit history, and settings.
- Switch context explicitly; never infer it only from a client-side control
- Use roles to separate management, publishing, approval, and analysis
- Archive before deletion when you need a reversible stop
- Export Organization data before a permanent deletion request
Connection health
healthyCapability checks passed
expiringReauthorization may be needed soon
reauthConnect again before publishing
restrictedProvider or policy limits the action
unknownDo not assume delivery is safe
Connections
Authorize a destination, not a promise.
A Connection is the OAuth-authorized provider account. A Channel is the concrete destination selected from it. QueueTempo enables only the exact post types that the account, granted scopes, provider, and product status allow.
- Never provide a social password
- Confirm identity and scopes after OAuth returns
- Reconnect from the scoped action when health requires it
- Disconnect stops future claims and deletes or revokes tokens promptly
Brand profile
Approved context in. Traceable drafts out.
Customer-provided text, files, URL snapshots, product facts, campaign notes, and content topics can become Knowledge sources only after their status and provenance are visible.
State what can be claimed.
Products, services, factual claims, defaults, links, locale, and spelling preference.
Set how the brand sounds.
Audience, voice traits, emoji preference, hashtag preference, and calls to action.
Draw hard boundaries.
Required phrases, prohibited phrases, excluded topics, and sensitive-industry controls.
Tempos
Timing, content, destination, and approval in one contract.
Use Every N hours, N times per day, selected weekdays and times, a monthly day, last day of month, or a one-time exact schedule.
Queue & approvals
Work the next item, then see its whole history.
Each Queue item carries an exact target, Variant, scheduled time, timezone, source Tempo, approval policy, and operational state.
- Review, edit, approve, reject, reschedule, cancel, or duplicate
- Revalidate every material edit before publish
- Use agenda view on narrow screens and as the calendar alternative
- Keep published records immutable and link to the provider result when safe
Review required
A permitted member must approve the exact Variant before its slot.
Auto-publish
Requires recorded express consent and remains subject to every safety check.
Balances
Reserve, settle, and explain.
AI AI credit lifecycle
Reserve before generation. Consume when a usable Variant is stored. Release when a provider, network, internal, or policy failure produces no usable Variant.
↗ Publishing lifecycle
Settle one allowance unit only after a destination provider accepts the target. Failed, canceled, skipped, and manual-handoff outcomes do not count.
Balances do not roll over. See plans and exact limits.
Use the state, not guesswork
Needs connectionReauthorize the exact Connection
FailedRetry or copy to draft when safe
SkippedReview why no eligible target existed
UnknownWait for reconciliation before retry
Failures & retries
Recover without publishing twice.
Retry behavior depends on the failure class. Provider rate limits wait for reset. Temporary network and 5xx failures use bounded backoff. Ambiguous outcomes reconcile first.
When a slot cannot publish safely, QueueTempo records a visible skip instead of sending an unapproved, stale, duplicate, or wrongly targeted post.
Account security
Protect identity, ownership, and support access.
Use a current verified email, review active sessions, apply the smallest practical role, and require recent authentication for destructive changes.
List and revoke access.
Sign out unknown or old sessions and recover through enumeration-safe flows.
Keep one responsible owner.
QueueTempo blocks removing the last Owner and audits transfers of control.
Share safe diagnostics only.
Use an optional request or event ID. Never send passwords, tokens, cookies, or payment details.
Set the next beat
Ready to set the first Tempo?
Start free, keep Review required on, and activate only after the next exact times and sample look right.