Act while context is fresh
Table and restaurant are stored with the comment.
Guest feedback
A rating and a written comment, tied to the table and outlet. This is service recovery, not another anonymous survey form.
Guest rating: 1–5, then continue — the same step they use at the table.
Guests scan, rate 1–5, and leave a required comment. Staff see the outlet and table so they know where to recover the experience.
The table token identifies the restaurant and table.
A score plus written feedback (optional guest name).
In-app bell and live toast for Hotel Admins, F&B or Front Office managers in scope, and the assigned Outlet Manager.
Read comments in the dashboard and watch negative-feedback volume on analytics.
Table and restaurant are stored with the comment.
Routine guest alerts are the in-app bell and a live toast while the team is signed in.
Open the same visit later in Reviews and Feedback, with outlet and table still attached.
The same flow works for a hotel restaurant or a standalone dine-in outlet under the hotel tenant.
Rating emojis, then continue. The comment is written on the next step.
Hotel Admins of that hotel, the Outlet Manager assigned to that outlet, and department managers whose service line covers that outlet type (F&B Manager for restaurants and in-room dining; Front Office Manager for front office).
A 1–5 rating, a written comment, and an optional name.
No. Routine alerts are the in-app bell plus a live toast. Email is used for account messages such as invitations and password reset.
One bell item. Rating-only is stored as a review event. Rating then private comment is stored as feedback, not two competing alerts.
In the staff app Reviews and Feedback lists, scoped to the hotel or the assigned outlet. Analytics also shows negative-feedback volume, rating distribution, and recent trends.