Navigate to the Settings Page by clicking on the Settings Icon in the Profile Menu

The Settings page is separated into different sections (click on each section to skip to the explanation below):

  1. Dashboard Settings
  2. Broadcast Alert Settings
  3. Responder Tags
  4. Message Settings
  5. Resource Lists
  1. Admin Language — Set the language administrative pages will appear in
  2. Maps Providers — Pick which map provider you will use; these maps show up on both the Web Dashboard and in the Mobile App for responders. Only Google Maps allows satellite view
  3. Catchment Area Latitude/Longitude — This setting is used to set the default map view for both the Web pages and the Beacon mobile app. (If the map already has your position set, this was likely done when you first created your account.) To set/update the default map view:
    1. Click the Drop Down next to the Latitude / Longitude coordinates to set the position of your map.
    2. Point and click to place the marker where you would like to center the map
    3. Click Save
  4. Time Zone — Use this drop-down to set the correct time zone for your service. Your time is based on UTC / GMT time zone. (Link to Time Zone calculator)
  5. Data Center On? — To create incidents and send messages to responders listed in this data center, this must be set to “Yes”. Changing this setting to “No” will prevent any incidents from being created
  6. Incident Numbering — Enter the number you would like your Incidents to start with. By default, Incidents will start numbering with “1”

Broadcast Alerts allow you to “crowdsource” Responders – similar to how Uber and Lyft crowdsource taxi drivers. Broadcast Alerts help response networks with large pools of Responders to improve response times, resource allocation, and response coverage.

Included here is a brief description of how they work — but please keep in mind that these settings can be used in a variety of different combinations, so you we urge you to read a more in-depth discussion of the different Broadcast Alert settings here.

  1. Maximum Number of First Responders (FRs) per Incident — Sets the limit on how many Responders can be assigned to each incident. This is a default setting and can be changed when creating a new incident
  2. Preferred ETA — Determines which Responders are preferred for an incident based on their ETA. When set at 10 minutes, Responders with an ETA of 10 minutes or less will be assigned to the incident; Responders with an ETA greater than 10 minutes will be told to standby.
    • Check out these scenarios and diagrams to see more examples of how the Preferred ETA works
  3. Confirmation Window 1* — The least amount of time (in minutes) you are willing to wait for Responders to reply to a Broadcast Alert from Beacon
  4. Confirmation Window 2* — The most amount of time (in minutes) you are willing to wait for Responders to reply to a Broadcast Alert from Beacon
  5. Custom Incident Labels — Allows managers to customize the Incident Class, Category and Type labels that appear on the Create Incident page – e.g, “Emergency – Trauma: Motor Vehicle Collision”. (Read more here)
  6. Default Dispatch Type — Set the default setting for “Dispatch Type” on the Create Incident panel

*For urban environments, the standard preferred ETA is 10 minutes or less. For rural environments, the standard preferred ETA is likely 20 minutes or more, depending on how many responders there are and how big your catchment area is.

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 learn more about the importance of Confirmation Windows read more here.

Read More

This is where you can create and save the different Tags your agency uses to organize responders — for example, according to neighborhood, zone, skill, seniority, role, equipment etc.

Click here to learn more about how to use Responder Tags.

  1. Beacon Gateway Number* — The phone number that Beacon uses to send and receive SMS messages to/from Responders in this Data Center. Responders who are using the SMS interface must communicate with Beacon using this number. All Responders should save this number as a contact in their mobile phone and assign a unique ringtone and vibration to it so that they can distinguish SMS messages coming from Beacon
    • Note: This is not a public access number — like 911, 112, 999 etc. This number is for Responders only, not to be shared with the public or published on the internet
  2. Outgoing Message Server* — Displays which SMS Gateway is being used to send messages to Responders (Twilio, Nexmo, Beem Africa, etc.).
  3. Supervisor Notices — This link takes you to a screen that allows you to add people who will receive Initial Alerts for each incident created via SMS, but are not Responders. Unlike Responders, the same phone number can be added to the Supervisor Notices List in as many different Data Centers as you have access to
  4. Restrict Active Incident Visibility — If set to “Yes”, Responders will only be able to see Active Incidents in the mobile app when they are assigned to that Incident. If set to “No”, Responders will be able to see all Active Incidents in the mobile app, whether or not they’ve been assigned to them

*Indicates settings that can only be changed by Trek Medics staff.

  • SMS Dispatcher List — Add and manage phone numbers enabled for creating new incidents via SMS. (See pages: Create SMS Dispatchers and Create Incidents by SMS)
  • Unregistered Parties — Shows SMS messages sent to Beacon from numbers not registered as responders with Beacon. (This includes members of the public who texted the wrong number, responders who accidentally used a different SIM on the same phone, or even marketing spam messages)

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

Not readable? Change text. captcha txt