AI assistant · N5 Complete system
Daily Community Manager Work Plan Builder for Restaurants
The work agenda for ONE social-media shift, not the monthly calendar: where the daily 45 to 60 minutes go, in what order, with a start time and a length per block, and what gets dropped without guilt on the day the dining room fills.
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
- There is almost always a calendar and almost never a shift.
- Whoever runs the accounts opens the phone at two in the afternoon, loses an hour answering messages, and the day ends with no product photo and no approved post published.
- This assistant does not decide what gets published — that arrives settled —: it allocates the time.
- It returns the day plan in blocks with start times and minutes, a slow-day version and a peak-day version that are not the same, the triage order for when forty messages land at once, and the one-line log that feeds the weekly reading at close of shift.
What you end up with
The day plan as a table, one block per row, with start time, length in minutes, the exact task, network or sales channel, owner and closing signal; the two shift versions — slow day and peak day — with the triage order and the list of what gets postponed without guilt; and the one-line closing log with its 7-day reading 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: «We're Sazón de Origen, contemporary Colombian casual dining in Medellín: two locations, six years, own delivery. Tuesday-to-Friday lunch, 12:00 to 2:30, is what pays payroll, and Sunday midday is the other peak. Catalina, from admin, runs the accounts and has 50 free minutes after service, between 3:00 and 4:00. This month's calendar is already approved. What I can't take anymore is her losing the whole hour on WhatsApp orders with not one photo of the Bandeja de la casa left; and Sunday, our peak, nobody touches social.»
| Block | Start | Length | Exact task | Network or sales channel | Owner | Closing signal |
|---|---|---|---|---|---|---|
| Capture in service | 12:40 p.m. | 6 min | Two photos and a 10-second video at the pass: the Bandeja de la casa plated and the Sancocho de tres carnes going out with steam on it | Phone camera, no posting | Andrés, at the pass | 3 files in the day's folder, before service drops |
| Reply cut | 3:00 p.m. | 22 min | Everything since 8:00 a.m., in this order: own-delivery orders with a committed time, group bookings, prices and hours, praise | WhatsApp and Instagram DMs | Catalina | Inbox at zero, tomorrow's orders copied onto the kitchen ticket |
| Posting | 3:22 p.m. | 12 min | Upload the piece the calendar approved for today and read it aloud before publishing; whatever sounds like a brochure gets rewritten on the spot | Catalina | Published, with the location's order number checked | |
| Close | 3:34 p.m. | 6 min | Second pass on new comments and the one-line log | Catalina | Log written in the register notebook |
Capture does not come out of Catalina's hour: it is 6 minutes from Andrés at the pass, because by 3:20 there is no Bandeja plated to photograph. The 10 minutes she has left are not distributed: they are the cushion for the day that goes sideways. Figures are illustrative; the real minutes get calibrated by walking the shift with Catalina in week one.
Slow day (Tuesday). The full shift above plus one thing: the 10 cushion minutes go into shooting Thursday's capture early and answering the praise left over from Sunday.
Peak day (Sunday midday). 18 minutes, two blocks, nothing else, because nobody has a free hour that day. Reply cut trimmed to 12 minutes, filtering own-delivery orders with a committed time and group bookings only; 6 minutes capturing the long family table already served, which on Sunday is the best photo the house has. Sunday's post comes from what was loaded on Friday.
Postponed without guilt, and written down: praise gets a heart on Sunday and a written reply on Tuesday; fine video editing never happens on a Sunday; the photo folder gets sorted on Tuesday.
Triage order when 40 messages land and 15 minutes remain: 1) own delivery with a committed time, which leaves more margin than the marketplace and so goes first; 2) a public complaint others can see; 3) price and hours, with the reply already saved; 4) praise. Whatever missed the block does not happen «later»: it is noted and enters the next day's cut.
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 sit **the closing log and the 7-day reading**: the line written at the end of the shift, the table that gathers the week, and the rule for the block that falls three days running — move the hour before the content, which is what turns a shift into a routine that corrects itself.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 11 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-20The day plan is tied to this house: the reply cut closes before the declared first peak, the posting block runs account by account across the active social channels and gets read aloud against the house tone, capture happens with the best-selling dishes plated, and Monday's seven logs are read against the year's goal. Those fields used to live in the header alone.v1.0.02026-08-19Initial version. Born in the August 2026 marketing batch to close the gap its two sisters left: the calendar says WHAT gets published and the grid says WHEN it goes out, but neither said in what order the person works on a Tuesday at two. It ships with a peak-day version because a plan that only survives quiet days is not a plan.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.