Notifications that reach you when you're not at the screen
Every event that needs a human now goes through one system: recorded in the bell, filtered by category, and escalated to your phone or your inbox on your terms. The order that arrived while nobody had the board open, the booking sitting unapproved, the subscription payment that failed quietly — they all reach you.
The cost of finding out late.
An order that lands while nobody has the board open. A booking request sitting unapproved for two days. A subscription payment that failed without telling anyone. Each of these is cheap to fix immediately and expensive to discover a week later.
Recorded first, escalated second
Every notification is written to your history whatever else happens, so the bell is a reliable record even if a push never lands.
It knows where to send you
Each notification carries the link to the screen that resolves it — the order board, pending bookings, or your billing settings.
Staff devices count
Push registers against staff logins too, so the phone in the apron pocket is the one that buzzes for a new table order.
One system, five categories, your rules
Table orders, bookings, loyalty, billing and account notices are separated so the urgent ones can reach your phone at eight on a Saturday while the rest wait quietly in the bell for you.
What partners can do
Notifications in action
Table orders, bookings, loyalty, billing and account notices are separated so the urgent ones can reach your phone at eight on a Saturday while the rest wait quietly in the bell for you.
What actually changes on the floor
The point is not more alerts. It is that the handful of things which genuinely need a person get to one, and everything else stops needing a watched screen.
The kitchen hears it
A short chime on each new order, switched on per device — so a wall screen works without anyone staring at it.
The owner is told once
Failed subscription payments and broken card connections raise a high-priority notice instead of being discovered at cancellation.
Nobody is woken twice
Per-category push and email switches mean turning off the 2am order alert does not also turn off your billing warnings.
Portal workflow
Something happens
A diner orders, a customer requests a booking, a tab asks to settle, or a subscription payment fails.
It is recorded
The notification is written to your history with a title, a plain-English line and a link straight to the screen that resolves it.
It reaches you
The bell count moves, the board chimes, and — where you have allowed it for that category — your phone buzzes or an email arrives.
You act from the notification
Tapping opens the exact place to act: the order board, the pending bookings tab, or your billing settings.
Fewer things falling through the gaps
Most lost revenue in a small venue is not a bad decision — it is an unseen request. Notifications close the window between something happening and someone knowing about it.
Requests get answered
A booking that needs approval raises an alert instead of waiting for someone to open the right tab.
Problems surface early
A card connection that fails to renew is a silent outage until you are told — after which it is a two-minute reconnection.
History when you need it
Ninety days of filterable record answers 'did we ever get told about that?' without a support ticket.
Business outcomes
Useful partner help articles
Helpful guides for partners using this feature.
Stop watching the screen.
Let the orders, bookings and billing problems that need you come and find you instead.