HospitalityOctober 29, 20265 min read

How DND/Make Up Room Requests Flow in a Hotel

How a guest's DND or Make Up Room request moves from keypad to corridor sign to housekeeping board, and what clears automatically.

A guest sets Do Not Disturb (DND) or Make Up Room (MUR) at an in-room keypad, touch screen, or app; that signal lights the corridor indicator outside the door, mutes the doorbell, and simultaneously pushes a status update into the property management system so the housekeeping board and front desk see it in real time. Room moves and checkout clear DND/MUR/Service Declined automatically; end-of-day reset is a configurable PMS control that an integrator and the hotel's operations team must agree on before go-live. Getting this right means testing the full event path — guest control point, corridor signage, PMS status, and the clearing rules — before any floor opens.

How does the guest's request reach the corridor sign and the front desk?

In a Crestron-based guest room, pressing DND or MUR on an in-room keypad triggers a scene that is "clearly displayed outside the door" via backlit corridor signage, according to Crestron's hospitality guest room documentation. The same action also needs to reach the property management system. Oracle's OPERA Cloud integration guide describes the mechanism directly: the partner system handling the in-room device or app "sends a setGuestHousekeepingServiceRequest API call to OPERA Cloud with the related Service Status," and OPERA Cloud then "displays it in the OPERA Cloud Housekeeping Room status section," per Oracle's Business Context documentation. That same source also describes the reverse path: when a front-desk agent sets the status manually in the OPERA Cloud UI, the change "will trigger a Business Event GUEST SERVICE STATUS REQUEST" that a subscribed partner system (the room control platform) receives automatically. So the status is meant to stay synchronized in both directions, not just guest-to-desk.

On the housekeeping side, Oracle's OPERA Cloud user guide confirms that staff can also manage the Guest Service Status from several different screens — the Housekeeping Board, the Housekeeping panel of an in-house reservation, the Task Sheet Presentation screen, and the Task Sheet Companion — so housekeeping attendants working a room list do not need to be in the same interface as the front desk to see or change a request, according to Oracle's Housekeeping Board documentation.

A property planning a custom build on Crestron should confirm which specific scene and PMS interface version its integrator is wiring, since the exact API behavior depends on the PMS edition in use; see Cave Group's hospitality page for how guest-room automation is scoped against a specific PMS platform.

What clears automatically, and what needs staff action?

This is the question that trips up go-live testing most often, because the answer is not uniform across all three statuses. According to Oracle's Housekeeping Board documentation, the automatic-clear logic breaks down as follows:

  • Reservation room move: Do Not Disturb, Make Up Room, and Service Declined are all removed automatically.
  • Checkout: Do Not Disturb, Make Up Room, and Service Declined are all removed automatically.
  • Make Up Room specifically: it is also cleared when the room is started from the Task Sheet Companion (i.e., when an attendant begins cleaning it) — independent of end-of-day processing.
  • End of day: clearing DND, Make Up Room, and Service Declined at end of day is controlled by the "Reset Guest Service Status" OPERA Control, which lets a property specify which of the three statuses reset to "No Status Selected" automatically overnight and which stay sticky into the next day.

That last point matters for the operational question hotels actually ask before opening: does DND survive overnight, or does it reset and need the guest to re-set it the next day? The answer in OPERA Cloud is that it is a configuration decision, not a platform default — the hotel's operations and IT teams need to pick the Reset Guest Service Status setting deliberately rather than assume a behavior.

What should an integrator test before a floor opens?

Based on the documented event path, a pre-opening acceptance checklist should at minimum verify each of the following against the live PMS, not just the control system in isolation:

  1. Guest-set DND/MUR from the in-room keypad or app correctly fires the setGuestHousekeepingServiceRequest call and appears on the OPERA Cloud Housekeeping Board within an acceptable delay.
  2. Front-desk-set status (entered directly in OPERA Cloud) correctly triggers the Business Event and is received by the room control system so the corridor sign updates — confirming the sync works in both directions, not just guest-to-PMS.
  3. Doorbell/chime suppression behaves correctly in DND rooms. Crestron's broader room platform documentation notes that Do Not Disturb mode silences interrupts and chimes in a room, though some chimes (fire alarm, security) can be configured to bypass DND — a hotel should confirm with its integrator which alerts are allowed to override guest DND, per Crestron Home OS documentation on Do Not Disturb.
  4. Room move and checkout clearing, tested as actual PMS transactions, not simulated toggles — since the clearing is a PMS-side rule tied to the reservation record.
  5. End-of-day reset behavior, tested against whichever Reset Guest Service Status configuration the property has chosen, so staff are not surprised by stickier or more aggressive resets than intended on opening night.

Any property building a custom Crestron guest-room system, or deploying Lutron myRoom where a packaged platform fits, should ask its integrator to walk through this specific test list — by room, by status, and by PMS platform — as part of the punch list, not after rooms are already in inventory.

Frequently asked questions

Does Do Not Disturb survive into the next day automatically?

It depends on the property's OPERA Cloud configuration. The "Reset Guest Service Status" OPERA Control determines whether DND, Make Up Room, and Service Declined reset to no status at end of day, so a hotel must decide and configure this behavior rather than assume it.

What clears a Make Up Room request besides the guest turning it off?

Make Up Room clears automatically on checkout, on a reservation room move, or when an attendant starts the room from the Task Sheet Companion — housekeeping beginning the clean removes the status without the guest or front desk doing anything further.

Can hotel staff set or clear DND directly, without the guest touching anything?

Yes. OPERA Cloud lets staff set or update the Guest Service Status from the Housekeeping Board, an in-house reservation's Housekeeping panel, the Task Sheet Presentation screen, or the Task Sheet Companion, and that change can trigger a Business Event back to the room control system.

Should fire alarm or security chimes be allowed to override a guest's DND setting?

Crestron's room platform documentation notes that interrupts and chimes can be configured to bypass Do Not Disturb mode, citing fire alarm and security chimes as examples — a hotel should confirm with its integrator exactly which alert types are configured to override DND before opening.

Is this the same workflow whether the guest room runs Crestron or Lutron myRoom?

The underlying PMS logic — housekeeping status, automatic clearing rules, and end-of-day resets — is a PMS-side behavior documented for OPERA Cloud regardless of control platform. The guest-facing keypad experience and corridor signage integration should be confirmed with your integrator for the specific platform in use.

Sources

Work With Cave Group

Planning a hotel technology upgrade?

Cave Group designs, installs, and supports these systems for luxury homes, hotels, and yachts across New York, New Jersey, and Europe — one partner from design through 24/7 support.

Start a Project

or explore our work