The alerting layer for the tools you already run. Not a booking system, not a chat app — the layer that makes sure the right phone buzzes.
FlowAlert takes the events that matter — a new order, a booking, a failed payment, a support ticket — routes each one to the person who needs to act, and makes sure they actually do.
1,000 free events/month · No card required
Group chats tell everyone about everything. FlowAlert tells the one person who needs to act — and escalates if they don’t.
An alerting layer that sits on top of your stack. Four things at its core.
None of them is “another app to run your business in” — FlowAlert is the connective tissue between what happens and who hears about it.
A routing & on-call layer
It takes events from your systems, matches them against your rules, and delivers each one to the right person or team — escalating if no one responds.
Source-agnostic
Anything that can send a webhook or API call — or runs our one-click WordPress plugin — can feed it: WooCommerce, bookings, forms, monitoring, or your own backend.
Mobile-first & accountable
Push notifications to iOS and Android, tap-to-acknowledge, automatic escalation, and on-call schedules so the right person is always reachable.
A complete audit trail
Every event, notification, and acknowledgement is logged and timestamped — so you always know what fired, who got it, and whether they acted.
It’s middleware. Not a replacement for your tools.
If you’re wondering whether it competes with something you already use, it almost certainly doesn’t — it works with it.
Not a booking system, POS, CRM, or help desk
It connects to those and notifies you on their events. It never becomes the system of record.
Not a group chat
Unlike Slack, Teams, or Telegram, it routes each alert to a specific person — not a channel where it scrolls past, unowned.
Not email or SMS marketing
It delivers operational push notifications to your team’s phones, not campaigns to your customers.
Not an enterprise incident-command suite
It covers what small teams actually use — on-call, escalation, acknowledged alerts — without the heavy setup of a PagerDuty or Opsgenie.
More on the two it’s most often confused with: FlowAlert vs Slack·FlowAlert vs Opsgenie
It works with your stack. It doesn’t become it.
FlowAlert earns its place by working with what you already have — and getting out of the way of the systems that do the actual work.
The honest capability list. What it can do — and what it won’t, by design.
Route by event type, priority, and any field in the payload
Notify individuals, whole teams, or both
Require acknowledgement and auto-escalate if no one responds
Run on-call schedules — recurring or one-off
Set per-person quiet hours and a custom sound per event type
Watch every site from the outside — built-in uptime checks, nothing to install
Keep a full audit trail and response-time analytics
Separate workspaces per location, brand, or team
Acknowledgement, escalation, on-call schedules & analytics are on the Pro plan.
Send email or SMS — it delivers push to the app, by design
Guarantee delivery to a phone that’s off or out of signal — escalation is the safety net
Replace the systems it integrates with — it sits on top of them
Act as a chat or conversation tool — there’s no channel to talk in
When to reach for it. And when it’s honestly not the tool.
Reach for it when…
- A real event needs a specific person to act, fast
- “Did anyone actually see it?” is a question you can’t afford to ask
- Your alerts are buried in a shared inbox or a noisy chat channel
It’s not the tool if…
- You need to message customers — that’s email or SMS marketing
- You want a place to discuss and collaborate — that’s chat
- You need a full incident-command platform with postmortems
Straight answers. The questions everyone asks first.
Still unsure whether FlowAlert fits your setup? The docs go deeper — or just ask.
No. FlowAlert connects to your booking system (like Amelia or FluentBooking) and sends a push notification the moment a booking comes in or is cancelled. It doesn’t take or manage reservations itself — your booking tool stays the system of record.
No, it complements them. Chat tools are built for conversation, so alerts scroll past in a shared channel and nobody owns them. FlowAlert routes each alert to a specific person, requires acknowledgement, and escalates if they don’t respond. Keep using Slack to talk; use FlowAlert for the events that need an owner.
No — FlowAlert delivers push notifications to the FlowAlert app on iOS and Android. Push is faster, free to send, and lets recipients acknowledge with one tap. If a phone is offline, escalation passes the alert to the next person.
It overlaps with the parts small teams actually use — on-call schedules, escalation, and acknowledged mobile alerts — without the enterprise setup or per-seat pricing. It is not a full incident-command platform with hundreds of native integrations and postmortem tooling.
Anything that can make a web request: our one-click WordPress plugin (WooCommerce, bookings, forms, support tickets), Zapier, or a direct REST API call from any language or system. Business events usually come from a plugin; technical events come from one POST.
No. FlowAlert sits on top of your existing tools. You keep your store, booking system, help desk, and chat exactly as they are — FlowAlert just makes sure the right person hears about the events that matter.
Now see it route an alert. Connect any source, define one rule, and the right phone buzzes in seconds.
No card required · Free plan forever · REST API included