Home Modules Scheduling & Operations — callouts
Scheduling & Operations · Callouts

Paging a roster, and tracking who answers.

Any event can be paged out to a roster by email and text at once. Responders answer without logging in, and every answer lands on one board while the rest are still arriving. Where the readiness board plans a week ahead, a callout covers tonight.

The dispatch board

One board, filling in as answers arrive

Every response, whether an email tap or a one-digit reply, posts to the same board with a timestamp. The people who haven't answered are as visible as the ones who have, so nobody reconstructs the count by scrolling back through a group text.

Windstorm activation Paged 4:12 PM · 22 members
9Responding 3Can't 10No answer
  • Dana Whitfield Text · answered 4:13 PM Responding
  • Marcus Reyes Email · answered 4:14 PM Responding
  • Priya Anand Text · answered 4:15 PM Can't make it
  • Tom Ochoa Text · delivered 4:12 PM No answer
  • Alicia Brandt Email · answered 4:19 PM Responding
Live as answers arrive. Anyone still showing no answer can be re-paged from here.

The dispatch board during an activation. Illustrative data.

TrainedResponder
Windstorm activation. EOC, 6 PM tonight. Reply 1 if you can respond, 2 if you can't.
1

A one-digit reply posts to the board.

  1. Email and text, together. Email carries a one-tap response link; text takes a one-digit reply. Members answer on whichever reached them first.
  2. Nobody has to log in to answer. The response link is tokenized, so a page at 9 p.m. doesn't depend on a member remembering a password.
  3. Everyone who responds is already on the roster for the event, so check-in and training credit pick up exactly where the callout left off.
Sending one

Sending a callout, start to finish

A callout is an action taken on an event rather than a separate tool beside the calendar, which is why the answers land on that event's roster.

Pick the event and the roster

A whole unit, a team, or a hand-picked list. Any event can be called out, whether it was on the calendar for weeks or created two minutes ago.

Email and text go out

Both channels at once, to whoever has each on file. Members who haven't confirmed contact details are held back rather than silently dropped.

Answers land on the board

Each response is stamped with how it came in and when. Re-page the silent ones in one action, without tracking who you already called.

Automatic

The roster builds itself

Everyone who said yes is already on the event's check-in roster, so hours and training credit follow from the activation with nothing re-entered.

Page the right people: the readiness board tells you who is qualified and likely around before you decide who gets the page. Availability is a hint, not a filter: a member who marked themselves off still gets paged and can still answer yes.
Mutual aid

Responders who aren't your members

A neighbouring CERT sends four people, a county employee works the shelter, a ham operator from the next district runs your net. They belong on the roster and on the hours report, but not in your membership, your training program, or your seat count.

  1. Recorded on the event, not in the directory. An outside responder is captured where they actually appeared, so they never become an account you have to deactivate later or a member your reports have to filter out.
  2. They count on the paperwork. Their hours land on the same activity report as everyone else's, which is what a state form or a grant asks for.
  3. Email yes, text never. They can be sent event information at an address they gave you, and are never added to an SMS callout. Consent to be texted is not something a sign-in sheet can transfer.
Outside responders Windstorm activation
  • Luis Navarro Riverbend CERT · mutual aid 5.5 hrsemail on file
  • Hana Kim County Public Works · agency staff 8.0 hrsemail on file
  • Ray Bergstrom District 4 ARES · mutual aid 5.5 hrsno contact given
On the roster and on the hours report. Not on the membership roll, and never on an SMS page.

Outside responders recorded against one activation.

Deliverability & compliance

SMS deliverability and consent

Most of what makes emergency SMS unreliable is regulatory rather than technical. These are the parts a carrier, or anyone reviewing your program, will ask about.

A registered A2P campaign

Messages go out over a carrier-registered 10DLC campaign rather than a consumer number relaying business traffic. Carriers filter unregistered senders heavily, and often without returning a delivery error.

Members opt in themselves

A member turns texting on from their own profile; phone lists are not imported and paged. STOP and HELP behave as carriers require, and stopping texts does not stop the email.

Pending members aren't paged

Someone part-way through joining has not confirmed their contact details yet. Until they do, operational email and SMS are held back rather than sent to an address or number that may not be theirs.

The full program disclosure — what we send, how often, and how to stop — is on the SMS policy page. Message and data rates apply.

Send a test page to your own phone.

Being on the receiving end of a callout tells you more than a screenshot does. We'll set that up on the call.