A weekly routine
Lesson 4 of 6 · Hotels and restaurants
Lesson summary
A routine is the same work in the same order each week, with a person at the end. The agent drafts. The manager posts.
Open the database Tasks. Three rows come back each Monday: invoice check, review replies, rota draft (US: schedule).
Set the Priority of each row. The Owner of each row is a person.
Give the review replies to Guest desk, with yourself as Reviewer and short Acceptance criteria. Nothing is sent to the agent: it finds the task at its next check-in.
Guest desk writes a draft reply in each row of the database Reviews. The task shows Needs review.
Edit the drafts that need a promise or that show private details.
Take the allergy complaint yourself. Phone the guest. Speak to the chef.
Post the replies by hand on each site and set the rows to Posted. Then open the task and select Accept.
Try it now
Choose three jobs that come back every Monday. Set the order and the owner of each one.
English transcript · same language as the video
Monday morning. The weekend left paper behind. Eleven new reviews. Fourteen supplier invoices. And next week's rota, with a wedding for seventy on the Saturday.
Ines does not start with the nearest thing. She sets the order first. That is her job, not the agent's.
Open the database Tasks. Three rows come back each Monday. The invoice check is first, because a price rise that nobody sees costs money every day. The review replies are second. The rota draft is third: Priya needs it by Wednesday.
Each row has an owner, and the owner is always a person. Each row has an assignee: here, an agent. And each task says what done looks like.
We follow the reviews. Ines gives the task to Guest desk, with herself as the reviewer. The acceptance criteria are short. One draft reply for each review. Use the house voice. Use only facts from the review and from our records. Do not offer money. Do not post anything.
Nothing is sent to the agent. Guest desk finds the task at its next check-in. It writes a draft reply in each row of the database Reviews. Then the task shows Needs review.
Ines reads the drafts. Eight are good as they are.
Two need her hand. One guest wrote about a slow breakfast. The draft says sorry. Ines adds what she changed: a second person on the counter from half past seven. Only she can promise that. Another draft confirms the dates of a guest's stay. She cuts that line. A reply never confirms private details.
The last review is different. A guest writes that she had an allergic reaction after dinner. Guest desk wrote no draft. It marked the row Owner only, and left a comment for Ines. That is the house rule, and the agent followed it. Ines phones the guest herself, and she speaks to Tobias.
Then Ines posts the ten replies herself, on each review site, and marks the rows Posted. The agent drafts. The manager posts.
There is one line that we do not cross. An agent drafts replies to real reviews. It never writes a review. Nobody asks staff or friends to write one, and nobody pays for a good one. Fake reviews are banned in the United States and in the United Kingdom.
Ines opens the task and selects Accept. The task shows Done.
Next Monday, the same three rows come back. That is a routine: the same work, the same order, a person at the end. In the next lesson, a bigger job: the autumn menu.
How was this lesson?
Tell us what was clear and what we should change. Your answers shape the next lessons.