Skip to content
Help

Notifications

Your own dashboard alerts, transactional email and mobile push to customers, and sending email from your own domain.

Settings & billing3 min read

Settings → Notifications.

#Your alerts

Your alerts are yours alone. Turning one off is not a change your team sees, and each person on your staff picks their own.

Under Your alerts, tick the events you want to hear about — new orders, cancellations, failed payments, reservations, waitlist joins, failed prints, low stock. You only see the events you have permission to see, so a cook is never alerted about a payment they cannot open.

When one arrives, a toast slides in at the bottom of the screen with the order number, the channel, the table or delivery address, and the total. Click it to open the order. The bell in the top bar keeps the last thirty, and the red count clears the moment you open the list.

#Sound

Play a sound adds a short chime to every alert. It starts off, and you have to turn it on from the page itself — browsers refuse to play audio until someone clicks, so there is no way to arm it for you.

The sound is remembered per device. Turn it on once on the kitchen tablet and once on your laptop; each one asks separately, and a device you never enabled stays silent.

#Browser notifications

Browser notifications put alerts on your desktop when the dashboard is in a background tab or on another screen. Switching it on asks your browser for permission — that prompt only appears when you click, never on load.

If you dismissed the browser prompt earlier, the toggle cannot bring it back. Allow notifications for the site in your browser settings, then turn it on again here.

#Muting a branch

Every branch you can see is listed under Branches with a switch. Turn one off and its alerts stop reaching you, while the rest keep coming. Nobody else's alerts change.

Muting is the right tool when you cover one location but can see several. To stop a whole category instead — every reservation, say — untick the event rather than muting branch by branch.

#What Restro sends

  • Order confirmation when an order is placed or paid
  • Order status updates
  • Review requests when an order completes, if the Reviews extension is on
  • Magic links and one-time codes for customer sign-in, if Accounts is on

#Email and push

Email goes to every customer who gave you an address. Push notifications go to customers who installed your mobile app and allowed notifications — they are faster and far more likely to be seen, which matters most for "your order is on the way".

Both are driven by the same order status changes, so you do not maintain them separately. There is nothing to switch on: push starts working once a customer installs the app, and customers choose what they receive in the app under Account → Notifications.

Order updates and marketing are separate consents. A customer who turned off promotions still hears about their order.

#Sending from your own domain

By default, email comes from a Restro address. To send from your own — orders@yourrestaurant.com — enter the address in Notifications, then add the DNS records Restro generates at your registrar.

Restro checks the records and shows the status as pending, verified, or failed. Until it verifies, email keeps going out from the default sender rather than failing.

Sending from your own domain markedly improves deliverability, and it is the difference between a confirmation landing in the inbox and landing in spam.

Did this page miss something? Tell us.

Back to top