• Dispatcher
  • Responder
  • Videos
  • FAQ
  • Status
  • ES
  • Ukrainian
  • Dispatcher
  • Responder
  • Videos
  • FAQ
  • Status
  • ES
  • Ukrainian

User Resources

home/Documentation/User Resources
  • Dispatcher Resources
    • Getting Started
      • Dashboard Navigation
      • Profile Menu
      • Responders Panel
      • Active Incidents Panel
      • Settings (ᵐ)
    • Key Functions
      • Add and Edit Responders (ᵐ)
      • Select Responder Type (ᵐ)
      • Add and Edit Web Users (ᵐ)
      • Map Layers
      • Transport Options
        • Add Transport Destinations
        • Arrival Notifications
      • Map Editing
      • Chats Feature
      • Push-To-Talk
      • Create Incident Panel
        • Creating Incidents
        • Pending Incidents Feauture
        • Dispatch Mode (previously called Incident Priority)
        • Alert Types (previously called Dispatch Types)
        • Responder Tags
        • Assigning Responders
        • Custom Incident Labels (ᵐ)
      • Dispatch Automation
        • Broadcast Alerts
        • Preferred ETA
        • Confirmation Windows
      • Monitoring Incidents
      • Dispatch Controller
      • Add Incident Disposition Codes
      • Add Dispatcher Incident Comments
    • SMS Functionality
      • SMS Chat Messaging
      • Add SMS Dispatcher (ᵐ)
      • Create Incidents by SMS
    • Reporting
      • Reports Automatically Generated by Beacon
        • Incident Reports
        • Summary Reports (ᵐ)
      • Documentation Manually Added by Responders
        • View Incident Notes (ᵐ)
        • Case Reports
    • More Dispatcher Resources
      • Practice Exercises
      • External Factors
  • Responder Resources
    • Mobile App interface
      • Beacon Mobile App Tour
      • Getting Started
        • Initial Sign In
        • Home Screen
        • SOS Feature
        • Map Features
        • Sidebar
        • Manage Responders
      • Response Workflows
        • Responder Types and Workflows
        • Incident Card Navigation
        • Incident Alert
        • En Route
        • Arrival On Scene
        • Additional Resources
        • Destination Transport
        • Arrival at Destination
        • Complete Incident
        • Response Times Summary
      • Documentation
        • Submit Incident Notes (Mobile App)
        • Case Reports
      • Other Features
        • Mobile App Chat
        • Push-To-Talk
        • Create New Incidents
        • Incident Dispatch Mode
        • Update the Incident After Creation
        • Interactive Notifications
        • Alerts Vibration for Beacon
        • Duty Scheduler
        • Special Permissions for Mobile App Users
        • Mobile App Settings
    • SMS Interface
      • Full Manual for SMS Users
      • SMS Code Index
      • Submit Incident Notes (SMS)
      • Requesting Additional Resources (SMS)
      • SMS Chat
    • Practice Exercises
  • Case Reports
    • Introduction to the Case Reports Feature
    • Setting Up Case Reports
    • Mobile App Case Reports Feature
    • Web App Case Reports Feature
  • GPS Settings & Tracking Services
  • Downloads
    • Web Dispatcher Cheat Sheet
    • Mobile App Responder: Patient Transport
    • Mobile App Responder: Response-only
    • Dispatcher Practice Exercises
    • SMS Responder: Response-only
    • Responder Practice Exercise
    • Alerts and Sound Settings
    • Dispatcher Guide Downloadable
    • Responder Guide Downloadable
    • Beacon Reporting Features Guide
    • Manager Assessment
  • Videos
  • Status

Confirmation Windows

Editing these Settings is only available for Managers

The Confirmation Window 1 & 2 settings serve two purposes:

  1. They set Minimum and Maximum time limits on how long Beacon will wait to receive replies to Incident Alerts from Responders
  2. They ensure that Responders who are close to an incident aren’t passed over simply because Responders who are farther away replied to the Incident 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, we’ve included 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 responders are using the Beacon Mobile App or SMS to complete their response)


Scenario 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.


Scenario 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 “Confirm En Route” because there were no other Responders with a shorter ETA, and when Confirmation Window 2 closes, Beacon will no longer accept replies.


Scenario 3:

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

FAQ: Why does the incident stay open after I complete it?

Incidents can be closed in three ways:

  1. All Assigned Responders complete the incident
  2. The Dispatcher cancels the incident manually
  3. Confirmation Window 2 closes and no other Responders are assigned

If you’re using Beacon to run simulations, it’s very likely you’re going to move through the incident very quickly — faster than in real life. This will result in you completing the incident before the Confirmation Windows close, so the incident will stay open until the Confirmation Windows close.

To read more Frequently Asked Questions, visit our FAQ page


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’d say it’s not as simple as it looks — crowdsourcing the nearest taxi driver is actually a lot easier than crowdsourcing emergency responders (and, as a rule of thumb, it’s not good for our profession to make that comparison).


In order to help dispatch operations, Confirmation Window’s timers will appear on the Beacon incidents tab for Immediate incidents.

These timers will display a count down of the remaining time for each Confirmation Window as selected in the Broadcast Alert Settings for your Beacon Agency Account.

  1. Timer 1 will display a count down of the remaining time before Confirmation Window 1 closes
  2. Timer 2 will display a count down of the remaining time before Confirmation Window 2 closes
Related Articles
  • Initial Sign In
  • Responder Types and Workflows
  • Pending Incidents Feauture
  • Duty Scheduler
  • Manager Assessment
Previous
Preferred ETA
Next
Monitoring Incidents

Dispatcher Resources

Responder Resources

Downloads

Status

Contact Us:

 [email protected]

 ENG +1.218.4 BEACON

(+1.218.423.2266)

 ESP +1.787.336.0123

*These are not emergency phone numbers.
In case of emergencies, please call your local emergency service.
  • Privacy Policy
  • Terms of Use
  • ©2025 TREK MEDICS INTL ALL RIGHTS RESERVED