Support

Tell us what needs attention.

Start with the Organization, a safe description, and an optional request or event ID. Never send a social password, OAuth token, authentication cookie, or payment-card detail.

Choose a path

Product guidance

Start with Organizations, Brand profiles, Connections, Tempos, queue state, balances, and failure recovery.

Browse documentation →

Integration eligibility

Check supported account types, content types, automatic-publishing status, restrictions, and verification dates.

Check integrations →

Security or privacy

Report a suspected issue with a safe description. QueueTempo will establish a restricted diagnostic channel if more detail is needed.

Read the security overview →

Account access

Use the supported sign-in recovery flow first. Support will never ask for a password or recovery token.

Recover account access →

Support request

Open a safe email request.

This form prepares a message in your email app. It does not upload or store the request on this page.

Use the opaque ID shown in QueueTempo. Do not paste a token or signed URL.

Explain what you expected, what happened, and the approximate time and timezone. Remove private post text unless it is essential.

Service status

No invented green lights.

Status is reported per component rather than as a single badge, so you can tell whether the problem is scheduling, drafting, a specific provider, or billing.

A provider is never marked operational while QueueTempo’s own Connection to it is broken, and the status surface runs independently of the app so it stays reachable during an incident.

App and schedulerREPORTED SEPARATELY
AI draftingREPORTED SEPARATELY
X and Instagram publishingREPORTED PER PROVIDER
Email and billingREPORTED SEPARATELY