Choosing a channel
Why SMS, not an app, for a security crew
Every scheduling app assumes the workforce opens it. That's a fine assumption for an office. It's a worse one for a crew that works nights, doesn't sit at a desk, and — like most hourly and contract workforces — treats a new work app as one more thing to maybe get around to installing. Here's the actual evidence, not just the intuition.
What the evidence on deskless-worker adoption actually shows
- Not everyone has a data plan to spare. Pew Research (fielded 2025) found roughly 1 in 6 U.S. adults are "smartphone-only" internet users — they own a phone but have no home broadband — and that group skews toward lower-income households, the same income band as median security-guard pay. An app that assumes always-on data and app-store access isn't a neutral choice for that group; SMS costs nothing extra to receive and needs no data plan to read.
- Frontline workers say the quiet part out loud. Deskless-workforce research consistently finds a large share of frontline workers would rather not install "yet another standalone app," and cites complicated access as one of the top-named adoption barriers by frontline leaders themselves — not a guess about worker behavior, a stated preference.
- Text-first isn't a security-industry idea — it's proven in an adjacent one. TeamSense, a text-first product built for manufacturing shift workers, built its whole product around avoiding a mandatory work-app install specifically because BYOD-style app requirements meet real resistance from hourly workers on personal phones — and reports full adoption specifically on its SMS-based feature. Security crews look a lot more like a manufacturing shift floor than an office roster.
No study specific to security guards was found — this is deskless/frontline workforce evidence generally, applied to a workforce that fits the same profile, not a security-specific study.
Which competitors actually offer SMS, and under what constraints
Worth getting precisely right, because "does it text?" and "can a guard do everything by text?" are very different questions.
| Product | SMS capability | The catch |
|---|---|---|
| Deputy | Real, two-way | Shift-confirmation texts (accept/decline) are on by default; general notification SMS is off by default and both carry per-message cost once used. A guard confirms or declines a shift dispatch sends them — they don't browse and choose among open posts by text. |
| Belfry | Two-way (claimed) | Marketing copy describes a reply-to-claim flow; no independently verified plan-tier or pricing detail was found beyond the vendor's own description — verify directly with Belfry before relying on specifics. |
| Connecteam | One-way only | Broadcast reminders and updates with a paid monthly allowance — no documented way for a guard to reply and claim anything by text. |
| When I Work | One-way notification | Delivers the schedule to a phone that isn't logged into the app; no documented reply-to-accept flow. |
| TrackTik / Trackforce | Two-way (reported) | Reply Y/N to a dispatched offer — dispatcher-initiated, not browse-and-claim. |
| Celayix | Notification only | Texts tell a worker a shift is available; claiming happens back in the app. |
| WinTeam, Shiftboard, Nowsta, LASSO | No reply-to-claim SMS found | — |
Deputy in particular has real, working two-way SMS — the honest differentiation isn't "who has texting," it's browse-and-claim across the whole eligible pool versus one dispatched offer at a time. See the full Deputy comparison for that distinction in detail.
How NabShift runs on SMS, specifically
The full loop, not just notifications
Claiming (CLAIM ARMORY), dropping, checking in, and getting shift details all work over plain SMS — not a text that tells you to open an app to finish the action.
Broadcast to the eligible pool
Every qualified, opted-in guard for a post gets the text at the same time; first valid claim wins. Nobody is waiting on a dispatched offer to reach them specifically before they even know a post exists.
Consent and compliance, one choke point
Every outbound message passes through the same consent gate, and STOP is always honored. If you're evaluating TCPA/A2P 10DLC compliance for workforce texting specifically, that's covered in detail on our SMS Terms page rather than repeated here.
Show us one difficult shift
Bring us the shift your crew struggles to fill because half the roster never opens an app. We'll show you how it runs entirely by text.
Show us one difficult shift Try the live demoor email hello@nabshift.com directly