becon-small-logo

Beacon SMS Workflows v4.0

First Responder Guide

Lea en Español

Software developed by:

Trek Medics International Logo

With the generous support of:

Twilio.org

About Beacon SMS Workflows in v4.0

Beacon v4.0 supports four different Responder Type workflows:

  1. Patient Transport
  2. Animal Transport
  3. Emergency Response only
  4. Transfers and Deliveries

Each Responder Type is sent all or some of the messages displayed here. Check the number next to each workflow header to see which messages are sent to which Responder Types.

1. Incident Alert 1-4

Responders receive a Request for Assistance from Beacon indicating the Incident ID (ID) and the Location of the incident. If a Responder can respond, they should reply with the Incident ID and the number of minutes it will take them to arrive to the location. The values must be separated by a ” . “ (see example at left). You will have between 2-3 minutes* from the moment the alert is created to confirm your participation. Depending on the Responder’s distance from the incident, they may be told to proceed to location, standby or that their participation isn’t needed.

*Actual times depend on your agency’s protocols and are set by your Administrator on the Beacon web pages (Read more here).

[New in Beacon v4.0]

2. En Route1-4

After you have been assigned to an incident:

  • Send  to inform dispatchers that you are on your way to the location
  • Send  to inform dispatchers that you have canceled your participation in the incident

3. On Scene1-4

  • Send  1   to Beacon when you have arrived at the scene of the incident and/or located the patient
  • Send  if you cannot locate the patient or the scene of the incident; Beacon will then inform the dispatcher to seek more information and update you via SMS Chat
  • Send  to cancel your involvement in the incident and make yourself available again to receive alerts for subsequent incidents.

4. Additional Resources1-3

The Responder to arrive on scene first is considered the “Incident Commander” (IC) and is given the option to request additional resources when needed. For example, one patient with a broken leg could be treated and managed by 2-3 Responders, while a bus accident with multiple casualties would need more help. In order to assist the decision-making process, the IC is told at the beginning of the text how many other Responders are currently en route (including yourself) and their estimated time of arrival in minutes (4 mins for Engine 6; “0” mins means Ambulance 414 is already on scene).

  • Send  if no additional resources are needed
  • If additional resources are needed, the Responder replies with the number of resources needed indicates the number needed — e.g., 4 if four more vehicles were needed. (Do not send #4 as # will not be acknowledged by the system)

5. Patient Transport1,2,4

Responders confirm that they are transporting patients by indicating the destination facility they’ll be transporting to, the number of patients they’ll be transporting, and their estimated time of arrival in minutes (ETA). In this case, there are four possible transport destinations (i.e., hospitals).

  • The Responder sends  for Georgetown Hospital,  to indicate they are transporting one patient, and  20  for their ETA in minutes. Always make sure that the values are separated by periods, as shown in the example at left.
  • Send  if no transport is needed

Note: Confirming transport will automatically send a notification text message to the receiving facility if your Administrator has set up a phone number for that facility in the Beacon web pages.

Note: For “Transfer/Delivery” Responder Types, the Transport Destination can include non-healthcare facility destinations, like private residences, shelters, pharmacies, etc.

6. Destination Arrival1,2,4

  • Send  to confirm when you have arrived at the destination facility
  • Send  2 , if you need immediate assistance from Dispatchers, Supervisors or Responders (for example, if you need a backup vehicles)
  • If  your transport is delayed, sends  followed by the expected delay time (in minutes). This text is forwarded to the destination facility.
  • Send  if you need to cancel your transport (rare, but possible)

[New in Beacon v4.0]

7. Complete Incident1-4

  • Send  if you need to add another transport leg or need to return to the scene. This will revert you back to Message 5: “Confirm Transport”
  • Send when you have completed the incident and are ready to become available again

8. Response Times Summary1-4

Once the Responder has completed the incident, they’ll receive a message providing their Response Times.

Additional SMS Functions

Log In / Log Out

  • To Log In: Send 123 to Beacon, then select which type of Transport you have
  • To Log Out: Send 456 to Beacon

SMS Chat

It’s possible to send chat messages to Web Dispatchers via SMS. Simply include 411 at the beginning of your message, and it will be sent to Web Dispatchers. Chat messages coming from Web Dispatchers via SMS will start with [411] . (This is to help you distinguish between chat messages sent via mobile app and SMS.)

Read more about SMS Chat and Mobile Chat here.

Responder Notes

It’s possible to submit and save incidents notes for any incidents that you’ve been assigned to. Simply start your message with the Incident ID in parentheses, and then write your notes after.

Read more about Incident Notes.

Don’t have an Agency Account yet?

Looking for more Beacon training?

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