DispatchOS Logo
Help & support

Keep your content moving.

DispatchOS turns your product context into a weekly content calendar so you can review, schedule, and publish consistently while you keep building.

Start here

  1. 1Complete onboarding with your website URL, audience, tone, and publishing preferences.
  2. 2Connect at least one social channel in Settings.
  3. 3Generate your first weekly calendar.
  4. 4Review the posts in the staging area.
  5. 5Edit, queue, hold, or drop posts as needed.
  6. 6Let DispatchOS publish automatically, or use manual publishing where a channel requires it.

How DispatchOS works

DispatchOS uses your website and onboarding information to create a working context for content generation. It then creates a weekly calendar with posts mapped to specific days, times, channels, and content categories.

Your workflow stays in your hands:

  • Edit a post before it is published.
  • Queue a post for publishing.
  • Hold a post for later.
  • Drop a post you do not want to use.
  • Regenerate a week when you want a fresh batch.

Regenerating a week may replace the current batch and remove edits made to those posts. Review the confirmation message before continuing.

Onboarding

Website URL

Use the website that best explains your product, company, or personal brand. A clear website with current positioning produces better results.

If your website is incomplete or mostly empty, add useful context during onboarding, such as:

  • Who the product is for
  • The problem it solves
  • Important features
  • Your preferred point of view
  • Current launches or updates
  • Topics you do not want to discuss

Audience and tone

Be specific about your audience. “Startup founders” is less useful than “technical founders building early-stage SaaS products.”

Choose a tone that sounds like you. Generated content should be treated as a strong first draft, not as a substitute for your judgment.

Reviewing your calendar

Before queuing posts, check:

  • The post is factually accurate.
  • The post sounds like your voice.
  • The call to action is appropriate.
  • The content is not repeating another post in the batch.
  • The scheduled time is correct for your timezone.
  • The selected channel is appropriate for the format and length.

Publishing and channel status

Channel availability can vary based on platform permissions, API access, and your connected account.

Connected

Ready to publish.

Reconnect required

The authorization or token has expired.

Manual

DispatchOS can stage the post, but you must copy or publish it yourself.

Beta

The integration is available for testing and may have limitations.

Unavailable

The channel cannot currently be used.

If a channel is marked Manual, queued posts will remain available in your staging area rather than being silently lost.

Scheduling and timezones

Your publishing schedule is configured in Settings. Confirm your timezone and publishing times before queuing a week.

If you join during the middle of a week, DispatchOS may generate content for the remaining publishing days rather than backfilling days that have already passed.

Generation and usage

Each generation request uses compute and AI capacity. Depending on your plan:

  • Full weekly generations may count toward your monthly allowance.
  • Regenerating a week may count as another generation.
  • Very large websites or repeated requests may be limited.

Usage limits are intended to keep the service reliable and predictable for everyone.

If you reach a limit, review your usage in the app or contact support before retrying repeatedly.

Analytics

Analytics become available after posts are published and the connected platform returns performance data.

Metrics may differ by channel. For example, one platform may provide impressions while another only provides reactions, comments, or reposts. A delay between publishing and analytics refresh is normal.

Common problems

My website could not be read

Check that:

  • The URL is correct and publicly accessible.
  • The site does not block automated requests.
  • The important product information is visible on the site.
  • The site does not require a login to view its content.

If the scrape still fails, add the key facts manually and try again later.

The generated posts are too generic

Add more specific context about your audience, product, point of view, and current work. You can also edit the website content or onboarding settings and generate a fresh batch.

A social connection stopped working

Open Settings and reconnect the affected channel. If the problem continues, include the channel name and the time of the failure when contacting support.

A post failed to publish

Open the post to review its status and error message. Check that the channel is connected, the content meets the platform's limits, and the scheduled time has passed. Do not repeatedly click publish if the platform may have accepted the first request.

I edited a post, but my edit disappeared

A regeneration may replace the current batch. If you need to preserve edits, do not regenerate that week until you have confirmed how the regeneration flow will affect the batch.

Analytics are missing

Analytics may take time to arrive, and some platforms expose fewer metrics than others. Confirm that the post was published successfully and that the channel is still connected.

Account, billing, and cancellation

Use the account and billing controls available in Settings to review your plan, usage, and subscription status.

For billing questions, include:

  • The email on the account
  • The plan name
  • The relevant invoice or transaction date
  • A short description of the issue

Do not send passwords, access tokens, or secret keys in a support request.

Privacy and security

DispatchOS may process your website content, onboarding information, generated posts, publishing settings, and social authorization data to provide the service.

You should:

  • Connect only accounts you control.
  • Review generated content before publishing.
  • Never paste passwords or private keys into post content or support messages.
  • Disconnect channels you no longer use.
  • Contact support if you believe an account or token has been compromised.

See the Privacy Policy and Terms of Service for the complete details of data handling and account responsibilities.

Contact support

When contacting support, include:

  • The email associated with your account
  • The page or workflow where the issue occurred
  • The channel involved, if applicable
  • The approximate time of the issue
  • The post, batch, or generation involved
  • A screenshot of the error, if safe to share
  • The steps you took immediately before the issue

Never include passwords, API keys, access tokens, or other secrets.

Product limitations

DispatchOS is designed to reduce the work of planning and publishing content, not to remove your responsibility for what gets published.

  • AI-generated content can be incorrect or incomplete.
  • You are responsible for reviewing content before publication.
  • Platform permissions and API behavior can change without notice.
  • Automated publishing may not be available for every channel.
  • Analytics are dependent on the data provided by each platform.
  • A website scrape does not replace your own product and customer knowledge.

We recommend starting with one connected channel, reviewing your first weekly calendar carefully, and expanding your automation once the workflow feels right.