ข้ามไปยังเนื้อหา
Back to BiteTheMenu Site

When your menu changes

เนื้อหานี้ยังไม่มีในภาษาของคุณ

Your menu moves and nobody tells the floor. A waiter sells a dish the kitchen took off last Tuesday. This watches your dishes and, when enough of them change, puts a note in front of you with questions your team could be taught.

The rule

Nothing an AI writes reaches your team until you read it. Twice: you approve the questions, then you publish the module they go into.

How it works

  1. We watch your dishes. When three or more change, a note appears under Training → Review queue listing what moved — say Margherita new, Marinara taken off.
  2. Press Write the questions. Four multiple-choice questions are written from those dishes.
  3. Read them. Drop any you don’t like.
  4. Press Approve into a new module. That makes a draft course called something like Menu update — August 26.
  5. Open it, publish it, and put your floor team on it like any other course.

Prefer them ready and waiting? Tick Write the questions for me automatically and step 2 happens overnight. It’s off until you turn it on, because writing questions uses a little of your credit each time.

Good to know

  • A published course can’t take new questions. Results already recorded point at the questions people actually answered, so a menu update becomes a short new module instead of being bolted onto an old one.
  • A question about a dish you’ve since deleted is left out of the batch and marked on screen, so you never publish a question about a plate nobody makes.
  • Allergen changes don’t trigger this. Only names, descriptions, prices, sections and dishes coming or going. Change an allergen and teach it yourself.
  • The first check is a quiet one. A venue new to this gets no note about edits made before it was switched on — otherwise you’d open a queue full of history.
  • You need permission to edit training courses to see this screen at all.