Direct marketing channel
Message your customers straight from your own app
Bite2Byte's push notifications let Australian restaurants message customers who have already ordered, straight through their own branded app on web and native, so the channel back to those customers belongs to the restaurant rather than to a marketplace.
The short answer
- Push notifications work on both the native app and the web app.
- Messages go to customers who opted in by using the restaurant's own app.
- Common uses are quiet-day offers, new menu items and pre-order reminders.
- The channel runs through the restaurant's own app, so the customer relationship stays with the restaurant.
- Customers can switch notifications off at any time, so frequency and relevance matter.
Practical ways restaurants use push
The notifications tool is the same one behind every use case below; only the message changes.
Quiet-day offers
A short-notice offer sent for a slow Tuesday lunch or a rainy Monday, timed to when the restaurant actually needs the traffic.
New menu items
Tell existing customers when a new dish, seasonal special or category goes live, instead of hoping they notice it in the app.
Pre-order reminders
A reminder for customers who order ahead regularly, useful around events, catering windows or busy service periods.
Loyalty prompts
A nudge when a punch card is close to full or a milestone reward is nearly earned, timed to bring the customer back.
Order updates
A push update on an order in progress, so the customer knows where things are without a phone call from the kitchen.
Owning the channel versus borrowing it
When someone orders through a marketplace, they are the marketplace's customer, and contact with them happens on the marketplace's terms. With Bite2Byte, the customer opened or downloaded the restaurant's own app, so the push channel is the restaurant's.
That only pays off if it is used well. An app that sends a notification every day gets muted or deleted. One that shows up with something genuinely worth knowing stays welcome.
Being responsible about frequency and opt-in
Push notifications go to customers who have already engaged with the restaurant's app, and they can turn notifications off from their device at any time. The channel works best when there is a real reason to send: a slow period, a genuine new item, a reward nearly earned. Sending on a fixed schedule regardless of relevance is what wears it out.
Questions, answered
- Do push notifications work on the web app or only the native app?
- Both. Bite2Byte supports native push on the iOS and Android apps and web push for customers using the web version, so a restaurant can reach its audience regardless of which version they use.
- Can customers opt out of push notifications?
- Yes, at any time, from their device's notification settings. Customers who have opted out stop receiving messages, which is why relevant, infrequent messages matter more than frequent ones.
- How often should a restaurant send push notifications?
- There's no fixed number. Send when there is a genuine reason: a quiet-day offer, a new menu item, a pre-order reminder. That keeps the channel useful rather than something customers mute or uninstall over.
- Is there a fee to send push notifications through Bite2Byte?
- Push notifications are part of the Bite2Byte platform, not a separate product. There's no public price list: pricing is a straightforward platform arrangement with no marketplace commission on orders, walked through for your restaurant's size and volume on a demo call.
Reach your own customers, on your own terms
Book a demo to see push notifications set up alongside loyalty and pre-orders on your menu.
Book a live demo