Automated Revel Systems Online Order Routing
Every few minutes, WebRun checks Revel Systems for newly placed online orders, reads the order type and requested location, routes each ticket to the right kitchen station or fulfillment queue, and posts a Slack alert so your team is never caught off guard by a missed online order.
How do I automatically route Revel Systems online orders to the right kitchen station?
WebRun checks Revel Systems every few minutes for new online orders, reads each ticket's type and requested time, determines the correct kitchen station or location using your routing rules, and posts an instant Slack alert so your team is never caught off guard by a missed or misrouted online order.
- No online order missed or delayed due to manual monitoring
- Kitchen team alerted within minutes of a new ticket arriving
- Urgent orders flagged automatically when the requested time is close
Built for QSR operators · restaurant managers · multi-location food-service owners · ghost kitchen operators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
manage.revelsystems.comin a real browser with your saved login - no setup, no API keys. -
1
Revel Systems - detect new online orders and read routing details
revelsystems.com
WebRun opens Revel Systems to detect new online orders and read routing details. - Open Revel Systems Management Console and check the Online Ordering queue for new tickets
- Read order type (delivery, pickup, dine-in), requested time, and line items for each new order
- Determine the correct kitchen station or location based on your routing rules and the order type
Done when Every new online order has a routing decision with the assigned station and order details captured.
-
2
Slack - alert the team with order details and assigned station
slack.com
WebRun opens Slack to alert the team with order details and assigned station. - Post an alert to the kitchen or ops Slack channel with the order number, type, items, and assigned station
- Flag any order with a requested time within the next 15 minutes as urgent
- Confirm no duplicate alerts are sent for the same order across successive runs
Done when Every new online order has a corresponding Slack alert with routing details and urgency flag if needed.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun modify the order or status in Revel?
No. WebRun reads the order queue and routes the alert but does not change the order status in Revel. All status updates remain with your team or the Revel system itself.
Can routing rules vary by order type or time of day?
Yes. You configure the routing logic when setting up the run: delivery orders go to one channel, pickup orders to another, and the urgency flag threshold is yours to set.
What happens if a new order comes in while a previous run is still active?
WebRun tracks which orders have already been alerted so each ticket gets exactly one Slack notification regardless of how frequently it polls.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.