All templates

Automated Therap Incident Report Follow-Ups

Every morning, WebRun opens Therap, finds incident reports past their required follow-up window, posts the overdue list to your QA lead in Slack, drafts the guardian notification for each incident in Gmail, and drafts a follow-up review meeting hold on Google Calendar so nothing sits open past its deadline.

Runs on WebRun · Strict Lockdown policy
Every morning at 7:00 AM WebRunorchestrates each step
1 Therap find incident reports needing follow-up
2 Slack alert QA of overdue follow-ups
3 Gmail draft the guardian notification
4 Google Calendar draft a follow-up review meeting hold
In short

How do I make sure every host home incident report gets a timely follow-up?

WebRun checks Therap every morning for incident reports missing a required follow-up, root cause, or corrective action, posts the overdue list to your QA lead in Slack, and drafts both the guardian notification and a follow-up review meeting hold. Nothing is sent or scheduled until a supervisor reviews and approves it.

  • No incident report sits open past its required follow-up window
  • Guardian notifications are ready to send the same morning instead of days later
  • State notification deadlines are flagged 24 hours before they're missed

Built for host home agencies · QA and compliance leads · shared living supervisors · I/DD program directors

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.therapservices.net in a real browser with your saved login - no setup, no API keys.

  2. 1
    Therap - find incident reports needing follow-up
    therapservices.net
    WebRun in Therap: find incident reports needing follow-up
    WebRun opens Therap to find incident reports needing follow-up.
    • Open Therap and filter incident reports to those still open or missing a required follow-up entry
    • Capture the individual, incident date, incident type, host home provider, and days since the incident for each
    • Note whether the state required notification window for this incident type has already passed

    Done when Every open or overdue incident report is listed with its detail and deadline status.

  3. 2
    Slack - alert QA of overdue follow-ups
    slack.com
    WebRun in Slack: alert QA of overdue follow-ups
    WebRun opens Slack to alert QA of overdue follow-ups.
    • Post the overdue and at risk incident list to the QA channel, oldest first
    • Flag any incident within 24 hours of missing its state notification deadline

    Done when QA has today's incident follow-up worklist in Slack, sorted by urgency.

  4. 3
    Gmail - draft the guardian notification
    gmail.com
    WebRun in Gmail: draft the guardian notification
    WebRun opens Gmail to draft the guardian notification.
    • Draft the required guardian or family notification for each incident that has not yet been sent
    • Use the facts already logged in Therap: what happened, when, and what the home did in response
    • Save every draft unsent in Gmail. Do not send any incident notification to a guardian automatically

    Done when A Gmail draft exists for every incident still owed a guardian notification.

  5. 4
    Google Calendar - draft a follow-up review meeting hold
    calendar.google.com
    WebRun in Google Calendar: draft a follow-up review meeting hold
    WebRun opens Google Calendar to draft a follow-up review meeting hold.
    • Draft a follow-up review meeting hold for each incident that needs a documented root cause or corrective action
    • Leave the hold tentative with no attendees invited. Do not send meeting invites automatically

    Done when A tentative review meeting hold exists for every incident still needing a documented follow-up.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.therapservices.net
ScheduleRuns automatically on this cadence
Every morning at 7:00 AM
DeliveryHow each run's result reaches you
Incident worklist · Slack
OutputWhat each run produces - An overdue incident worklist in Slack, a guardian notification draft in Gmail per incident, and a tentative review meeting hold per open incident.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it notify guardians about an incident without approval?

No. Every guardian notification is saved as a Gmail draft for your QA lead or supervisor to review, edit, and send. WebRun never contacts a guardian on its own.

How does it know an incident still needs follow-up?

It reads the live incident record in Therap each morning and checks whether a follow-up entry, root cause, or corrective action has been logged. Anything missing stays on the worklist.

What if an incident is close to missing its state notification deadline?

It flags any incident within 24 hours of its required notification window at the top of the Slack list, so QA can act before the deadline passes.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.