Automated NRC Health Service Issue Follow-Up
Every hour, WebRun opens NRC Health Rounding to find service issues logged during rounds, like a cold meal or a broken TV, posts each open item to the responsible department's Microsoft Teams channel, and triggers a PagerDuty escalation to that department's on-call if the issue is still open past your SLA.
How do I make sure service issues logged during patient rounding actually get fixed?
WebRun checks NRC Health Rounding every hour for service issues logged during rounds, posts each open item to the responsible department's Microsoft Teams channel, and triggers a PagerDuty escalation to that department's on-call if it's still open past your SLA. Issues raised during a round get fixed while the patient is still there, instead of surfacing later as a complaint.
- Service issues get fixed while the patient is still in the room
- Nothing sits open past your SLA without an automatic escalation
- Each department only sees the issues that are actually theirs to fix
Built for environmental services · facilities teams · dietary departments · patient experience teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.nrchealth.comin a real browser with your saved login - no setup, no API keys. -
1
NRC Health Rounding - find open service issues from rounds
nrchealth.com
WebRun opens NRC Health Rounding to find open service issues from rounds. - Open NRC Health Rounding and pull service issues logged during rounds
- Sort each issue to the department that owns it, like EVS, dietary, or facilities
- Note how long each issue has been open
Done when Every open service issue is sorted to its owning department with an open time.
-
2
Microsoft Teams - notify the responsible department
microsoft.com
WebRun opens Microsoft Teams to notify the responsible department. - Post each new open issue to the owning department's Microsoft Teams channel
- Include the room and the exact concern from the round
- Mark it resolved once the department confirms the fix
Done when Every open issue has been posted to the right department channel.
-
3
PagerDuty - escalate anything still open past SLA
pagerduty.com
WebRun opens PagerDuty to escalate anything still open past SLA. - Trigger a PagerDuty escalation for any issue still open past your SLA
- Route it to that department's on-call rotation
- Note the escalation on the original issue so it isn't paged twice
Done when Every issue past SLA has been escalated through PagerDuty exactly once.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does the patient know their issue was escalated?
That's between the department and the patient during their next visit. WebRun only manages the internal routing and escalation, it never contacts the patient itself.
What counts as past SLA?
Whatever open-time limit you set per issue type, like 2 hours for a cold meal or 4 hours for a maintenance request. Anything crossing that line gets escalated.
Can different departments have different SLAs?
Yes. Set a different threshold per department or issue type, and WebRun will escalate each one against its own clock.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.