Reference · built on requestOperator by FibricHospitality & guests

DND Check

Watches rooms on Do Not Disturb or refusing service past your policy limit and proposes a welfare check, naming who should knock.

Request accessPricing ↗

About

A room on Do Not Disturb for a day is normal. A room that has refused service for longer than your policy allows is a question of safety, and the answer is a person at the door. DND Check reads housekeeping status from your property management system, the attendant's refused-service entries, the reservation behind the room, and how long the guest has been in-house.

When a room crosses the limit you set, it proposes a welfare check and the person to make it, posted to your team channel. The manager on duty approves. The check, the outcome, and the time are recorded against the reservation.

This is a reference listing. It documents what Fibric would read from DND Check and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Housekeeping status per room in Cloudbeds through getHousekeepingStatus, including the Do Not Disturb and Refused Service states
  • Housekeeping room status, discrepancies, and task sheets through the hsk module in OPERA Cloud
  • Housekeeping tasks in Mews by department and deadline, including tasks closed as not done
  • The reservation on the room: arrival date, nights in-house, number of guests, and any notes
  • Hours since the last completed service on the room, from the housekeeping records above
  • Acknowledgements on the proposals it posts to Teams or Slack

Proposed actions

  • Target capability: propose a welfare check on a room past the policy limit, naming who on duty makes it, for the manager to approve
  • Target capability: propose the message to the team channel with the room, the hours since service, and the reservation summary
  • Target capability: propose a housekeeping note or trace on the reservation recording the check and its outcome
  • Target capability: propose escalation to the manager on duty when a check is not acknowledged within the time you set
  • Target capability: propose a courtesy message to the guest offering a service time, where your policy allows it

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Knock on the second morning

    Cloudbeds shows a room in Refused Service since the previous morning, past your limit. The operator proposes a welfare check by the floor supervisor and posts it to Teams for the manager to approve.

    With Cloudbeds, Microsoft Teams

  • Record the check on the stay

    After the check, the supervisor marks the outcome on the Slack post. The operator proposes a housekeeping note on the OPERA Cloud reservation with the time and what was found.

    With Slack, Oracle OPERA Cloud

  • Offer a service time first

    Where policy allows, the operator proposes an SMS through Twilio offering the guest a time for service before anyone knocks, and records the reply against the Mews reservation.

    With Twilio, Mews

Requirements

  • A property management connector that exposes housekeeping status, including Do Not Disturb or refused service: Cloudbeds, Oracle OPERA Cloud, or Mews
  • A Teams or Slack channel for the manager on duty, with approve and decline actions
  • Your policy: the hours a room may refuse service before a check, who makes the check by shift, and the escalation path
  • Optionally, a Twilio number for the courtesy message to the guest
Authentication
DND Check keeps no credentials. It reads housekeeping status and reservations through your property management connector and posts proposals through your Teams or Slack connector.

Limits

  • It knows what housekeeping records. A door sign that no attendant logs is invisible to it.
  • The check is made by a person. The operator does not open doors, call rooms, or contact emergency services.
  • Where the property management system records only clean and dirty, the refused-service signal comes from tasks or notes you keep.
  • It works in hours since the last service, not in judgments about the guest.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request DND Check ↗

Questions and answers

Who approves the check and what do they see?
The manager on duty. The proposal shows the room, the hours since the last service, the reservation summary, and the person proposed to make the check. The manager approves, changes the person, or declines with a reason.
What record is left after a welfare check?
A receipt per room: when the limit was crossed, the housekeeping entries behind it, who was proposed and who approved, when the check was acknowledged, and the outcome written by the person who made it. The note on the reservation is proposed with the same facts.
Does it contact the guest or enter the room?
No. Someone knocks. A courtesy message goes only where your policy allows it and after approval. It never opens a door, places a call to the room, or alerts anyone outside your team.
Ask about DND Check

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy