Automated Missed-Service Recovery
Every morning, WebRun opens Tank Track, finds grease trap jobs that were scheduled for the previous day but never marked complete, drafts a fresh work order to reschedule each one, prepares a short apology text in Twilio for every affected customer, and posts your dispatch team a Slack recovery list so nothing falls through.
How do I recover missed grease trap visits with follow-up work orders automatically?
WebRun opens Tank Track every morning, finds grease trap jobs scheduled yesterday that were never completed, and drafts a fresh work order to reschedule each one. It queues a polite apology text in Twilio for every affected customer and posts your dispatch team a Slack recovery list, so missed visits are recovered while a human approves each booking and message.
- Missed visits are caught the next morning, not weeks later at billing
- Every skipped job gets a drafted reschedule and a queued apology text
- Repeatedly missed accounts are escalated to a supervisor in Slack
Built for grease trap haulers · pump truck dispatchers · liquid waste operators · field service 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
tank-track.comin a real browser with your saved login - no setup, no API keys. -
1
Tank Track - find missed jobs
WebRun opens Tank Track to find grease trap jobs that were missed. - Open Tank Track and list grease trap jobs scheduled yesterday that are not marked complete
- Capture the site, contact, original date, driver, and reason if one is noted
- Draft a new work order to reschedule each missed job at the next suitable slot
- Leave each new work order in draft so dispatch can confirm the date before it commits
Done when Every missed job has a drafted reschedule work order with a proposed new date.
-
2
Twilio - draft the apology text
WebRun drafts an apology text in Twilio and leaves it queued for approval. - Draft a short, polite apology text for each affected customer noting the missed visit and the proposed new date
- Invite the customer to reply to confirm or ask for a different time
- Queue every text in Twilio but leave it unsent for dispatch to review
- Never text a customer about a missed visit without a human approving it
Done when An apology text is drafted and queued for review for every affected customer.
-
3
Slack - post the recovery list
WebRun posts the missed-visit recovery list to Slack for dispatch. - Post a recovery list to the dispatch Slack channel with every missed job, the customer, and the proposed new date
- Flag any account missed twice in a row so a supervisor can step in
- Note which reschedule work orders are drafted and awaiting confirmation
Done when Dispatch has a Slack recovery list covering every missed job and its next step.
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
Will it text customers or commit the new booking on its own?
No. WebRun drafts the reschedule work order and queues the apology text in Twilio, then leaves both for dispatch to confirm. No customer is texted and no new date is committed until a human approves it.
How does it know a job was missed?
It reads Tank Track each morning for jobs scheduled the previous day that are still not marked complete, so any visit that was skipped, cut short, or left open shows up on the recovery list.
What about accounts that keep getting missed?
It flags any account missed twice in a row in the Slack recovery list so a supervisor can intervene before the customer is repeatedly let down.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.