Automated Produced Water Pickup ETA Texts
Every few minutes, WebRun checks Engage Mobilize for newly dispatched produced-water hauls, works out each pickup ETA from the truck's assignment and route, drafts a short operator text in Twilio, and posts the queued messages to Slack for a dispatcher to approve before any text is sent to a lease operator.
How do I automatically notify operators of a produced water pickup ETA?
Every few minutes, WebRun checks Engage Mobilize for newly dispatched produced-water hauls, estimates each pickup ETA from the truck and route, and drafts a short operator text in Twilio. It queues every message in Slack for a dispatcher to approve, so operators get an accurate heads-up but no text is sent without a human signing off.
- Operators get an accurate pickup ETA without a dispatcher typing it
- No text reaches an operator without human approval
- Each dispatched load produces at most one ETA draft
Built for oilfield dispatchers · produced water haulers · lease operators · fluid logistics 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.engagemobilize.comin a real browser with your saved login - no setup, no API keys. -
1
Engage Mobilize - find dispatched hauls and ETAs
engagemobilize.com
WebRun finds dispatched produced-water hauls and their ETAs in Engage Mobilize. - Open Engage Mobilize and find produced-water hauls dispatched since the last run
- Read the assigned truck, lease, tank, and scheduled pickup window for each
- Estimate the pickup ETA from the truck's current assignment and typical route time
- Skip any haul whose operator was already notified for this pickup
Done when Every newly dispatched produced-water haul has a pickup ETA and the operator contact on file.
-
2
Twilio - draft the operator ETA text
twilio.com
WebRun drafts each operator ETA text in Twilio and leaves it unsent. - Draft a short, plain text for the lease operator with the tank, the truck, and the pickup ETA
- Prepare the message in Twilio addressed to the operator's number on file
- Leave every message queued and unsent so nothing reaches an operator without approval
Done when A ready-to-send operator ETA text is drafted in Twilio for each haul, all unsent.
-
3
Slack - queue texts for dispatcher approval
slack.com
WebRun queues the ETA texts in Slack for a dispatcher to approve. - Post the queued ETA texts to Slack with the operator, lease, and pickup time for each
- Let a dispatcher approve, edit, or hold each message
- Send only the messages a dispatcher approves; hold the rest
Done when Dispatch has the queued ETA texts in Slack and only approved ones go out.
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 operators without my approval?
No. WebRun drafts every operator ETA text in Twilio and leaves it unsent, then posts the queue to Slack. A dispatcher approves, edits, or holds each message, and only approved texts are sent to a lease operator.
How is the pickup ETA calculated?
It reads the assigned truck, scheduled window, and typical route time in Engage Mobilize for each dispatched haul, then estimates when the truck will reach the tank. The ETA is included in the draft text for the operator.
Will an operator get texted twice for one pickup?
No. WebRun skips any haul whose operator was already notified for that pickup, so each dispatched load produces at most one draft text for approval.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.