PR-2147 · Live

Issue Beacon

When a technician's check-in flags an unforeseen circumstance, the right manager gets a text with the facts, the customer or tenant contact gets notified, a follow-up task is assigned, and the job is tagged for reporting. Unforeseen circumstances get handled the same day without phone tag.

Built for

Field Supervisor

the person it works for

Processes

Job

one unit of work

Priced

15 rivets

per job

Returns

3 min

back to the field supervisor

3 min × $18/hr

$0.90

Returned Each Run

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.

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 an unforeseen circumstance, the platform picks it up immediately.

The right manager gets a text

Using configured message templates and escalation rules, the Field Supervisor receives a text with the relevant facts.

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.

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.

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.

Before

After

Technician checks in at a job site. Finds a locked gate with no access code on the work order. Texts the dispatcher. Dispatcher texts the Field Supervisor. Phone tag begins.
9:15 AM
Technician checks in and flags the access issue on the form. IssueBeacon picks it up immediately. Field Supervisor receives a text with the facts. Customer is notified automatically.
9:15 AM
Before
Technician checks in at a job site. Finds a locked gate with no access code on the work order. Texts the dispatcher. Dispatcher texts the Field Supervisor. Phone tag begins.
After
Technician checks in and flags the access issue on the form. IssueBeacon picks it up immediately. Field Supervisor receives a text with the facts. Customer is notified automatically.
Field Supervisor learns about the access issue thirty minutes after it occurred. Tech has been waiting. Customer has not been notified.
9:45 AM
Follow-up task already created and assigned. Job tagged for reporting. Escalation ladder on a timer in case no response comes.
9:45 AM
Before
Field Supervisor learns about the access issue thirty minutes after it occurred. Tech has been waiting. Customer has not been notified.
After
Follow-up task already created and assigned. Job tagged for reporting. Escalation ladder on a timer in case no response comes.
Follow-up task created manually after the situation is resolved. Job tagged only if someone remembers to do it.
10:00 AM
Situation resolved. Field Supervisor marks it closed. The record is complete.
10:00 AM
Before
Follow-up task created manually after the situation is resolved. Job tagged only if someone remembers to do it.
After
Situation resolved. Field Supervisor marks it closed. The record is complete.
Three site access issues this week. None traceable in reporting because tags were inconsistent.
4:30 PM
Three site access issues, all traceable in reporting with consistent tags. Pattern visible for the first time.
4:30 PM
Before
Three site access issues this week. None traceable in reporting because tags were inconsistent.
After
Three site access issues, all traceable in reporting with consistent tags. Pattern 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
×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