SimplifyFlow documentation

SimplifyFlow is in design. This page exists so the documentation URL is stable from day one — bookmark it and it will fill in rather than move.

What it will cover

• Installation — one plugin, what it adds to the admin, what it stores in your database, and what it does to page load (nothing: chat traffic is kept off the rendering path).
• Channels — public, private and read-only channels, topics and pinned items, archiving, and how WordPress capabilities decide who can see, post in and manage each one.
• Threads and mentions — keeping a channel readable, mentioning a person, a role or a channel, and how notifications are derived from both.
• Direct messages — one-to-one and small groups, and what an administrator can and cannot see.
• Calls — huddles, video meetings, screen sharing, links for people with no account, and where recordings are stored.
• Files and search — uploads in the media library, search across messages, threads, files and site content, and the filters that make it usable.
• Guests and spaces — scoping an external account to one channel, expiring it, and running more than one workspace on a single install.
• Events into channels — sending orders, forms, posts, bookings and stock warnings into the channel that should see them.
• Automations, webhooks and the API — incoming and outgoing payloads, Slack-compatible formats, and the MCP server for AI agents.
• Retention and export — what is kept, for how long, and how to get all of it out.

Shaping it

The hard part is real-time delivery that feels instant on ordinary shared hosting rather than only on a server you tuned yourself. That is the problem this is being built around, and it is why there is no date on it yet.

If you run a team or a community from a WordPress site and have a view on what a chat tool must have on day one — and what it can do without — we want it.

Join the waitlist or read the product page.