Automated Restoration Loss Intake Routing
Every few minutes, WebRun checks Next Gear DASH for newly logged losses, reads the loss type, location, and urgency, matches the job to the right crew lead based on your routing rules in Google Sheets, and posts that lead a Slack alert with the full job details.
How do I automatically route new restoration losses to the right crew?
WebRun polls Next Gear DASH every few minutes for newly logged losses, matches each one to the right crew lead using your routing rules in Google Sheets, and sends that lead an instant Slack alert with the full job details. Unmatched losses are posted to the dispatch channel so no job goes unassigned.
- New losses are routed to the right crew lead within minutes of intake
- No job sits unassigned while a dispatcher is unavailable
- Routing rules update instantly when you edit the Google Sheet
Built for water damage restoration companies · fire and smoke restoration contractors · mold remediation firms · restoration dispatch managers
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
app.nextgearsolutions.comin a real browser with your saved login - no setup, no API keys. -
1
Next Gear DASH - detect new losses
nextgearsolutions.com
WebRun opens Next Gear DASH to detect new losses. - Open DASH and check the job queue for losses added since the last run
- Capture the loss type, address, reported damage, and any notes for each new job
- Note the urgency level and any TPA or insurance carrier assignment
Done when Every new loss since the last check is listed with full intake details.
-
2
Google Sheets - look up routing rules
google.com
WebRun opens Google Sheets to look up routing rules. - Open the crew-routing sheet and match the loss type and zip code to the correct crew lead
- Read the lead's name, Slack handle, and on-call status
- Flag any loss type that has no matching routing rule so a manager can assign manually
Done when Each new loss has a matched crew lead or a manual-assignment flag.
-
3
Slack - alert the assigned crew lead
slack.com
WebRun opens Slack to alert the assigned crew lead. - Post a direct Slack message to the matched crew lead with the job address, loss type, and intake notes
- Post unmatched losses to the dispatch channel for manual assignment
- Include a link to the DASH job so the lead can accept immediately
Done when Every new loss has been routed and the crew lead has a Slack notification.
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
What happens if no crew lead matches the loss type or location?
WebRun flags the loss and posts it to your dispatch Slack channel for manual assignment, so no job sits unrouted.
How do I update routing rules when crew coverage changes?
Edit the routing Google Sheet directly. WebRun reads it on every run, so changes take effect immediately without any reconfiguration.
Does it work with TPA-dispatched losses from carriers?
Yes. WebRun reads all new jobs in DASH regardless of source, including TPA and direct intake, and routes each one against your rules.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.