AI assistant · N5 Complete system
Weekly Community Manager Plan Builder for Restaurants
Treats the social week as a production cycle with measured load: every block with its day, its length in minutes and its owner, the shooting batch protected in a single session, a buffer that always gets used and a 20-minute huddle that writes down what will NOT be done this week.
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
- Most restaurants don't fail for lack of ideas: they fail because the content load was never weighed against the hours the team actually has.
- So filming breaks into five scraps under five different lights, the numbers block is the first to fall when service gets heavy, and Monday opens by arguing about last Monday.
- This assistant does not run the shift — the daily plan does that: it splits the week.
- You get the block grid with day, length and a named owner, the batch shooting sheet, the rule that decides what gives way when an event lands on top, and the numeric criterion that separates a week fulfilled from a week merely survived.
What you end up with
The week's grid with its six columns — day, block, length in minutes, owner with a job title, deliverable and the daypart or sales channel it feeds —; the batch shooting sheet in a single row; the rescheduling rule with the month's commercial dates already written in; and the week's cut with the percentage of blocks executed and a one-line verdict.
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 and 24 people. Everyone does the content and nobody does it: I film one video on Tuesday between orders, another on Thursday, and the pieces don't match. Strong lunch runs Tuesday to Friday from 12:00 to 14:30 and Sunday at noon; Monday drops. Across both locations I can free up 5 hours 30 minutes a week, and this year I have to take the operating margin from 8% to 14% without touching menu prices. Tell me what happens each day and what I stop doing.»
| Day | Block | Length | Owner | Block deliverable | Daypart or channel it feeds |
|---|---|---|---|---|---|
| Monday | Weekly huddle | 20 min | Owner + location head | 3-line minutes and deferred list | The whole cycle |
| Monday | Batch production | 90 min | Location cook + manager | 16 photos and 4 videos for the week | The slow Monday and Tuesday-to-Friday lunch |
| Tuesday | Scheduling | 40 min | Manager | 7 posts loaded at their exact hour | Lunch from 12:00 to 14:30 |
| Wednesday | Interaction | 25 min | Afternoon-shift cashier | WhatsApp messages and comments answered | Own delivery |
| Thursday | Buffer | 60 min | Deliberately unassigned | Whatever fell through | Whichever one needs it |
| Friday | Interaction | 25 min | Afternoon-shift cashier | Messages answered before 11:30 | Friday lunch |
| Sunday | Number reading | 30 min | Manager | The week's cut | Decides Monday's plan |
Why the batch lands on Monday and not Sunday: Monday is the only day with no declared strong lunch, the kitchen can plate the Bandeja de la casa, the Sancocho de tres carnes and the Trucha al ajillo without stalling orders, and Sunday noon runs full. 40 minutes stay unassigned on purpose: a plan at 100% of capacity breaks on the first odd day. Figures are illustrative; the real hours come from your week.
Batch shooting sheet — Monday, 3:00 p.m., 90 minutes, Laureles location. Planned shots: 16 photos (the Bandeja de la casa complete before it leaves for the table, the Sancocho de tres carnes served in the clay pot, the Trucha al ajillo coming out of the pan) and 4 videos of 20 seconds (the meat being cut, the rice landing on the plate, the in-house courier closing the thermal bag, the 12:15 line). Cooking: the location cook. On camera: the location head. What is NOT filmed this week gets written down: the Sunday menu waits for the next batch.
| What landed on top | Which block gives way | Which block freezes |
|---|---|---|
| Corporate lunch for 60 on Monday | The batch moves to Tuesday 3:00 p.m., identical | Monday's huddle and Sunday's reading |
| Commercial date: Mother's Day, Sunday noon | Friday's 25 interaction minutes go to scheduling | The batch is untouched |
| The delivery marketplace goes down on a Thursday | The buffer block is spent answering on WhatsApp | The batch and the huddle |
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 week's cut**: the planned-against-executed table block by block, the numeric criterion written BEFORE measuring — 80% of blocks and the batch intact — and the one-line verdict that decides whether the week was fulfilled, survived or lost.
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 card declared the house data at the top and worked with concepts below: once personalised, the instruction still described any restaurant. The four working sections are rewritten so the hour budget is measured against team size, the batch opens with the star dishes, the daily load is split against the strong dayparts, the grid only admits the declared networks and sales channels, and the week's metric is judged against the main goal. Role, method, context block and example stay untouched.v1.0.02026-08-19Initial version. Born in the August 2026 marketing batch to cover the missing piece: someone decides what to post and someone schedules the hour, but nobody was counting the hours the team actually has. From today the week arrives with a budget, a protected batch, a buffer nobody can steal and the hardest line to write: what will NOT be done this week.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.
