In-depth platform guide

Compare tools, modules, pricing, and deployment in one place.

This page goes deeper than the homepage overview. Review a full side-by-side product comparison, advanced modules by plan, deployment patterns, and live pricing when you are evaluating Sanctuary Signal with leadership or mapping it to radios, training, and compliance workflows you already use.

Built for mixed team profiles: off-duty law enforcement in uniform, visible team members with lanyards and discreet earpieces, and plain-clothes responders who coordinate in the background.

No app required. Works on the phones your volunteers already carry.

Coordinator managing church safety communications from a dispatch workstation

How Sanctuary Signal works

A quick walkthrough of check-in, on-duty visibility, direct messages, supervisor broadcasts, and end-of-shift review.

  1. Volunteer texts CHECKIN.
  2. Leader sees who is on duty.
  3. Team member sends a direct message using @Name.
  4. Supervisor sends a controlled broadcast.
  5. Leader reviews message history or the shift summary.

See product tour See SMS playbooks See full product comparison

Why teams standardize here

Designed for Sunday worship

Live worship demands discretion and reliability, not another social feed competing for attention.

Structured and accountable

Message history, broadcast control, and summaries help leadership debrief without guesswork.

Flexible deployment

TEXT works on any phone without installs - meeting volunteers where they already are.

What teams use today (and what breaks)

Many church safety teams combine texting with radios or headsets to keep communication discreet during service. Some also repurpose workplace chat tools for BOLO-style updates and coordination. In practice, teams patch together tools that were never designed for duty routing, authority controls, or accountability.

Notable signals we hear from church teams

  • Communication needs to stay discreet and non-disruptive during worship.
  • Many teams switch between texting and radios/headsets depending on the moment.
  • Open group threads are often avoided because they can get noisy and distracting.
  • Some teams use workplace chat for BOLO-style broadcasts, but it is not built for rotating volunteers.
  • The core need is fast coordination, clear on-duty status, and leadership visibility.

Why Sanctuary Signal is different than chat apps

  • On-duty routing: messages can target checked-in responders instead of blasting everyone.
  • Broadcast authority: leadership controls who can broadcast to reduce noise and confusion.
  • Accountability: message history supports review and follow-up.
  • Adoption: TEXT works on any phone without installs and fits volunteer rotations.

Why it's different than group texts

Purpose-built for discreet coordination-without sharing contact lists or noisy group threads.

No contact lists required

Team members don't need anyone else's number. Personal contact info stays private.

Messaging by name

Send a direct message using @Name. If there's more than one match, you'll be prompted to choose.

See who's on duty

Text STATUS to view who's checked in right now-no guessing, no calling around.

Structured & accountable

Role-based broadcast control plus message history for leadership review and follow-up.

Phone displaying an SMS dispatch alert for an on-duty church security responder.

Sanctuary Signal TEXT

SMS-first communication built for duty routing, broadcast authority, and accountability during worship. Use the live demo to see how check-ins, STATUS, supervisor broadcasts, and @Name routing read on a handset without installing an app.

Sanctuary Signal TEXT

Lightweight, dependable dispatch that works on any phone.

  • Day-1 ready: check-ins and supervisor broadcasts.
  • No app download / no Wi-Fi required.
  • Message teammates by name and see who's on duty instantly - even if you don't have their contact info.
  • Structured team control: role-based broadcasts capability + join approvals.
  • Admin-only console: team roster, message history, queue health, pending work.
  • Public dashboard for awareness; admin console for control.
  • Best for: volunteer rotations, low training, universal reach.

See product tour

Legend of yes and no icons used in the church security product comparison table.

Full product comparison

A practical view of how teams commonly coordinate today and where TEXT provides clearer duty routing, authority controls, and accountability.

Show/Hide product comparison
Capability Sanctuary Signal TEXT Group Texts WhatsApp / GroupMe / Band
Consumer group chat
Slack / Microsoft Teams
Workplace chat
Church mass-notification tools
Broadcast-first
No app required Yes Yes Usually no Usually no Usually yes
Works well for rotating volunteers Yes Usually no No No Usually no
On-duty routing (check-in/out; target only on-duty) Built in No No No No
Direct message by name (no contact lists needed) Built in No No Usually yes No
Broadcast authority controls Yes No Usually yes Usually yes Usually yes
Message history / accountability Yes No Usually no Yes Usually no
Incident workflows (assign / escalate / resolve) No No No No No
Dashboard and metrics Console No No No Usually yes
SMS fallback when app/push isn’t available Yes Yes Usually yes No No
Best fit Universal reach and low-friction coordination Same users always working together All users have deployed the app and have know how Staff workplace collaboration One-way alerts / broadcasts

Advanced modules by plan

Pricing starts with three simple plans. Medium includes Medic Routing and Language Packs. Large adds Private Shift Channels and the Watchlist Module. Language packs and redundant SMS delivery remain optional resilience upgrades when your leadership is ready.

Use this section to understand what each module does and when churches usually enable it. Start on the pricing page if you need the plan-first view.

Language Packs (EN/ES)

When it helps: You have volunteers or attenders who are more comfortable in Spanish than English (or the reverse), and you want scripted prompts, confirmations, and help text to read cleanly without improvised translation in the moment.

What you get: Bilingual message templates and UI-facing language paths so supervisors and members see consistent wording in the language your policy defines for that audience.

Medic Skill-Based Routing

When it helps: You handle enough medical traffic that everyone blasting MEDIC into the main duty thread creates noise, and you want the first reach to match the severity you are seeing (minor first aid versus clinician-level support).

What you get: Skill-based routing so simple bumps and sprains can go first to someone with basic first aid, while higher-acuity events can be steered toward paramedic-, nurse-, or physician-capable members when your roster includes those skills. The shift lead or supervisor on duty chooses the best destination from context (for example First Aid / CPR, Paramedic, Doctor / Nurse) instead of broadcasting the same alert to every checked-in volunteer.

Normal duty broadcasts remain available when policy calls for wider visibility.

Private Shift Channels

When it helps: Checked-in members need a quieter side thread for coordination that is not a wide open group chat, and a one-to-one DM is too tight when three or four people need to stay aligned.

What you get: Member-initiated private shift channels so end users can spin up a small-room conversation without pulling the whole roster into “everyone sees everything” mode. It is closer to a focused DM thread, but with more than two participants when the situation calls for it, while the main duty channel stays on operational rhythm.

Redundant SMS Providers

When it helps: You have already seen carrier throttling, regional outages, or high-traffic windows where a single provider is an unacceptable single point of failure for safety coordination.

What you get: A secondary outbound SMS path with automatic failover when delivery fails, plus the ability for an app owner or the supervisor on duty to switch or fail over on demand when they see risk building during service.

Watchlist Module (Suspicious Person Watch)

When it helps: You maintain a suspicious-person watchlist and want field teams to reference the same approved imagery and notes without trading files in unmanaged consumer threads.

What you get: Controlled watchlist distribution with room for an end user to flag a question to the shift supervisor about a selected entry (for example uncertain match or changing behavior), so leadership can respond without turning the main channel into an open debate.

Pair with your counsel on imagery, consent, and retention; the module is a delivery mechanism, not a substitute for local policy. Technical limits such as photo count still apply at checkout.

Watchlist access control flow · BOLO template demo · BOLO use case

Watchlist screenshots and supervisor alerts: watchlist access control · BOLO SMS demo

View Small, Medium, and Large plans

Deployment At A Glance

Your team already has plans, schedules, and training. Sanctuary Signal can be the SMS communication layer that makes them actionable during live services - especially for volunteers who will not download another app or reliably monitor push notifications. Deployments focus on fast onboarding, clear role ownership, and structured communication paths. Teams can launch with TEXT first, then add richer workflows as ministry needs evolve.

Many campuses also want Sanctuary Signal to sit alongside tools they already use for compliance documentation, incident review, and team training. We can map that fit during onboarding without locking you into a single-vendor stack.

Guides and Operational Resources

Explore comparison guides, use-case workflows, and templates to plan your team’s communication model.

TEXT Pricing

Small, Medium, and Large. Medium is the recommended plan for most churches. See the dedicated pricing page for plan comparisons, and overage examples.

Sanctuary Signal TEXT

Structured SMS coordination with predictable monthly pricing.

*Monthly active users are unique users who check in or send/receive messages during the month. Billing is based on monthly active users - not roster size, shifts, or days used. Product Owners can also be a user and excluded from monthly usage counts.*

Request more info

Tell us about your church team and how you coordinate today.