DND: How to Configure (MOP 2.0)

DND: How to Configure (MOP 2.0)

Do Not Disturb (DND) configuration allows properties to define how many consecutive days a room can remain in Do Not Disturb status before MOP automatically creates a DND Alert. Proper configuration helps ensure guest safety, compliance, and timely follow-up without disrupting daily operations.

DND Threshold Configuration

Each property can define how many consecutive DND days are allowed before an alert is triggered, with thresholds configured at the property level and aligned to brand or local safety requirements. To prevent unintended changes, DND Threshold permissions control which users can view or update this configuration, ensuring access is limited to only those who need it.
  1. Common thresholds include 2, 3, or more days, depending on brand standards
  2. All threshold changes are logged for visibility and auditing
Steps to Threshold Configuration

Use the steps below to configure or update the DND threshold for a property, which can be set between 1 and 7 consecutive days based on property or brand requirements.

DND Threshold Permissions
DND Threshold permissions control which users can view or modify DND configuration settings, ensuring that access is limited to only one or a small number of authorized users. Because changes to the threshold directly impact alert creation and compliance, restricting access helps prevent unintended updates.

Assigning Permissions at the Role Level



Assigning Permissions at the User Level




Alert Notifications Configuration

To ensure proper visibility and management of alerts, administrators can grant a role or individual user access to the Alerts page, which allows them to view all alerts and see the notification badge when an alert remains unassigned. Alert notifications ensure the appropriate users are informed when action is required, enabling timely review, assignment, and documentation. From a team usage perspective, correctly configuring access to the Alerts page is critical to ensure only authorized users can view and manage alerts, helping prevent missed tasks, support accountability, and ensure alerts are handled consistently across the property.

Steps to Alert Notification at the Role Level
Use the steps below to configure role-based permissions that control which users receive and can act on DND alert notifications.


Steps to Alert Notification at the User Level
Use the steps below to assign alert notification access directly to individual users based on their assigned roles and permissions.

What Happens Next

The updated DND threshold is applied immediately at the property level.
  1. All configuration changes are recorded in the Configuration Activity Log, including:
    1. User who made the change
    2. Previous and new values
    3. Date and time of the update
  1. The activity log supports visibility, auditing, and compliance tracking.
After the threshold is set:
  1. Alert notifications must be configured to ensure the correct users are notified.
    1. At the Role Level, permissions control which roles can receive and act on DND alerts.
    2. At the User Level, permissions ensure individual users within those roles receive notifications.
NotesChanging the DND threshold impacts when DND alerts are automatically created for all rooms at the site. Alerts will only be actionable if the appropriate role and user permissions are enabled.

Still Need Help With This Topic?

Ask Yourself:
  1. Is the DND threshold configured correctly for my property?
  2. Are alerts triggering at the expected number of days?
  3. Are authorized users receiving notifications?
  4. Is Action Taken being documented before completing alerts?
Support May Ask You:
  1. What DND threshold is currently configured?
  2. Which room triggered the alert and when?
  3. Was the alert assigned and completed?
  4. Is DND monitoring enabled at the site level?

    • Related Articles

    • Do Not Disturb (DND) Monitoring Feature (MOP 2.0)

      The new Do Not Disturb (DND) Monitoring Feature helps properties track guest rooms that show consecutive days of “Do Not Disturb” or service refusal. When a room reaches your configured threshold, MOP creates a DND Alert task, ensuring timely ...

    • Download Safety Alerts Report (MOP 2.0)

      The Download Safety Alerts Report feature allows authorized users to export a complete CSV file of safety-related alert activity. The report includes both active and archived alerts—specifically DND Alerts and Suspicious Activity—and is designed to ...

    • DND: What Is It and How Does It Work? (MOP 2.0)

      Do Not Disturb (DND) monitoring helps properties track guest rooms that cannot be serviced due to Do Not Disturb or service refusal statuses. By monitoring consecutive days without room access, MOP helps ensure guest safety, operational awareness, ...

    • Report Suspicious Activity (MOP 2.0)

      Report Suspicious Activity allows hotel staff to discreetly document and escalate potential security concerns directly within MOP. Submissions create a dedicated alert task, notify the appropriate team members, and ensure incidents are tracked, ...

    • MOP Overview

      Introducing MOP — the housekeeping and maintenance platform that streamlines daily operations, automates routine tasks, and strengthens team coordination. Accessible on any phone or laptop with no downloads required, MOP brings hotel automation to a ...