Someone I know runs a small neighbourhood restaurant. Two locations, four people including himself.
The most annoying stretch is the hour or so after closing at ten. The day’s group-buy orders need a pass to check them, tomorrow’s new set menu has to be put together, and yesterday’s reviews are still sitting there unanswered.
In that hour, the part that actually needs thought is under ten minutes. The rest is spent on the same loop: open, find, fill in, send, then open the next page.
Three platforms, two locations, entering the same set-menu details three times, four or five hours a week.
Three kinds of phone work left after closing
Copy and fill: check-in records, set-menu listings, store profile updates, changes to opening hours. The information already exists. It only has to be moved, again and again.
Copy and reply: replies to common questions, thank-yous for good reviews, booking confirmations.
Must be you: bad reviews, complaints, dealing with people from the platform, conversations that involve a promise.
The first kind has the most items. The third has the fewest, and the cost of a wrong sentence is the highest. The second sits in between. Most of the time goes to the first kind, because there are so many items.
Check-ins and group-buy listings, and how far each can go
The check-in action itself stays with you. The customer is waiting at the counter. Scan the code, confirm, say “done”. Those few seconds have to happen on the spot.
The record and the check after the check-in can be handed over.
A lot of owners go by memory, or flip through the dashboard in passing, and only find a few entries that do not match when they reconcile at the end of the month. By then the records on the platform side are hard to search back through.
What can be handed over is this step: at a fixed time each day, read the check-in records out of the dashboard and append them to a sheet. The step copies the numbers. It does not review them, edit them, or act on the orders.
Described in iEasyRun, it comes out roughly like this:
Open the order pages for these three platforms, read out every group-buy
order checked in today (order number, set menu, check-in time) and append
them to the end of this sheet.That description has no “how to tap”. It only says what to read, and where the reading goes.
It does not touch any operation. The risk is zero. The worst case is one misread number, which you can see at a glance.
The first time you list a set menu, judgement is involved: which set menu to put together, what price to set, which hours it can be used. Those are decisions about the business. They stay with you.
After that, the same information, already decided, has to be entered once on each of three platforms.
The field names differ on each platform. One calls it “set name”. Another calls it “item title”. One asks you to fill in “terms of use”. Another splits that into “validity” and “blackout dates”. The content is the same thing. The format has to be filled three times.
What can be handed over is that second half:
Open the listing pages for these platforms and fill in the set-menu details
from this configuration sheet. Use the images in this folder. Stop when you
are done and wait for me to confirm before submitting.Keep “stop, and wait for me to confirm”. A listing changes what is shown to customers. If a field is wrong and the flow is still sitting before submit, one extra confirmation keeps a wrong set menu from going live.
Review replies and store content
Good reviews can use a prepared reply. Vary them. Platforms recognise template wording. Dozens of identical “thanks for your support, we hope to see you again” replies in a row on the same store do the store no good. Keep three to five and rotate them, or include the name of the dish.
Write neutral reviews and bad reviews yourself. The customer wants to be taken seriously. A forced template makes a bad review likely to escalate, and then to become a complaint to the platform.
What reviews can hand over is the reminder. The reply is still written by you.
Each morning, check the review pages for these stores. If there are new
reviews, screenshot them and send them to me.Missing a bad review costs more than answering one late. A conversation that needs a careful reply is also a poor fit for a template.
What to post, and how to shoot it, is your judgement. It stays with you. Sending the same clip to several platforms is worth handing over.
One ten-second video goes out once on Douyin, once on Xiaohongshu, and once on WeChat Channels. The three actions do not need the decision to be made again. Together they take a bit over twenty minutes, and each time the file has to be chosen again and the title written again.
Post the videos in this folder to these three platforms, using the matching
title from the sheet.For how to lay that out in detail, see how bulk posting on Xiaohongshu works. The approach is the same.
What to keep, and which job to hand over first
Calming someone under a bad review. No exceptions.
Conversations with a platform account manager, or with support. Those go back and forth, and they include probing. A machine cannot take them.
Anything that involves a promise: refunding a deposit, booking the room out, issuing an invoice, holding a table. The wrong sentence is a dispute.
Last-minute changes: closing for half a day today, a temporary price change. There is no fixed pattern, and handing them to a machine makes a wrong send likely.
If the wrong wording in that sentence would cause a real loss, keep the job. “Hope to see you again” sent wrong is only awkward. “The deposit can be refunded” sent wrong costs money.
Hand over read-only work first. The daily check-in reconciliation, and the review reminders. They change no data, and once they are running you can feel how much manual checking dropped.
Then hand over the copy-and-fill work. Set-menu listings, profile updates, sending the same content out. Add a manual confirmation.
Messages that go out to customers come last, and only the most standard lines.
To judge whether a job can be handed over, ask three questions.
Is the answer fixed? If it has to be thought through again every time, handing it over only moves the thinking to another place.
Does a mistake cause a real loss? If it does, keep the job in your own hands.
Does it need a judgement on the spot? If it does, keep it.
If all three pass, it can be handed over. If one of them fails, leave it for now.
Start with one location, and try the read-only reconciliation for a week. The software is completely free, and it runs once it is installed on your own computer. When a device will not stay connected, see what to do when a phone keeps going offline. For how the data you sort through every day lands in a sheet, see turning phone screenshots into a spreadsheet.
Frequently asked questions
- How should a store's phone work be sorted?
- Three kinds: copy-and-fill (check-in records, set-menu listings, profile updates), copy-and-reply (common questions, thank-yous, booking confirmations), and must-be-you (bad reviews, complaints, anything involving a promise). The first is the largest and the third is the one that hurts.
- Can in-person check-ins be automated?
- The check-in itself cannot — the customer is standing at the counter and those few seconds have to happen live. What can be handed over is everything after it: reading the day's checked-in orders at a fixed time and appending them to a sheet, without reading, changing, or acting on anything.
- Why does listing a set menu take so long?
- Because the first time needs judgement — which set menu, what price, which hours — and everything after that is repetition. The same information goes onto several platforms, each with different field names, so you enter one thing in three different formats.
- Can good reviews use a template?
- Yes, but not one identical template forever. Platforms recognise boilerplate, and dozens of identical replies on one store do it no favours. Keep three to five variants, or mention the specific dish.
- Can a machine answer negative reviews too?
- No. Not because a machine writes badly, but because those customers want to be taken seriously rather than politely dismissed. A template usually escalates the review into a platform complaint.
- So what exactly gets handed over in reviews?
- Not the reply, the alert. Have the machine check each store's review page once a day and screenshot anything new. You never miss one — missing a bad review costs far more than answering it late — and you never answer with a template that deserved attention.
- Which store tasks should never be handed over?
- Calming an angry reviewer, conversations with platform account managers or support, anything involving a promise (deposit refunds, private bookings, invoices) and anything improvised (a sudden closure or price change). One test covers it: if the wrong sentence causes real loss, keep it.
- What order should I hand things over in?
- Read-only first (check-in reconciliation, review alerts) because the risk is zero; then copy-and-fill (listings, profile updates, content distribution) with a confirmation step; and outbound messages last, and only the most standard ones.
How many locations?
Let the computer take the read-only jobs first
Software is completely free and runs on your own computer. Start with one location for a week.