Collection
Collection robots: dishes and orders back the other way
A collection robot carries used dishes back to the wash and brings placed orders in from the pass. Hybot models both as first-class task types, COLLECT_DISHES and GET_ORDER, queued and assigned by the same scheduler as deliveries so the return leg is never left to whoever happens to be free.
| Task type | Assignment |
|---|---|
| COLLECT_DISHES | Automatic, re-scored every two seconds by priority, distance and battery |
| GET_ORDER | Automatic, re-scored every two seconds by priority, distance and battery |
How it works, specifically
The return leg is a real task, not a favour
COLLECT_DISHES and GET_ORDER enter the same queue as deliveries and are scored by the same scheduler, so clearing does not depend on someone noticing.
Guests can start the task themselves
From the table QR page a guest can ask for dishes to be collected. The request becomes an ordinary runtime task with its source recorded as the customer.
Staff see exactly what was asked for
Guest requests surface as a customer-requests chip in the staff header with approve, reject, done and cancel, plus configurable attention pop-ups per device class.
One open request per table
A table can hold one open robot request and one open waiter request at a time, which stops the queue filling with duplicates of the same ask.
Common questions
- Can a guest ask for their table to be cleared?
- Yes. The table QR page offers calling a robot to collect dishes. The request becomes a normal task in the queue, tagged as coming from the customer, and staff can approve or reject it if an approval queue is enabled.
- Does collection compete with delivery for robots?
- They share one queue and one scheduler. Priority is part of the scoring, so an urgent delivery outranks a clearing run without anyone having to hold robots back by hand.
- What stops one table asking ten times?
- A table can hold only one open robot request and one open waiter request at a time, and venues can additionally require staff approval or restrict requests to the venue's own network.