Automated FIELDBOSS Entrapment Dispatch
The moment an entrapment or shutdown call arrives in FIELDBOSS, WebRun reads the site, unit, and severity, finds the nearest qualified on-call technician, drafts a dispatch SMS in Twilio, and posts your dispatcher a Slack alert to approve and send within seconds.
How do I dispatch the nearest technician to an elevator entrapment fast?
The moment an entrapment or shutdown call hits FIELDBOSS, WebRun reads the site, unit, and severity, finds the nearest qualified on-call technician, and drafts a dispatch SMS in Twilio. It posts your dispatcher a priority Slack alert to approve the send, so the right tech is moving within seconds and a person always confirms.
- The nearest qualified tech is chosen in seconds, not minutes
- A dispatcher approves every emergency text before it sends
- A backup tech is always named for instant reassignment
Built for elevator service contractors · dispatchers · field-service teams · on-call coordinators
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.fieldboss.comin a real browser with your saved login - no setup, no API keys. -
1
FIELDBOSS - read the emergency call
WebRun opens FIELDBOSS to read the entrapment call. - Open the new service call in FIELDBOSS and confirm it is an entrapment or shutdown
- Read the building, unit ID, contact, and reported severity
- Check the on-call roster and pull the nearest technician qualified for that equipment
Done when The emergency call is matched to the nearest qualified on-call tech.
-
2
Twilio - draft the dispatch SMS
WebRun drafts the dispatch SMS in Twilio, unsent. - Draft an SMS with the address, unit, contact, and reported issue
- Address it to the chosen technician's mobile number
- Leave the message queued and unsent for your dispatcher to approve. Never text the tech automatically
Done when A dispatch SMS is drafted and queued for approval.
-
3
Slack - alert the dispatcher to send
WebRun alerts the dispatcher in Slack to approve the send. - Post the dispatcher a high-priority alert with the call and the chosen tech
- Show the drafted SMS and a one-tap send-or-reassign choice
- Note the second-nearest tech as a backup
Done when The dispatcher has the call, the drafted SMS, and a send-or-reassign choice.
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 technicians without me?
No. WebRun drafts the dispatch SMS in Twilio and leaves it queued. Your dispatcher approves the send from Slack, so a person always confirms who is going to an entrapment before the text goes out.
How does it pick the right technician?
It reads the on-call roster in FIELDBOSS and the equipment on the call, then picks the nearest tech qualified for that unit. It also names a second-nearest tech so your dispatcher can reassign in one tap.
What if no on-call tech is qualified nearby?
It flags that in the Slack alert instead of guessing, listing the closest available techs by distance so your dispatcher can make the call and escalate if needed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.