AI assistant · N4 Executable plan
Recovery Flow Builder for Unhappy Restaurant Guests
Builds the flow your restaurant uses to win back a guest who left angry: who enters and who does not, the private message sent only once, what gets replaced at recipe cost with its monthly ceiling, and the fix that stays in the kitchen.
N4Executable plan
A plan with owners, deadlines and the metric you review. Not advice: an agenda someone can execute on Monday.
◆ This assistant 23 of the 164 published assistants are at this levelIs this for you?
What it does and what you get
- Most restaurants answer the complaint in public and stop there: the guest never returns and nobody notices.
- This assistant takes the job that starts where the public answer ends —the move to private, with a name and a role— and turns it into a flow with rules that bite: who enters (only the guest who left a contact route), what gets replaced and what does not, with the gesture costed at recipe cost instead of menu price, and a single attempt with its window, because pushing someone who stays quiet stops being service.
- It ends where a complaint really closes, which is inside: a fix with an owner and a date, and the rule that a theme repeated three times freezes replacements.
What you end up with
Five chained deliverables: each case with its entry verdict, the replacement rule with recipe cost and monthly ceiling, the private message ready to send on every route, the clock of the single attempt, and the 60-day board with the in-house fix.
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: "Five guests left angry this month: two two-star reviews, a sancocho sent back, a delivery that arrived cold and a table complaint on Saturday. I answered the two reviews in public and that was that."
Of the five, four have somewhere to write to and one does not. That one is not a gap in the method: it is the rule working.
| Case | When and where | Checkable fact | Contact route | Verdict |
|---|---|---|---|---|
| Cold Trucha al ajillo, 2★ on the search profile | Thursday 1:40 p.m., Laureles location | Docket 4187: 19 minutes between the pass and the table, in the middle of the lunch rush | Profile private message | Enters |
| Sancocho de tres carnes sent back | Sunday 12:50 p.m., dining room | The server logged the return on the docket but not the cause; paid by card and left an email for the invoice | Enters | |
| Own-delivery order arrived cold | Tuesday 8:10 p.m. | 52 minutes on the road against the 35 the house promises | Order WhatsApp | Enters |
| 2★ on the delivery platform, "the portion is not the one in the photo" | Saturday 1:20 p.m. | No exit weight recorded; there is nothing to check it against | Platform chat, which closes at 72 hours | Enters, short window |
| Table complaint, Saturday 8:30 p.m. | Dining room, El Poblado location | The plate left cold; the server settled it with a complimentary lemonade and nobody took a detail | None | Does not enter |
The fifth one stays out because there is no CRM and no dining-room guest list: from the room you can only recover whoever left a detail, and nobody asked this one for it. The case is not lost, it moves whole into block ⑤ and leaves the flow here.
Two findings the count puts on the table: two of the four that enter broke inside the strong slots of the house —Tuesday-to-Friday lunch and Sunday midday—, which is where most people see it; and the platform one has no checkable fact because nobody weighs the plate at dispatch. Illustrative figures, built from the data you gave.
The gesture is costed at recipe cost and never at menu price. The difference between replacing and giving away fits in one column.
| Case | What is admitted | What gets replaced | Recipe cost | What is NOT offered |
|---|---|---|---|---|
| Cold trout | The plate left cold and was charged in full | The Trucha al ajillo, served at the table on the next visit | 16,100 COP | No discount on the check, no courtesy for companions |
| Sancocho sent back | It was returned and it was charged | The Sancocho de tres carnes, with no expiry date | 11,700 COP | No drinks, no complimentary dessert |
| Cold delivery | 52 minutes against the 35 promised | The whole order, Bandeja de la casa and Sancocho, plus packaging | 27,500 COP | Not the delivery fee in cash |
| Platform portion | No exit weight: the fact is not admitted | Nothing. The recipe portion is explained and weighing starts today | 0 COP | No replacement, no voucher for an opinion nobody can verify |
Monthly ceiling: 5 replacements per location, 10 across both, or 150,000 COP of recipe cost, whichever comes first. Against 4,458 tickets in the month that is 0.22% of the checks. These three cases take 55,300 COP of the ceiling: room for seven more.
SUPUESTO: the house has no written food cost ceiling for what it replaces, so the 34% its own menu averages is used here and the replacement is asked not to go past it. This is not an industry yardstick: it is yours, taken from your own recipes. If you set the ceiling at 30%, the trout misses it by 5 points and you would replace with another dish or fix its price first. Argue with the assumption before signing off on the monthly ceiling.
A finding that is not a failure of the offer. The Trucha al ajillo sells at 46,000 COP and its recipe costs 16,100: 35% food cost, one point above the menu average. Replacing it is still the right call, but the problem there is not the offer, it is the menu price. The Sancocho lands at 30.8% and the Bandeja at 31.9%; both fit, and the contribution margin a full month of replacements takes away still sits under the ceiling. Illustrative figures.
One per route, signed with a name and a role, sent without editing anything beyond the name and the dish.
Profile private message (cold trout, within 24 hours of the public answer):
Good afternoon, don Julián. I am writing separately: I am Marcela Ruiz, floor manager of Sazón de Origen in Laureles. Your trout left the pass on Thursday at 1:21 and reached your table at 1:40, and that is on us, not on the day. From Monday no trout leaves without going under the heat lamp and the hot-section chef answers for the time at the pass. I have the Trucha al ajillo held for you whenever you want to come back; tell me a day and I will keep it.
Email (sancocho sent back):
Doña Elvira, this is Marcela Ruiz, floor manager. On Sunday we charged you for a sancocho you sent back, and that is not how it is done. The Sancocho de tres carnes stays in your name, with no expiry. If you tell me what went wrong with the plate —the meat, the salt, the temperature— I will take it to Monday's kitchen meeting with your name on it.
WhatsApp (cold delivery):
Don Andrés, this is Marcela Ruiz, from Sazón de Origen. Your Tuesday order took 52 minutes and we promise 35. I am replacing the whole order, bandeja and sancocho, on the day you ask for it. Does this week work?
The line that never gets written, in any of the three: "we will give you 20% off your next check". A percentage on something not yet bought replaces nothing, and it does teach the price of a complaint.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 3 of 5 parts. Behind the wall are the two pieces that actually get executed. The clock of the single attempt, channel by channel: when the message goes out, who signs it with name and job title, how long the window lasts —5 days on the profile and email, 3 on delivery WhatsApp, 72 hours in the platform chat— and what gets written when nobody answers, with the Monday 9:00 a.m. cut where every case falls into one of three boxes and the silent ones are closed for good. And the in-house fix with the 60-day board: theme, times in 30 days, fix, owner, date and the figure that closes it, plus the rule that freezes the cold-plate replacement until twenty dockets in a row leave under six minutes, and the row that forces every replacement to be logged where waste is logged.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 12 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.1.12026-08-26The body stops contradicting the answer ladder. It used to say «do not move on until it arrives», the very order the ladder was born to replace: the assistant asked the owner for what the owner does not have and stalled. It now says what the house doctrine says — ask one at a time, and if they do not know, continue with a marked assumption. FORMAT OF THE RESULT was not touched, so the example still corresponds and its seal moves up with the card.v1.1.02026-08-25Body rewritten to pay down duelo debt: it scored 84.7 out of 90.0, the closest to the threshold in the whole batch and the one failing on a single count. The `lexico` signal read ZERO: a flow that costs dishes, watches food cost and decides replacements never said «food cost», «standard recipe», «contribution margin», «waste» or «portioning» — it said «recipe cost» and «what gets replaced», which is correct but is not the trade's vocabulary. Those terms now appear where they belong, and two missing cautions are added. The hard-coded figure the card had carried since its first version is also REMOVED: the «32% ceiling on that dish» was written as universal truth, and the ceiling is now measured against contribution margin with a SUPUESTO line declaring where the yardstick comes from and what changes if the real one differs. Step 6 forces the replaced plate to be logged where waste is logged, so the replacement does not vanish from food cost without a trace. The seven labels now carry `##` and the traps of the trade are distributed across ROLE, METHOD and BEFORE YOU DELIVER. Rises to 95.8.v1.0.02026-08-25The assistant is born.Same method, another variant
Inside the app this is a single control: you press it and the assistant reframes itself, including the variants that don't appear here because they don't have their own page yet.
More assistants in this category
Writes the messages your restaurant answers automatically -welcome, booking, delivery, opening hours, address,…
N4 · Executable planWrites the replies to four and five-star reviews: sorts them by what each one brings, hands out a long reply o…
N4 · Executable planWrites the protocol for the first hours when something turns against you online: three levels with countable c…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.