- Products
- SimplifyFlow
Channels, threads and calls — inside WordPress
SimplifyFlow
FluentBoard did it to Trello and FluentBooking did it to Calendly. SimplifyFlow does it to team chat: everything Slack and Pumble are used for all day, on your own site, your own users and your own database — with no per-seat bill and no history that expires.
In build
SimplifyFlow is in active design. Join the waitlist and you will get early builds — and a say in what ships first.
Talk.
The conversation surface every team already knows how to use, with nothing missing from it.
Channels
Public channels anyone on the site can find, private ones by invitation, and read-only ones for announcements. Topic, description and pinned items at the top, so somebody joining in month six can work out what a channel is for without asking. Archive a channel instead of deleting it and the history stays searchable.
Threads
Any message can become a thread, so a tangent stops taking the channel with it. Follow a thread you care about, or send the resolution back to the channel when it lands.
Direct and group messages
One-to-one and small groups, for the things that are not a channel's business. Same threads, same files, same search.
Mentions and reactions
Mention a person, a role or a channel. React with an emoji when a reply would just be noise — which is most of the time.
Scheduled send
Write it now, deliver it at nine. Nobody's phone goes off at 2 AM because you were clearing your head before bed.
Voice and video notes
Record a short clip in the browser instead of scheduling a meeting for it. Stored in your own media library like any other upload.
Drafts, edits and unsends
Edit with an edit marker rather than silently, delete with a tombstone rather than a hole. A channel people trust is one where the record is honest.
Meet.
The five-minute call that saves forty messages — started from the channel it is about.
Huddles
Audio-first calls you drop into from a channel, the way you would lean over a desk. No invitation, no scheduling, no meeting ID: the channel is the room. Turn video on when you need to, share a screen when pointing is faster than typing.
Video meetings
Full calls with the people in a channel, or with anyone you send a link to — including people who have no account on your site.
Screen sharing
Show the bug, the design or the spreadsheet instead of describing it.
Recordings
Keep a call for the people who were asleep in another timezone. The recording lands in the channel and in your media library.
Keep.
The part every hosted tool eventually charges you for, or quietly takes away: your own history.
History that does not expire
Every message, every file, every thread — kept for as long as you keep your database, because it is your database. No ninety-day cliff, no upgrade prompt standing between you and a decision your team made last year, and no bill that grows because you kept talking.
Search across everything
Messages, threads, files and the site's own content in one search, filtered by channel, person or date.
Files where files go
Drag anything in and it lands in the media library with a preview in the channel — one place for uploads, not two.
Pins, bookmarks and notes
Pin the decision, bookmark the link everyone keeps asking for, and keep a shared note per channel for the things a chat log is bad at holding.
Work.
The reason to put chat inside the site rather than beside it: the work is already in here.
The site posts into the channel
A new order, a failed payment, a form submission, a post going live, a booking, a stock warning from SimplifyStock — into the channel that cares about it, with the record itself one click away. No connector to configure and no third service holding the token, because both halves are already on the same install.
Automations
If this happens in the channel, do that on the site — and the other way round. Built from the events WordPress already fires.
Lists and handoffs
Turn a message into something with an owner and a state, so "can someone look at this" stops being the last word on it.
Integrations and webhooks
Incoming and outgoing webhooks, Slack-compatible payloads, and a REST API — so it fits what you already run rather than replacing it.
An MCP server
Point an AI agent at your workspace to summarise a channel, find a lost file or write the weekly update — through a key you issue, and read-only unless you say otherwise.
Everyone.
Members, guests and permissions — decided by the roles you already maintain, not by a second directory.
Your users are the members
Everyone who can sign in can already talk. No invitations to a second product, no seat list drifting out of sync with your team, and no monthly line item that grows every time you hire. WordPress capabilities decide who can see, post in, and manage each channel.
Guests, scoped
Give a client, a contractor or a partner a single channel and nothing else, on an account that expires when the work does.
Community channels
Open channels to members, students or customers, so a membership site or a course gets a real conversation instead of a comments section.
Presence and profiles
Who is around, who is heads-down, and who does what — read from the profiles the site already has.
Spaces
Separate workspaces on one install, each with its own channels and members, for an agency running more than one team.
Own.
Where the data sits, what it costs, and who can change either.
On your host, in your database
Messages, files and calls' metadata stay on infrastructure you control, under whatever data rules you already answer to. Export the lot whenever you want, set your own retention, and never find out from a blog post that your archive is now behind a higher tier.
Priced like a plugin
A licence for the site, not a fee for every person on it. Adding the tenth person costs the same as adding the second.
Runs on ordinary hosting
Real-time delivery that feels instant on the shared hosting most WordPress sites actually run on — not only on a server you tuned yourself. That is the hard part, and it is the part being built first.
How it works
Three steps, then it runs
- 01
Install it
One plugin. It reads the users, roles and capabilities already on the site, so there is nothing to import and no second directory to keep in sync.
- 02
Open a few channels
Start with the two or three that match how the team already works, decide who can see each, and let threads take the tangents.
- 03
Point the site at them
Send the events you care about — orders, forms, posts, bookings, stock warnings — into the channel that should see them, and stop checking four dashboards for things that could have found you.
SimplifyFlow works with
- WordPress
- WooCommerce
- Slack
- Zapier
- Webhooks
- WP-CLI
Questions
About SimplifyFlow
How does this compare with Slack or Pumble?
Feature for feature it aims at the same job — channels, threads, DMs, calls, files and search. What differs is where it runs and how it is priced: inside a site you already own, on your existing users, for a licence rather than a per-seat monthly, with history that is yours because the database is yours. If your company runs on Slack and always will, keep it — SimplifyFlow can post into it instead.
Is it a full replacement, or a companion?
For a team already run from a WordPress site — an agency, a shop, a membership, a support desk — it is meant to be the whole thing. For a company whose engineering org lives in Slack, it is more useful as the place where the site's own work gets discussed.
Where do the messages live?
In your own database, on your own host, exportable at any time. That is the point of building it here rather than as another hosted product.
Will it slow the site down?
Chat traffic is deliberately kept off the page-rendering path, and the real-time layer is being designed for ordinary shared hosting rather than for a tuned server. If it cannot be fast on the hosting most WordPress sites run on, it is not finished.
When can I use it?
It is in active design. The waitlist gets the early builds and a say in what ships first — and the order things ship in is being decided by what people on it say they open a chat tool for every day.
The rest of the family
Each one stands alone. Use one, use all five, or use one and ignore the others entirely.
SimplifyStock
LiveAI stock manager for WooCommerce
Forecasts demand from your own sales history and tells you what to reorder, how much, and when — before you sell out.
Learn moreSimplifyRoster
BetaShift scheduling for 24/7 support teams
One place to see who is covering every hour, across every timezone — with country holidays, leave and overtime handled where the schedule lives.
Learn moreSimplifySearch
PlannedAI product search for WooCommerce
Search that answers what a shopper meant, not what they typed — built on a catalogue it reads and structures for itself, so there are no synonym lists and no filters to maintain.
Learn moreSimplifyApps
PlannedSaaS tools for forms and operations
Internal tools without the internal tools project — forms, approvals and operational dashboards assembled from your existing data.
Learn more
Be first to use SimplifyFlow
The whole of modern team chat — channels, threads, direct messages, calls, files and search — running inside your own WordPress site, on the users you already have.