AI assistant · N5 Complete system
Community Manager Operations Manual Builder for Restaurants
The document that outlives whoever holds the job: where the access lives and who custodies it, how the house speaks, what gets approved and within how many hours, what to answer on a public complaint and what never gets posted — written so that whoever starts on Monday can operate without calling anyone.
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 day your social media person quits, three unwritten things leave with them: the passwords, the judgment and the photo archive.
- This assistant doesn't build calendars or split the week — the daily and weekly plans do that —: it writes the manual a replacement can run tomorrow.
- Indexed chapters with a named owner, access with a custodian and a revocation route, the house voice with real examples, the approval flow with deadlines in hours, the public-complaint protocol with its escalation and the short list of what never gets posted.
- Plus the one-page card people actually read and the manual's own version log.
What you end up with
The chaptered manual, each chapter carrying its table of What gets done · How it's done here · Who answers · When; the one-page card to tape next to the computer, with access and custodians, escalation phone numbers, what never gets posted and the daily checklist; and the manual's own version log with its quarterly review already booked.
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: «We're Sazon de Origen, contemporary Colombian cooking in Medellín: two locations, 24 people and a 48.000 COP average check. The woman who ran Instagram and WhatsApp quit on Friday and everything left with her: nobody knows the password to the account's email, where the photos are, or what to answer when someone complains about a delivery that arrived cold. Someone new starts Monday, and I'm fighting to take operating margin from 8% to 14% without touching menu prices: I need them to operate without calling me every 20 minutes.»
| # | Chapter | What it settles | Owner | Last review |
|---|---|---|---|---|
| 1 | Access and custody | Who holds which account and how it's granted or pulled | Laureles manager | Aug 19, 2026 |
| 2 | The voice of Sazon de Origen | How the house speaks —warm, unpretentious— and which words are out | Owner | Aug 19, 2026 |
| 3 | Approval and deadlines | What goes out alone and what waits for sign-off | Owner | Aug 19, 2026 |
| 4 | Material and archive | Where the photos of the house Bandeja, the three-meat Sancocho and the garlic Trout live, and how a file is named | Envigado manager | Aug 19, 2026 |
| 5 | Complaints and escalation | The delivery that arrived cold, the Sunday line, and who gets called | Delivery lead | Aug 19, 2026 |
| 6 | What never gets posted | The short list, no exceptions | Owner | Aug 19, 2026 |
Every chapter fits on one page and opens with the same line: «If you just arrived, read this first». Figures are illustrative: the manual closes once both managers confirm the six accesses across the two locations.
| Account or channel | Who custodies it | How it's requested | How it's revoked |
|---|---|---|---|
| Instagram @sazondeorigen | Laureles manager | Invite from the account panel, with the incoming person's email | Access pulled from the same panel on their last day |
| WhatsApp Business (delivery line) | Delivery lead | The number is added as a linked device | That device's session is closed within 24 hours |
| Account email | The owner, and only the owner | Not shared: the owner runs whatever step is needed | Not applicable, it never leaves their hands |
| Google listings for both locations | Envigado manager | Email invite as administrator | Removed from each listing, same day |
| Delivery platform panel | Delivery lead | Their own user with their own email, never the owner's | The user is deactivated; the owner's password is untouched |
| Photo bank | Laureles manager | Shared cloud folder, edit permission | Permission revoked, the folder is not deleted |
The rule holding the chapter up: no password gets written here, and none travels through the team chat. A password that passed through a WhatsApp group has already left the business, and no resignation brings it back. When someone leaves, the chapter runs within the same shift: six rows, six revocations, 20 minutes.
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 sits the **one-page card** —the six accesses with custodians, escalation phones in order, the reply window in hours, the never-post list and the daily checklist—, the COP arithmetic that explains why the 30% discount landed on that list, the three-move public complaint protocol and the version log that forces a date and a signature every quarter.
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 City and country. 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-27It now declares the «See photos» capability, so the AI selector warns before you open the prompt in one that lacks it, instead of letting you find out mid-task.v1.1.02026-08-20Rooting. The manual was written on concepts —accounts, channels, what we show, the team— and only tone carried the house data, so once personalised it was still any restaurant's manual. Now the access chapter opens one row per declared network and sales channel and outside those lists there is no manual, the voice examples are built on the star dishes, every chapter defends the promise, and the final test is whether anyone on the team could run it tomorrow without calling. Role, method, context block and example stay untouched.v1.0.02026-08-19Initial version. Born in the August 2026 marketing batch to fill the gap the plans leave: daily and weekly split the work, neither teaches how to do it. This one writes down what stays when the person leaves — access with custodians, voice with examples, approval deadlines and a complaint protocol —, plus the one-page card that is the only piece anyone actually reads.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
The job description that gets signed, not the task list that gets forgotten: what belongs to the community man…
N5 · Complete systemThe board that rules on whether the social media role is paying for itself: every indicator with a written for…
N5 · Complete systemA comment isn't answered for the person who wrote it: it's answered for the people reading. This writes the th…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
