AI assistant · N5 Complete system
Service Error Recovery Procedure Builder for Restaurants
Pick at the top what went wrong —a kitchen error, a service error, a billing error, a delay, a delivery or a booking— and out comes the floor procedure for THAT moment: the four moves anyone can make without calling the boss, the clock in minutes, who faces the guest, the phrases in the house tone, the list of what is NOT done and the escalation line.
N5Complete system
Several chained pieces you install and operate over time, with their review cadence. It changes how the business runs, not one decision.
◆ This assistant 110 of the 164 published assistants are at this levelIs this for you?
What it does and what you get
- The mistake already happened; whether that table comes back is decided by whoever is standing in front of it during the first two minutes — and that person is almost never the owner.
- A twenty-page manual is useless on the floor: nobody reads it with an upset guest in front of them.
- This assistant builds the SHORT procedure — four moves, ready-made lines, the list of what is not done and who each thing goes to — and adapts it to how your house serves: at the table the shift lead shows their face before dessert, at the counter you solve it in one minute because the line will not wait, and on delivery the apology travels by WhatsApp before the review arrives first.
- The recovery board measures the system; THIS procedure trains the hand.
What you end up with
The floor procedure in four moves plus the leader's fifth, adapted to your service style; the frequent-mistakes table with response, line and compensation; the phrase bank in your house's form of address with the forbidden lines next to it; the digital script with the A/B/C compensation menu; what is NOT done; the three-step ladder with its autonomy panel — and the house graphic document (six to eight A4 pages, signed 'Creado por MASTERESTAURANT') with the printable pass card, readable on a phone.
EXAMPLE This is what you getAn example built with Sazón de Origen, the house's fictional restaurant.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: “I run a dining room plus delivery. On Friday a new server argued with a table over a wrong dish, and yesterday an incomplete order ended up on Instagram. Everyone answers as best they can. I want a short procedure anyone can apply, not a manual.”
| Move | In the dining room | On delivery |
|---|---|---|
| 1 · Listen all the way | No interrupting, no defending, right beside the table | Read the whole message before replying |
| 2 · Apologize without excuses | «You're right, this should not have happened» — the kitchen does not travel to the guest | In writing within 10 minutes, with your own name |
| 3 · Resolve on the spot | Remake the dish now; the boss stops by before dessert | Replacement on the way or on the next order, guest's choice |
| 4 · Report and log | The boss hears it from you, not from the review | Photo of the order ticket and a log entry before closing the shift |
The floor rule: move 3 asks no permission below the ceiling. Remaking a wrong dish costs less than arguing about it, and the argument gets paid for in the review that everyone comparing restaurants reads.
| Mistake | Done NOW | The line | Compensation | Does it escalate? |
|---|---|---|---|---|
| Wrong or cold dish | Pulled and remade first in the pass queue | «I'll change it right now; the new one goes out first» | A: the dish, with its waste absorbed | No |
| Long wait in the room | Give the real time and offer a house drink | «It'll be 15 min longer than I told you; this lemonade is on the house» | A: a drink | If repeated: shift leader |
| Incomplete delivery order ticket | Replacement on the way or a discount on the next order | «An item was missing and that's our error: shall we send it now or take it off your next order?» | B: item and delivery | Only if the guest asks |
| Wrong charge | Corrected in front of the guest, no justifying | «You're right, here it is corrected; thank you for telling me» | None | If a refund: shift leader |
SUPUESTO: no «normal» industry complaint percentage is hard-coded here, because it shifts by format and by country. The first rung's autonomy ceiling is set as a multiple of the average ticket you declare, and it says so. If your real ticket were half the assumption, the ceiling drops and the incomplete delivery order climbs a rung.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 2 of 3 parts. Behind the wall are **the house graphic document with the pass card** and **the escalation ladder with the A/B/C compensation menu** — plus the two figures from the log, read at 30 days, that say whether the procedure is alive or ended up in a drawer.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 8 of the 23 fields in «My Restaurant», among them Restaurant name, Business type and Active sales channels. It does not ask out of curiosity: these are what make the answer speak about YOUR scale instead of an industry average — the same calculation on a business of another size returns a number you cannot decide with. You fill them once and they apply across the library, so the second assistant you open already starts with them in place. Whatever you leave blank, the assistant asks for one thing at a time instead of inventing it, and says so before answering, so you know what it is working from.
Always up to date
Every assistant carries a visible version and date. When an AI changes how it works, the assistant's version goes up and you see what changed.
v1.3.02026-08-27It absorbs the other six protocol cards in c31 —kitchen, service and billing errors, delays, deliveries and bookings— plus the service recovery protocol. They are the same floor procedure with a different incident in front: the four moves do not change; the clock, who faces the guest, the cap on what is replaced without asking and how the apology travels do. That now lives in the selector's per-option rules.v1.2.02026-08-25Body rewritten to pay down duelo debt: it scored 68.8 out of 90.0 with two signals at ZERO. `cifras`, because a procedure played on the clock —«under ten seconds», «reply fast», «before dessert»— had all its times spelled out in words, and a figure in letters is not a figure: the clock is now stated as 10 seconds, 1 min, 10 minutes, 15 min and 30 days, which is what the team can actually meet. And `lexico`, because the card costed compensations without ever naming contribution margin, waste, average ticket or the order ticket, which is what the trade calls what it was already doing. `arraigo` also measured 0 fields in the work sections: the eight «fields» were declared in YOUR RESTAURANT while the TASK spoke of «my house» and «my mode» without naming them again; the TASK is now six numbered steps that tie the autonomy ceiling to «ticket_promedio» and the service mode to «canales_venta». The SUPUESTO: line is added for the complaint percentage and the cost of a compensation, which the house does not hard-code. Rises to 94.2.v1.0.02026-08-18Initial version, commissioned directly by Diego (2026-08-18): the FLOOR procedure that was missing next to the board. Its written boundary: the board (MPV-0925) measures the system — capture, minutes, costs, return —; THIS procedure trains the hand at the moment of the mistake, short and graphic, adapted to the service style already living in My Restaurant (business type + channels). Money caps are not duplicated: they are inherited from the board's scale.v1.1.02026-08-18Second round from Diego's direct review ('too basic and incomplete […] more powerful and expert', with his graphic-documents MASTER PROMPT as the bar): the role rises to world-class consultant with the real frameworks (service recovery paradox, repair and surprise, capped empowerment), the formal/casual address, the A/B/C compensation menu with costs, the digital script and the filter question come in, and the deliverable grows to the house GRAPHIC DOCUMENT (6-8 A4 pages) with the pass card. The signature becomes 'Creado por MASTERESTAURANT' — no personal names. The visual system does not travel pasted here: it lives as a single dato (datos/documentos_graficos.json) attached by the runtime — fixing it once fixes it for every builder ficha.Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
