Automated Bail Bond Exception and Incident Alerts
Every few minutes, WebRun opens Captira and scans for exception events: defendants flagged by Defendant Watch re-arrest alerts, defendants with two or more consecutive missed check-ins, payment failures on active plans, and bonds approaching forfeiture. It immediately posts urgent alerts to the agency Slack channel and Telegram so agents can act before situations escalate.
How do I get instant alerts when a defendant triggers a bail bond exception?
WebRun scans Captira every few minutes for high-risk exception events including re-arrest alerts, consecutive missed check-ins, payment failures, and defendants with court dates in 48 hours who have not checked in. It immediately posts urgent alerts to Slack for the assigned agent and a backup alert to Telegram for after-hours coverage, so no critical bail event goes unaddressed.
- Re-arrest alerts and critical exceptions surface in Slack and Telegram within minutes, not hours
- Agents on call receive Telegram backup alerts for after-hours exceptions so no event waits until morning
- Every exception is logged to Captira and the alert names the responsible agent, making follow-up immediate
Built for bail bond agency owners · bail bondsmen · bail bond compliance officers · surety agents
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
app.captira.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Captira - scan for exception events and risk flags
captira.com
WebRun opens Captira to scan for exception events and risk flags. - Open Captira and check the Defendant Watch and notification center for new re-arrest alerts
- Review the check-in compliance list for defendants with two or more consecutive missed check-ins
- Scan payment plan records for any payment that failed or returned in the past 6 hours
- Check the bond record for any defendant whose next court date is within 48 hours and who has not completed today's check-in
Done when All high-risk exception events in Captira are identified and categorized by type and severity.
-
2
Slack - post urgent exception alert to agency channel
slack.com
WebRun opens Slack to post urgent exception alert to agency channel. - Post an urgent alert to the agency Slack channel for each exception event, listing the defendant name, bond amount, event type, and recommended action
- Tag the assigned agent in each alert so they are notified immediately
- Use a distinct alert format for re-arrest events to make them visually distinct from check-in or payment exceptions
- Do not include sensitive case or financial details beyond what agents need to act
Done when Assigned agents and the manager have Slack alerts for every new exception event identified in this run.
-
3
Telegram - send backup alert to agent on-call
telegram.org
WebRun opens Telegram to send backup alert to agent on-call. - Send a backup alert to the agency Telegram group or the on-call agent for every re-arrest event and any bond with a court date within 48 hours
- Keep the Telegram message brief: defendant name, event type, and the assigned agent's name
- This ensures the alert reaches agents who may not be monitoring Slack outside office hours
Done when A Telegram backup alert has been sent for every critical exception event so after-hours agents are also notified.
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 take any action on the defendant or bond when it detects an exception?
No. WebRun only monitors and alerts. All actions on the defendant, bond, or indemnitor, such as contacting the defendant, initiating surrender proceedings, or notifying the surety, are taken by your agents after reviewing the alert.
How does it know if a defendant has been re-arrested?
WebRun reads from Captira's Defendant Watch notification center, which monitors re-arrest data nationwide. It does not perform its own law enforcement data lookups.
Can it distinguish between a check-in that is genuinely missed versus one that was manually waived by the agent?
Yes. WebRun only flags defendants who show as non-compliant in Captira's check-in records. If an agent has manually waived or rescheduled a check-in in Captira, that defendant will not trigger an alert on the next run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.