Diner feedback for catering sites
Hear every diner,at every location.
A code on the table opens a short survey on the diner's own phone. NCMS turns what they say into ratings by location, by meal and by question — for the people who can fix it.
The problem
Most feedback never reaches the kitchen.
- Comment cards, read once a month
- A complaint with no location, no meal, no time
- One bad day taken for a trend — or a real trend nobody sees
With NCMS, every answer arrives as a record.
| Location | Meal | Question | Rating | Reason | Time |
|---|---|---|---|---|---|
| Riyadh · North Camp | Lunch | How would you rate the temperature of your food? | 2 | Food was cold | 13:12 |
How it works
From the table to the report, in six steps.
Replaced — the old card no longer opens
A code on every table
Each location gets its own QR code. Print it on the table card; replace it and the old one stops working.
How was your meal?
How would you rate the portion size?
A survey for this meal
It opens in the browser for whichever meal is being served. One tap per question, on five faces.
What went wrong?
- Food was cold
- Queue was too long
- Portion too small
- Not enough choice
A low rating says why
Rate a question low and the survey asks what went wrong — so a complaint arrives already sorted.
- Location
- Riyadh · North Camp
- Meal
- Lunch
- Rating
- 2
- Reason
- Food was cold
- Time
- 13:12
Saved · read-only
Written once, kept as given
Each answer is stored with its location, meal and time, and cannot be edited afterwards.
Period average
4.21
Counted, per location and meal
Averages, trends and the reasons behind low ratings — measured against the client's own benchmark.
Lunch is under the benchmark
Riyadh · North Camp · last 14 days · 212 answers
Weekly digest · Monday 07:00Raised with the right person
A meal under the benchmark for 14 days, or a card silent for 3, opens an issue. Camp bosses can get a digest every Monday at 07:00.
The console
Everything a client needs to see, in one place.
The figure that matters
The period average against the client's benchmark, beside the number of answers behind it.
The trend, by meal
Breakfast, lunch and dinner as separate lines — a bad lunch never hides inside a good day.
The reasons behind it
What diners picked when they rated low, counted, so the fix is obvious.
Every location, and a file to send
Each location side by side, and the report as CSV, XLSX or PDF — in English or Arabic.
What changes
What a client gets from a code on a table.
- Feedback
Diners rate in seconds, at the table, without giving their name.
- Data
Every answer is tied to a location, a meal, a question and a time.
- Insight
Averages and trends against the benchmark — and why ratings dropped.
- Action
Issues and weekly digests put the problem in front of the person responsible.
Who it's for
One platform. Four people.
NCMS
Sets up each client: its locations, its camp bosses and the questions asked at every meal.
Company manager
Follows their own company — its locations, its results, its reports. No other client is visible.
Camp boss
Looks after the locations assigned to them, with a mobile app on the way to the stores.
Diner
Scans, answers, leaves. No account, no name, no download.
Built the way catering runs
- Arabic and English throughout — the Arabic PDF is real text, not a picture.
- Each client's data is kept apart inside the database itself.
- An answer cannot be changed once it is given.
- Questions are set per location and per meal.
- Ratings are faces a diner understands at a glance, not stars.
Every meal has something to say.Start hearing it.
The NCMS team sets up each client — locations, camp bosses and questions. Already a client? Your console is one sign-in away.