Dispatch Automation Settings: Confirmation Windows

About Confirmation Windows

The Confirm Window 1 & 2 settings make sure that responders who are close aren’t excluded simply because responders who are farther away reply to the alert more quickly.

When dispatchers send out Broadcast Alerts, responders are asked to self-report their ETA to the Incident Location. But the reality is, you can only wait for so long. This is where Confirmation Windows 1 & 2 come into play.

Using the Settings shown here, following are three examples that demonstrate how the Confirmation Windows work in conjunction with the Preferred ETA setting.

(Please note: The Confirmation Window 1 & 2 settings work the same whether you’re responding through the Beacon Mobile App or via SMS.)

Example 1

Confirmation Window 1 = 3 mins
Responder ETA > Preferred ETA

In this scenario, Confirmation Window 1 opens at 12:00, when the Broadcast Alert is sent out, and will stay open for 3 minutes.

The responder shown here replies to the Broadcast Alert at 12:01, with an ETA that’s greater than the Preferred ETA of 10 minutes, so Beacon asks the responder to Please standby: 2 minutes.

At 12:03, Confirmation Window 1 closes, so Beacon has to decide if it’s going to assign the responders or tell them they’re not needed.

Though the responder can’t see what happened, Beacon tells them they’re not needed — at 12:02 Beacon found another responder with an ETA of 3 minutes, reaching the maximum number of responders that Beacon can assign itself to this incident.

Example 2

Confirmation Window 2 = 5 mins
Responder ETA > Preferred ETA

In this scenario, Confirmation Window 1 opens at 12:00, when the Broadcast Alert is sent out, and but then closes 3 minutes later at 12:03. If Confirmation Window 1 closes and Beacon hasn’t met the Assigned Responders maximum limit, Confirmation Window 2 opens.

The responder shown here replies to the Broadcast Alert at 12:04, with an ETA that’s greater than the Preferred ETA of 10 minutes, so Beacon asks the responder to Please standby: 1 minutes.

At 12:05, Confirmation Window 2 closes (5 minutes after the Broadcast Alert was first sent out), so Beacon has to make a final decision if it’s going to assign the responders or tell them they’re not needed.

In this scenario, Beacon tells the responder to “Proceed to Location” — there were no other responders with a shorter ETA, and when Confirmation Window 2 closes, Beacon will no longer be accepting replies.

Example 3

This diagram demonstrates multiple responders replying to the same incident at different times:

Summary

In short, the Confirmation Windows, in combination with the Preferred ETA, make sure that:

  1. The closest responders are always assigned
  2. The farthest responders are only assigned when there isn’t enough help close by
  3. And neither of them are prematurely dismissed

If you think this could all be done more easily with GPS, we agree. The problem is not everybody has GPS (or Internet or smartphones) and we don’t want you to have to exclude any one who can help.

 

Return to the Dispatch Automation page

Recent Posts

Send us an email to share how you think Beacon can help your service.