Muse for Hospitality Managers: Shift Schedules, Guest Messages, and Review Replies That Hold Up
A hospitality manager setup for Muse: a shift roster built from forecast demand and skills, guest messages drafted only from the booking in front of you, and review replies sorted by urgency, with events checked against staffing before they are confirmed.

Hospitality work fails at the handoffs. A roster covers the headcount and misses the one person who can run check-in alone on a sold-out night. A guest asks about early arrival, gets a promise the housekeeping board cannot keep, and starts the stay annoyed. A review that names a real problem sits for five days while three five-star reviews get quick thank-yous. Muse does the drafting and the sorting for those jobs, and you keep the roster, the promises, and the replies that go out in the property’s name.
This setup runs three jobs. Muse builds a draft roster from forecast demand, availability, and skills, drafts guest messages only from the booking and policies you paste in, and sorts reviews into a queue with draft replies you approve. An event or group booking gets confirmed only after the same roster says the staff can cover it.
A good roster starts from demand. Forecast arrivals, departures, occupancy, and covers by day, then turn that forecast into staffing by role using ratios you already know, such as rooms cleaned per housekeeper per shift or check-ins per front desk agent per hour. Publish the roster at least two weeks ahead where you can, check it for skills, approved time off, weekly hours, and fair access to the better shifts, and keep a named bench for call-outs. Guest communication has the same shape. A booking confirmation goes out immediately, a pre-arrival message three to five days before check-in covers arrival, parking, and requests, an in-stay problem gets a fast reply because the guest is still there to help, and a thank-you with a review link goes one to two days after checkout.
The short version
- Build the roster from the forecast, by role and skill, not from headcount alone. A shift is covered only when someone on it can do each required job.
- Draft guest messages only from the booking and policies pasted in that run. Early check-in, late checkout, refunds, and upgrades are never promised beyond what those policies state.
- Sort reviews before you reply. Safety, cleanliness, and billing complaints go to a manager first, within 24 hours. Positive reviews still get a specific reply.
- Check every event and group booking against the roster before you confirm it. Selling rooms without staff to clean, serve, and check them in is a problem created at the booking desk.
- The failure mode to watch for is a warm message that promises what operations cannot do, and the fix is a standing rule that Muse works only from the material pasted in that run.
The Setup: The Front Desk Board
Call the whole arrangement the Front Desk Board. The example I run it against is a 42-room boutique hotel with a small restaurant, run by a general manager and two shift leads, with a core team and a part-time bench for weekends and events. The inputs are ordinary: the arrivals and departures list and occupancy forecast from the booking system, staff availability and approved time off, a skills list that says who can work front desk alone, who is trained on the restaurant pass, and who can close, the property policies on check-in times, early arrival, late checkout, cancellations, and refunds, guest messages as they arrive, reviews from the platforms the property sells through, and the event inquiries book with dates, party sizes, and room needs.
The board depends on a few standing pieces. A standing instruction from our memory guide holds the durable parts: the property voice for guest messages and review replies, the list of promises Muse never makes on its own, and the list of issues that always go straight to a manager. Each request follows the same discipline as a task brief written for an agent: what dates, guests, or reviews are in scope, what the sources are, and what a finished draft looks like. The roster draft runs weekly as a scheduled routine, so the manager starts from a sorted draft instead of a blank grid.
The board borrows its queue discipline from the customer support lesson, where a human sends every draft and anything sensitive leaves the queue entirely, its scheduling discipline from the people ops lesson, where time off and hours are checked before a schedule is published, and its event discipline from the event planners lesson, where a run-of-show is checked against the people actually on shift. Managers who also run the front office like an operations desk will recognize the pattern in the operations managers lesson: the document, the board, and the floor have to match.
| Board | What it tracks | What decides the action |
|---|---|---|
| Roster board | Forecast demand, availability, skills, hours, bench | Whether each shift has the skills it needs, not just the headcount |
| Guest message queue | Booking, stage of stay, request, policy that applies | Stage and urgency first, time waiting second |
| Review queue | Platform, rating, issue type, date of stay as written | Issue type first, with safety, cleanliness, and billing to a manager |
| Events and bookings board | Date, rooms, covers, setup needs, staff required | Whether the roster for that date can cover it |
Prompt 1: Build the Roster Draft From the Forecast
Run this weekly, far enough ahead that the published roster lands at least two weeks before the first shift on it where your property and local rules allow. Draft one week at a time. A month at once hides the weekend where the forecast jumps and the bench is empty.
Schedule by role. Eight people on a Saturday means little if none of them can close the restaurant or work the desk alone during the check-in peak. Check every draft for the same faults before it goes out: a shift with no trained closer, a staff member over the weekly hours in the material you pasted in, approved time off that was ignored, and the same people taking every difficult close because the draft found them first.
Build a draft roster for the week below from the forecast, availability, and skills below. Return: (1) Roster: one row per day and shift, with the roles required, the staff assigned to each role, and the demand figure from the forecast below that set the staffing for that shift. (2) Gaps: every shift where a required role has no trained staff member available, every shift below the minimum staffing stated below, and every date where the bench is empty. (3) Checks: staff assigned during approved time off, staff over the weekly hours limit stated below, staff assigned to a role they are not listed as trained for, and any run of closing shifts followed by opening shifts for the same person. (4) Swaps to ask about: for each gap, a named staff member from the bench or availability below who could cover it, written as a question to ask them, not as an assignment. Rules: use only the material below. Do not assign anyone during time off listed below. Do not invent a skill, an availability, or an hours limit that is not in the material below, write not recorded instead. Do not publish or send this roster, return it as a draft for the manager.
Forecast for the week, with arrivals, departures, occupancy, and restaurant covers by day: [paste it]. Staff list with roles, trained skills, and contracted hours: [paste it]. Availability and approved time off for the week: [paste them]. Minimum staffing by shift, weekly hours limits, and bench list: [paste them].
Read the Gaps and Checks lists before you read the roster. A roster that looks full and fails the checks is worse than a short roster you can see clearly, because the short one gets fixed on Tuesday and the full one fails on Saturday night. Ask about swaps yourself and confirm them with the staff member before the roster is published. Muse drafts the grid, a manager makes the promises to the team.
Prompt 2: Draft Guest Messages From the Booking Only
Run this as messages arrive, sorted by stage of stay. An in-stay problem comes first, then a day-of-arrival question, then a pre-arrival request, then a post-stay thank-you. That order follows the guest. The guest who is standing in a room with no hot water can still be helped. The guest who checked out yesterday cannot.
Keep each stage to the message that stage needs. The pre-arrival message used in this setup is short: arrival date, check-in time and late-arrival arrangements, parking, and one open question about requests such as a quiet room, extra bedding, or an early arrival the property will confirm on the morning of the stay subject to availability. Early check-in is the request that breaks most often, because it depends on the previous guest leaving and housekeeping turning the room, neither of which a message sent three days earlier can guarantee. Guidance from Mews on guest messaging makes the same point. Messages work when they are timely, personal from the booking details, and clear about what happens next, with routine questions answered fast and complex requests handed to a person.
Draft replies to the guest messages below, sorted by stage of stay. Return: (1) Manager first: every message reporting a safety concern, a cleanliness failure, a billing dispute, a refund request, or a guest who is in the property now and unhappy, each with the issue in one line and the booking reference exactly as written below. Do not draft a reply to these. (2) Draft replies: for each remaining message, a reply in our property voice that uses the guest name and booking details exactly as written below, answers only from the policies and property facts below, and states clearly what we will do next and by when, using only times the policies below support. Keep each reply under 90 words. (3) Requests we cannot confirm yet: every request for early check-in, late checkout, a specific room, or an upgrade, with the reply that explains how and when we will confirm it, taken from the policies below. (4) Missing facts: any question a guest asked that the policies and facts below do not answer, written as needs checking. Rules: use only the material below. Do not promise an early check-in, a late checkout, a refund, an upgrade, or a room type that the material below does not confirm for that booking. Do not invent a check-in time, a parking detail, or a price. If a fact is not below, write needs checking instead of drafting around it.
Guest messages, with guest names, booking references, dates, and stage of stay: [paste them]. Policies on check-in, early arrival, late checkout, cancellation, refunds, and upgrades: [paste them]. Property facts: parking, breakfast times, Wi-Fi, and contact details for the front desk: [paste them]. Property voice notes: [paste them].
Send replies only after you have read them against the booking. The draft can be warm. It cannot be generous with rooms, times, or money the policy does not cover. Work the Manager first list yourself, in the same sitting, and act before you reply at length. A guest with a problem in the building needs a person at the door or on the phone, and the written reply records what was done.
Prompt 3: Sort Reviews, Draft Replies, and Check the Event Against the Roster
Run the review sort daily for a busy property and every second day for a quiet one. Respond to negative reviews first, and aim to answer within 24 to 48 hours while the stay is still fresh. Industry guidance collected by Hospitality Net on review handling sets the same standard: respond within 24 hours where possible, thank the guest, address the specific point, state what will be done, and invite the guest to contact management directly for resolution. Never confirm booking details, rates, or personal information in a public reply, and keep any compensation in a private channel.
The event check belongs in the same run because reviews and events meet on the roster. A wedding inquiry for a date that already has high occupancy, a thin bench, and no trained closer books a bad night in advance. Check rooms, covers, setup and clear-down time, and the staff the event needs against the forecast and roster for that date before anyone confirms it.
Sort the reviews below, draft replies, and check the event enquiry below against the roster. Return: (1) Manager first: every review reporting a safety concern, a cleanliness failure, an injury, a billing problem, or discrimination, plus every review of two stars or fewer, each with the issue in one line. Do not draft a public reply to these beyond a short holding reply if one is provided below. (2) Draft replies: for each remaining review, a reply in our property voice, under 90 words, that thanks the guest by the name as written below, names one or two specific points from their review, states the action taken or planned only if that action is stated below, and invites them to contact the manager directly using the contact below. For a positive review, name the specific thing they praised and the team it belongs to. (3) Repeats: any complaint or praise that appears in three or more reviews below, listed once with the count and the department it belongs to. (4) Event check: for the event enquiry below, the rooms, covers, setup needs, and staff required, set against the forecast and roster below for that date, flagged as can cover it, tight, or cannot cover it, with the reason and the gap named. Rules: use only the material below. Do not confirm a stay date, a rate, or a booking detail in a public reply that is not already in the review text below. Do not promise compensation, a refund, or a fix that is not stated below. Do not confirm the event, return the check as a draft for the manager.
Reviews, with platform, guest name as shown, rating, date, and full text: [paste them]. Actions already taken or planned for issues named in the reviews, and the manager contact for public replies: [paste them]. Event enquiry, with date, party size, rooms, covers, and setup needs: [paste it]. Forecast and draft roster for the event date: [paste them]. Property voice notes: [paste them].
Read Repeats before you send any reply. One complaint about water pressure is a maintenance ticket. Four complaints about water pressure in a month is a capital problem, and the reply that calls it a one-off will read badly next to the other three. Share positive repeats with the team by name where the review names them. For an event flagged tight or cannot cover it, the honest options are to add bench staff and confirm them first, to reduce the size or scope of the event with the organizer, or to decline the date. Confirming first and staffing later is how a good property earns the review it then has to answer.
What Can Go Wrong
The common failure is a friendly message that commits the property to something operations cannot do. It happens in a predictable way: the policy is in a binder, the booking is on the screen, a similar message from last week is open as a model, and a detail from that older stay, an early check-in that was possible on a quiet Tuesday, a late checkout that a previous manager allowed, a room with a view that happened to be free, ends up in the new draft as if it were confirmed for this guest. The guest arrives expecting it, the desk cannot deliver it, and the stay starts with an apology for a promise nobody on shift made. The roster version of the same failure is quieter: a draft that respects availability as it was pasted, after a swap agreed in the corridor changed it, so the published roster and the team’s understanding part company.
The fix is an evidence rule you keep in the standing instruction: Muse may state a booking fact, a policy, a time, or a staffing fact only when it appears in the material pasted in that run, and it writes not recorded or needs checking everywhere else. Then read the short lists first each run, Gaps and Checks on the roster, Manager first and Requests we cannot confirm yet in the message queue, and Repeats in the review queue. Those lists are where this setup tells the truth about itself. Keep the pasted material current as part of the job: after any swap, policy change, or event confirmation, update the source the next run will paste from, or the next draft will faithfully reproduce last week’s property.


