GoTeam Dispatch Processes


The Go-Team dispatch process has been reworked as of 2018 Q1.  This document will give an overview of the process, what to expect when being dispatched, and how to respond to dispatch messages.

Key Points

  • Same message used for SMS (text message) and Email
  • Language has been standardized; all dispatch messages are the same
  • Removed ambiguous wording (“respond”, “drill” etc.)
  • Removed “this is not a drill”
  • All instructions fit in one SMS message – no getting pieces out of order and minutes apart!
  • Removed extended characters which were causing issues with Twilio

Sample Dispatch Messages

Sample Message

MCCERT Deployment, Highrise evac // Bohrer Park, 510 S Frederick Ave, Gaithersburg, MD 20877 // Reply if able to arrive by 0900 & deploy now

Message Breakdown

MCCERT <- Who we are
Deployment, Highrise evac <- Incident Type (and detail, if available)
Bohrer Park, 510 S Frederick Ave, 20877 <- Location (if applicable)
Reply if able to arrive by 0900 & deploy now <- Instructions

Incident Types Details, Usages, and Responses

Incident Types

There are currently five types of incidents for which Dispatch may contact members of the Go-Team.  They are:

  • Communications Test
  • Availability Check
  • Exercise
  • Deployment
  • Event

Incident Type Details & Responses

Communications Test

Used for testing CERVIS & Twilio operations

MCCERT Communications TEST // Reply with time message was received; DO NOT DEPLOY!

Sample Reply

Dave Mroz 1803

Availability Check

Used for gauging how many members we could theoretically deploy.  *IF* there was a deployment right now, would you respond?

MCCERT Availability Check // Bohrer Park, 510 S Frederick Ave, Gaithersburg, MD 20877 // Reply if able to arrive by 0900; DO NOT DEPLOY!

Sample Reply

Dave Mroz 1803

Exercise

Used for training exercises. May be announced or unannounced.

MCCERT Exercise, Highrise Evac // Bohrer Park, 510 S Frederick Ave, Gaithersburg, MD 20877 // Reply if able to arrive by 0900 & deploy now

Sample Reply

Dave Mroz 1803

Deployment

Used for real-world incidents when the Go-Team is requested by MCFRS, OEM/HS and/or MCPD. Always unannounced.

MCCERT Deployment, Highrise evac // Bohrer Park, 510 S Frederick Ave, Gaithersburg, MD 20877 // Reply if able to arrive by 0900 & deploy now

Sample Reply

Dave Mroz 1803

Event

Used for dispatching for an event you pre-registered for in CERVIS.  Always pre-planned and should be on your calendar!

MCCERT Event, Summerfest // Boher Park, 510 S Frederick Ave, Gaithersburg, MD 20877 // You registered & are expected; Reply & arrive by 1700

Sample Reply

Dave Mroz 1803

Off Duty Message

At the conclusion of one of the above incidents, dispatch will send a follow-up message only to those who deployed. Dispatch needs response to know you are safely off-duty, wherever that may be.  In most cases, the “off duty” message should be sent when you are safely back home, but this message can (and should) be send immediately after the conclusion of an incident if you not going directly home.  (For instance, you may be “off duty” immediately if you are going to dinner after an incident.)

MCCERT Deployment Complete // Reply with time off duty

Sample Reply

Dave Mroz 1803

How To Reply to Dispatch

  1. Read the dispatch message.
  2. Re-read the dispatch message
  3. Take a deep breath
  4. Read it again
  5. Type your reply

Notice that all of the replies are exactly the same.  The text can be send back to dispatch by replying to the email or the SMS, but the reply text should be the same regardless of the system you’re using or the message to which you’re replying.

Name & time (in 24-hour time). That it.

Sample Reply

Dave Mroz 1803

Final Reminders

MCCERT’s response time is [usually] 90 minutes and the CDO wont ask for the roster for at least 30-60 minutes after the initial dispatch message is sent, so you don’t have to reply the nanosecond the dispatch message arrives.  Please take a second to read and re-read the dispatch message to make sure you understand what’s being asked of you and formulate your reply accordingly.  If driving, please take care to stop your car somewhere safe before replying to the email or SMS.

Key Notes

  • One out, one in – One dispatch message, one reply
  • Reply via SMS or email, whatever is easier.
  • Only reply with your name and time. Dispatch knows what they sent out so they don’t need that information again
  • If you are unable to do whatever dispatch instructs, DO NOT REPLY.
  • No, “I can come later if you need me” – if we need a second wave, we’ll ask dispatch to send a second message
  • EVERYBODY who deploys MUST reply to dispatch (even if it’s outside the response time window)
  • Off-duty time is critical. Don’t forget to send it.
  • Do not “swing by” and event to see what’s going on; you’re either part of the effort or you’re at home, but don’t come a as a lookie-loo!