PR-2147 · Live
Issue Beacon
When a technician's check-in flags an unforeseen circumstance, Issue Beacon picks it up the moment it is reported. The right Field Supervisor gets a text with the facts, the customer or tenant contact is notified, a follow-up task is assigned, and the job is tagged for reporting. If no one responds in time, the next person in the chain is notified automatically. Site access issues, unsafe conditions, and unforeseen circumstances get handled the same day, without phone tag.
The promise
The Field Supervisor stops finding out about site access issues, unsafe conditions, and unforeseen circumstances at the end of the week. The platform surfaces them the moment the technician checks in, with the right people already notified.
How it works
The path from input to value.
- 01
The check-in flags an unforeseen circumstance
When a technician's check-in indicates an unexpected situation, such as a site access issue, an unsafe condition, or another unplanned circumstance, the platform picks it up immediately.
- 02
The right manager gets a text
Using configured message templates and escalation rules, the Field Supervisor receives a text with the relevant facts.
- 03
The customer or tenant is notified
The relevant customer or tenant contact receives a notification about the situation, keeping them informed without the manager having to make a separate call.
- 04
A follow-up task is assigned and the job is tagged
A follow-up task is created and assigned automatically, and the job is tagged for reporting, so the circumstance is traceable and nothing falls through without resolution.
- 05
The escalation ladder kicks in if there is no response
If the manager does not respond within the configured window, the escalation ladder activates and the next person in the chain is notified automatically.
The day before. The day after.
Same moments. Lived differently.
A technician checks in at a job site and finds a locked gate with no access code on the work order. They text the dispatcher. The dispatcher texts the Field Supervisor. Phone tag begins.
9:15 AMThe technician checks in and flags the access issue on the form. Issue Beacon picks it up immediately. The Field Supervisor receives a text with the facts. The customer is notified automatically.
9:15 AMBefore
A technician checks in at a job site and finds a locked gate with no access code on the work order. They text the dispatcher. The dispatcher texts the Field Supervisor. Phone tag begins.
After
The technician checks in and flags the access issue on the form. Issue Beacon picks it up immediately. The Field Supervisor receives a text with the facts. The customer is notified automatically.
The Field Supervisor learns about the access issue thirty minutes after it occurred. The technician has been waiting. The customer has not been notified.
9:45 AMThe follow-up task is already created and assigned. The job is tagged for reporting. The escalation ladder is on a timer in case no response comes.
9:45 AMBefore
The Field Supervisor learns about the access issue thirty minutes after it occurred. The technician has been waiting. The customer has not been notified.
After
The follow-up task is already created and assigned. The job is tagged for reporting. The escalation ladder is on a timer in case no response comes.
The follow-up task is created by hand after the situation is resolved. The job is tagged only if someone remembers to do it.
10:00 AMThe situation is resolved. The Field Supervisor marks it closed. The record is complete.
10:00 AMBefore
The follow-up task is created by hand after the situation is resolved. The job is tagged only if someone remembers to do it.
After
The situation is resolved. The Field Supervisor marks it closed. The record is complete.
Three site access issues this week, and none of them are traceable in reporting because the tags were inconsistent.
4:30 PMThree site access issues, all traceable in reporting with consistent tags. The pattern is visible for the first time.
4:30 PMBefore
Three site access issues this week, and none of them are traceable in reporting because the tags were inconsistent.
After
Three site access issues, all traceable in reporting with consistent tags. The pattern is visible for the first time.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Does not resolve the circumstance on the manager's behalf; the team closes it out.
- ×Does not reschedule or reassign jobs flagged with unforeseen circumstances automatically.
- ×Does not handle inbound responses from customers or tenants after notification.
- ×Does not apply to check-ins with no issue flagged.