AI assistant · N5 Complete system
WhatsApp Bot Implanter for Restaurants
The tool is already built and you can download it: what's missing is making it YOURS. This assistant produces the verdict on whether it pays, the inventory of what your customers ask with the cut between what a machine answers and what a person does, your written data files —menu, hours, zones, voice with its prohibitions— and the brake on what the bot never promises.
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
- A WhatsApp bot is neither bought ready-made nor written from scratch: the hard part —how it connects, how the number doesn't get blocked, how it doesn't invent a price— is already solved and measured inside the Universal WhatsApp Bot folder you download from your library, with its own specification inside.
- What no universal folder can bring is your menu, your Sunday hours, your delivery zones, your way of speaking and your prohibitions.
- That's what this assistant does, and in the right order: first it tells you with figures whether it pays —because a tool that doesn't pay gets switched off in two months—, then it pulls the real list of what your customers ask and cuts it in three (what's answered by reading a value, what needs judgement, and what a machine doesn't answer), and only then writes your data files ready to paste.
- Whatever you haven't told it gets marked PENDING, never filled in: invented data about your business is something it will say to a customer of yours.
What you end up with
The verdict with your figures and the sentence on whether it pays; the question inventory cut in three —no model, with model, to a person— with the data each one needs; your data files written and ready to paste, with the PENDING items marked; the brake on what the bot never promises with its handover line and its hours; and the switch-on order with what can be checked at each step, its owner with name and job title, the indicator with its numeric target and the monthly routine with its switch-off rule.
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: «About 60 messages a day come in across Instagram and WhatsApp. We answer when we can; at the lunch peak nearly all of them drop. I know we're losing delivery orders but I don't know how many.»
| Messages a day | 60 |
| Unanswered at the peak (12:00–14:30) | ~26 |
| Of those, asking a price or whether you deliver | 19 |
| Average delivery ticket | $38,000 |
| If 1 in 4 is recovered | ~$5.7M/month |
| Bot cost (machine + channel + model) | ~$310,000/month |
It pays for itself in the first week, and not because of the bot: because of the nineteen questions nobody answers today that are answered by READING a value. Caveat: the figure above comes from your 60 messages and my peak count — if the real count is half, it still pays.
| Question | Channel | Times/wk | How it gets answered | Data needed |
|---|---|---|---|---|
| «how much is the platter?» | delivery | 84 | NO MODEL | menu with prices |
| «do you deliver to Laureles?» | delivery | 61 | NO MODEL | zones with cost and time |
| «how late are you open?» | direct | 38 | NO MODEL | hours with the Sunday exception |
| «where are you?» | direct | 22 | NO MODEL | address and landmark |
| «anything without pork?» | delivery | 14 | MODEL | menu with descriptions |
| «can you replace an order that arrived cold?» | delivery | 6 | TO A PERSON | — |
The cut: 4 out of 6 need no model. Those cannot invent a price because they do not think: they read. And the first two rows are 65 % of the week's volume: that is the 20 % that must be perfect before switching on.
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 five written data files**, **the brake with its handover line** and **the switch-on with owner, indicator and a sixty-day switch-off rule**.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 13 of the 23 fields in «My Restaurant», among them Restaurant name, Business type and Cuisine or concept. 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-27The kit this card delivers moved from 1.46.4 to 1.47.1 —Diego published the Universal Bot the same day— and the card still quoted the old version in both languages. Doc 35 §2.5 has asked for this since it was written: the card states which universal version it ships, so a client coming back in six months knows whether theirs is current. Nobody checked it. Now `_QA/prueba_kits_declarados.py` compares the quoted seal against the package manifest's `version_kit` and fails when they disagree.v1.1.02026-08-27My error, caught by the duel gate: it was born at 60.1 against a threshold of 90 —zero figures with a unit and zero trade terms in the body—, an assistant that talked about a bot without talking like a restaurant. Now the business yardstick carries its percentage, the arithmetic its three lines and its 1.5 %-of-sales ceiling, the inventory is sorted by frequency and sales channel, and the bot's reply shapes the sales mix instead of pasting the whole menu.v1.0.02026-08-26Initial version, and the catalogue's first UNIVERSAL TOOL card: it does not explain how a bot is built —that is already solved and measured inside the downloadable folder, with its own specification— it makes it THIS restaurant's. Born together with the Universal WhatsApp Bot downloadable kit (34 files, distilled from version 1.46.4 of the origin engine), served through the same plan-gated door as the other kits.More assistants in this category
Not one cycle: the whole ring. Which decisions your house takes today without a figure, which cycles feed them…
N5 · Complete systemThe board of boards: the census of the cells you fill by hand, which ones can fill THEMSELVES with what you al…
N5 · Complete systemYou bring a routine you already do by hand —reviewing the month's numbers, tidying up what came out of the mee…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.