Guardian Callout sends a recall to the people you tagged — a SWAT team, a shift, an overtime list — and tracks every reply on one live board. No phone tree, no group text, no guessing at your headcount.
Recalls still run on phone trees and group texts. The message goes out, replies scatter across a dozen threads, and the commander is left counting heads by hand while the clock runs. Guardian Callout turns that into one send and one board.
Organise personnel into the groups you actually call — SWAT, snow ops, a specific shift, dept-wide. Send to a tag, not a hand-picked list.
Personnel answer by text: coming, unavailable, or en route with an ETA. Replies attach to the right callout automatically.
Watch the board fill as answers arrive, with running counts of who is coming, who is out, and who has not answered yet.
People join through a single-use link tied to their own number and confirmed with a one-time code — so the roster reflects who really consented.
Guardian Callout records status, not position. There is no responder GPS to collect, store, or explain to a union — and no location permission to ask for.
Every callout keeps an immutable record of who was contacted, when, and how they answered. Export it when a contract or a review requires it.
Pre-build the callouts you send under pressure so triggering one takes seconds rather than careful typing.
Personnel messaging runs on its own number and its own opt-out list. A resident texting STOP can never remove an officer from a recall.
Build the roster once and tag people by team, shift, or speciality.
Pick a tag, pick a template or write the message, and fire the callout.
Replies land on a live board with running counts as they arrive.
The full contact-and-response record is retained and exportable.
No. Enrolled personnel are roster records, not user accounts — they receive and answer callouts entirely by text. The console is for supervisors and administrators.
Through a single-use enrollment link bound to their own phone number and confirmed with a one-time code, alongside a supervisor attestation that a signed agreement is on file.
No. It records response status and ETA only. No responder location is collected or stored.
Yes. Each callout retains who was contacted, in what order, when, and how they replied, and that record can be exported.
No — SMS is best-effort by nature, and Guardian Callout should be one mechanism in your recall plan rather than the only one. Delivery and response are logged so you can see what actually happened.
No. Callout is staff-only and runs on separate messaging from anything citizen-facing, with its own opt-out list.
Book a 20-minute Guardian Callout demonstration and see a muster tracked end to end.