Before service
Booking rules, deposit chases, opening hours, menus and team roles are checked before the rush starts.
Help should understand the room: calls, covers, deposits, POS, stock notes, supplier pressure and the timing of service.
Launch calm.
We help map what Elyx should learn first, which loops should run first and what the team should expect on day one.
Payments, bookings and POS stay tied to the support conversation.
How support works
If a workflow touches guests, money or service pressure, support treats it as operational work, not a generic software ticket.
Booking rules, deposit chases, opening hours, menus and team roles are checked before the rush starts.
Call handling, missed demand, payment links and urgent restaurant signals get routed with context attached.
Receipts, call summaries, stock notes, supplier pressure and recovery signals land in the same support conversation.
Trust and control
We help restaurants decide which loops Elyx can run, which rules apply, and where a manager should stay in control.
Autonomy rules. Source records. Receipts.