WordPress Bookings
WordPress Booking Notifications
Whatever booking plugin you run, get a push notification the instant an appointment is booked or cancelled — routed to the right staff member, with acknowledgement and escalation. Connect via the FlowAlert plugin, a built-in webhook, or the REST API.
1,000 free events/month · No card required
Why booking-plugin alerts get missed.
Most booking plugins only send email — and email lands in an inbox nobody is watching during a busy day.
There's no confirmation a staff member actually saw a new appointment.
A late cancellation isn't surfaced in time to re-fill the slot from your waitlist.
One missed appointment is a no-show you could have prevented and lost revenue.
FlowAlert pushes each booking straight to the right person's phone — with optional acknowledgement and automatic escalation — no matter which booking plugin fired it.
1,000
Free events every month to start. No card required.
How it works
From event to acknowledged alert — the whole path, in order.
Connect your booking plugin — the FlowAlert WordPress plugin (one click), the plugin's built-in webhook, or the REST API
A customer books or cancels — the event is sent to FlowAlert instantly
FlowAlert's routing rules send it to the right staff member or team
They get a push notification on their phone — iPhone or Android
They acknowledge — if no one responds in time, it escalates to a manager
See it in action
booking.created
→ Front Desk · Priya
What you get
Works with any WordPress booking plugin
Push notifications — not an unwatched inbox
Alerts on new bookings and cancellations
Require acknowledgement & auto-escalate (Pro option)
Route by service, staff member, or location
Cancellations surfaced instantly so slots get re-filled
Works on iPhone and Android
Free plan available — up to 1,000 alerts per month
Exactly how each booking plugin connects.
Not every plugin connects the same way. Amelia, FluentBooking, LatePoint, MotoPress Hotel Booking and Five Star Restaurant Reservations are true one-click toggles in the FlowAlert plugin. Others expose their own webhook you point at FlowAlert, and the rest connect through the REST API or Zapier. Here is what to expect from each.
booking.created · booking.cancelledInstall the FlowAlert plugin and enable Amelia under Bookings. It hooks amelia_after_booking_added and amelia_after_booking_canceled directly — customer name, time and service are read from the appointment and pushed automatically.
booking.created · booking.cancelledOne toggle in the FlowAlert plugin. It listens on fluent_booking/after_booking_scheduled and booking_schedule_cancelled, so every scheduled or cancelled slot pushes with the attendee and start time — no webhook to wire up.
booking.createdNow a native toggle in the FlowAlert plugin via LatePoint's latepoint_booking_created hook. Customer, service and start time are extracted from the booking model and pushed the moment a booking is made.
booking.created · booking.cancelledOne toggle in the FlowAlert plugin. It listens on mphb_booking_confirmed and the status-change hook for cancellations, so a confirmed stay pushes with the guest name and check-in/check-out dates — lite and pro both work.
booking.createdOne toggle in the FlowAlert plugin via the rtb_insert_booking hook — every new reservation request pushes with the guest, party size, and requested time, so the host stand can confirm it before the guest gives up.
booking.created (custom payload)Booknetic is closed-source with no PHP hooks, but it ships a Webhooks workflow action. Add one pointing at your FlowAlert /events URL with your API key and map the booking fields into the title and body. A few minutes in Booknetic's own UI, no code.
booking.created (your mapping)These connect through the FlowAlert REST API — POST the booking to /events from the plugin's automation/webhook step or an automation hub. You control exactly which fields land in the alert.
booking.created (via Zap)Bookly's core is fully encapsulated and exposes no developer hooks, so a native toggle isn't possible. Connect it through Zapier or the REST API instead — the setup guide has the exact Zap steps.
Common questions
The things people ask before connecting this — the docs cover the rest.
Any of them. Amelia and FluentBooking connect natively via the free FlowAlert WordPress plugin. LatePoint and Booknetic have built-in webhooks you can point at FlowAlert with no code. Everything else — BookingPress, Simply Schedule Appointments, Easy Appointments, Bookly, custom systems — connects via Zapier or the REST API.
The FlowAlert plugin is a one-click toggle for the booking plugins it supports natively (Amelia, FluentBooking). For others, you use the booking plugin's own webhook or POST to the FlowAlert REST API — both take only a few minutes.
Yes. As long as the booking details are in the event, FlowAlert's routing rules send each booking to the right person or team.
Yes — push via APNs on iOS and FCM on Android, on the lock screen with sound, even when the app is closed.
FlowAlert starts free with up to 1,000 alerts per month. Pro is a flat $29/month — one saved booking a month more than pays for it.
Stop missing what matters.
Set up FlowAlert in under two minutes: connect a source, define your first routing rule, and the right person’s phone knows from then on.
No card required · Free plan forever · REST API included