ReachFlow documentation
ReachFlow brings brand context, AI content creation, media, schedules, connected social accounts, publishing checks, and day-to-day operations into one organized workspace.
Start here if you are evaluating ReachFlow, preparing your first organization, onboarding a team, or learning how each part of the platform connects to the next.
On this page
Start with the right guide
The introductory path explains what ReachFlow is, how information moves through the product, the vocabulary used across the workspace, and the safest way to complete a first publishing workflow.
You do not need to understand every feature before starting. Learn the core model first, complete a small real workflow, and then move into the feature-specific guides as they are added.
01 · Product overview
What is ReachFlow?
Understand the problem ReachFlow solves, its primary capabilities, and who it is designed for.
Read guide02 · System model
How ReachFlow works
Follow the complete path from organization context to a validated and published social post.
Read guide03 · Vocabulary
Core concepts
Learn organizations, AI Brains, connections, schedules, media, publishing states, credits, and MCP access.
Read guide04 · First workflow
Quick start
Prepare an organization, connect a channel, create a schedule, review the result, and publish safely.
Read guideThe ReachFlow workflow
ReachFlow treats social publishing as a connected operational system. Brand knowledge informs creation; creation produces drafts and media; schedules place that work in context; validation checks provider requirements; and publishing records the final result.
- 01Create an organization and define the brand context.
- 02Prepare the organization's AI Brain with approved knowledge and visual direction.
- 03Connect the social accounts or custom destinations the organization is allowed to use.
- 04Create weekday, calendar, or daily scheduling rules for the required channels.
- 05Generate or write content and attach the correct media.
- 06Review the content, permissions, media requirements, and publishing readiness.
- 07Schedule or publish, then follow the activity and result inside ReachFlow.
What you can manage
The workspace is divided into focused operational areas. Each area keeps its own responsibility while sharing the same organization context and permission model.
AI Brain
Brand voice, audience, approved knowledge, goals, memories, and visual direction.
Content and media
Platform-ready copy, hashtags, visual prompts, generated images, and uploaded assets.
Schedules and calendar
Reusable weekday rules, daily work, calendar placement, and publishing timing.
Publishing
Connected providers, requirement checks, explicit approval, delivery, and status tracking.
ChatGPT MCP
Authorized content, media, scheduling, validation, and publishing actions through conversation.
Teams and reporting
Organization isolation, role-aware access, activity visibility, usage, and operational follow-up.
Supported publishing destinations
ReachFlow includes workflows for the major social networks used by modern teams. The exact publishing actions available to an organization depend on each provider's API, approved permissions, account type, media rules, and current platform policies.
- Facebook Pages
- Instagram professional accounts
- Threads
- X
- LinkedIn profiles and organizations
- TikTok
- YouTube
- Signed custom API destinations
How to use this documentation
Each page begins with the outcome it helps you achieve, then explains the concepts, prerequisites, safe workflow, and validation points. Use the left navigation to move between guides and the page outline to jump to a specific section.
The documentation is being expanded feature by feature. The initial introduction establishes a reliable shared vocabulary so future guides can stay precise without repeating the same foundation.
Documentation roadmap
Upcoming guides will cover AI Brain configuration, content generation, media management, schedule types, provider connections, publishing rules, ChatGPT MCP setup, teams, security, usage, billing, reporting, and troubleshooting in detail.
New feature guides will be added to this same navigation and will receive their own server-rendered page, canonical metadata, structured data, sitemap entry, and previous or next relationship.
