Automated TazWorks Stalled Verification Escalations
Every morning, WebRun opens TazWorks, finds employment and education verifications with no response from the employer or school in more than 3 business days, posts the oldest stalls to Slack for escalation, and logs each one to a sheet so your researchers know exactly what to chase.
How do I escalate background check verifications that have stalled?
WebRun checks TazWorks every morning for employment and education verifications with no response from the employer or school past your set threshold, then posts the oldest stalls to Slack for a researcher to escalate. Each one is also logged to a sheet with the verifier's contact details and days silent, so nothing sits quiet until a client asks for status.
- Stalled verifications get escalated the same morning they cross the threshold
- Researchers work from a sorted list instead of scanning the full queue
- Verifier contact history is logged automatically, not tracked from memory
Built for CRA operations teams · background screening companies · verification researchers · screening 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.tazworks.comin a real browser with your saved login - no setup, no API keys. -
1
TazWorks - find stalled verifications
tazworks.com
WebRun opens TazWorks to find stalled verifications. - Open TazWorks and filter verifications still awaiting a response
- Compare each one's last contact date against your escalation threshold
- Note the verifier's name, phone, and contact method on file
Done when Every verification stalled past the threshold is listed with its last contact date.
-
2
Slack - escalate the oldest stalls
slack.com
WebRun opens Slack to escalate the oldest stalls. - Post the stalled verifications to the researcher channel, oldest first
- Tag the researcher assigned to each order
Done when Researchers have today's escalation list with the oldest stalls at the top.
-
3
Google Sheets - log the stall and next step
google.com
WebRun opens Google Sheets to log the stall and next step. - Log each stall with the verifier contact, last attempt date, and days silent
- Update the row once a researcher logs a new contact attempt
Done when The stalled-verification sheet reflects every open escalation and its history.
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 employer or school directly?
No. It only surfaces stalled verifications internally in Slack and logs them to a sheet. Any outreach to a verifier is made by your researcher, not WebRun.
What counts as stalled?
Any verification with no response from the employer or school past the contact threshold you set, based on the last attempt date recorded in TazWorks.
What happens once a researcher makes a new attempt?
The log updates with the new contact date, so a verification that's actively being worked doesn't keep escalating as if it were ignored.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.