Automated HVAC Emergency No-Heat No-Cool Alerts
Every few minutes, WebRun checks ServiceTitan for newly created no-heat or no-cool emergency jobs, posts an immediate priority alert to your dispatch Slack channel with the job details and customer contact, and flags any unassigned emergency that has been waiting more than 15 minutes.
How do I get instant alerts for no-heat and no-cool emergency HVAC calls?
WebRun checks ServiceTitan every few minutes for new no-heat and no-cool emergency jobs. The moment one is created, it posts a priority alert to your dispatch Slack channel with the job details and customer contact. Unassigned emergencies that wait more than 15 minutes trigger a follow-up escalation so nothing slips through.
- Emergency calls are alerted to your dispatcher within minutes of being created
- Unassigned emergencies trigger an escalation after 15 minutes of inactivity
- No customer is contacted automatically. Your dispatcher stays in control
Built for HVAC dispatchers · heating and cooling contractors · HVAC service managers · on-call HVAC 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
go.servicetitan.comin a real browser with your saved login - no setup, no API keys. -
1
ServiceTitan - detect new emergency jobs
servicetitan.com
WebRun opens ServiceTitan to detect new emergency jobs. - Open ServiceTitan and check the job queue for new jobs created in the last few minutes
- Filter for jobs tagged as no-heat, no-cool, or emergency priority
- Capture the job number, customer name, address, contact number, equipment type, and time created for each
Done when All new emergency jobs created since the last check are identified with their details.
-
2
Slack - alert dispatcher immediately
slack.com
WebRun opens Slack to alert dispatcher immediately. - Post an immediate priority alert to the dispatch Slack channel for each new emergency job
- Include the job number, customer name, address, and contact number in the alert
- If the job has been unassigned for more than 15 minutes, post a follow-up escalation alert
- No message is sent to the customer. Alerts go only to your internal dispatch channel
Done when Dispatcher has an immediate Slack alert for every new no-heat or no-cool emergency.
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
Does it contact the customer when an emergency job is created?
No. Alerts go only to your internal Slack dispatch channel. No message is sent to the customer. Your dispatcher handles customer communication directly.
What counts as a no-heat or no-cool emergency job?
It looks for jobs in ServiceTitan tagged with your emergency job types, such as no-heat, no-cool, or emergency. You can configure the exact job type names to match your setup.
What happens if the dispatcher misses the first alert?
If the emergency job remains unassigned in ServiceTitan for more than 15 minutes, WebRun posts an escalation alert in Slack to prompt immediate action.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.