Notifications and delivery

Before sending

Configure the organization’s SMS, email, and voice channels with support. A member’s phone number or roster entry is not permission to send messages. Obtain channel-specific consent and preserve evidence of how it was collected.

Send a facility update

1. Confirm the active organization in your admin workspace.
2. Review the affected area, schedule, and override before publishing.
3. Select the relevant topic and subscribed audience. Review the message preview and channels.
4. Submit the update once, then check the notification log.

Members can choose topics and available channels in their notification preferences. Whole-facility alerts use the facilityOverride topic; area and custom-topic identifiers come from the organization’s notification options.

Understand delivery

Queued means work is waiting. Provider acceptance does not mean the recipient has received or read a message. Delivery receipts can arrive later, and channel-specific outcomes differ.

The delivery workflow journals attempts to reduce duplicate sends. Confirmed failures can be eligible for an administrator retry. Ambiguous outcomes need investigation before retrying, because the original message may already have been accepted. Do not repeatedly submit the same send request after a timeout.

SMS preferences and support

Recipients can reply STOP to the sending number to stop texts. For help, contact support@facilipulse.com. The facility must ensure its messaging profile’s HELP response and opt-out handling match its published disclosures. Email preferences and unsubscribe links are separate from SMS opt-out.

See Messaging terms and Privacy.

Scope of the feature

Voice notifications are outbound calls using the configured provider and message content. These docs do not promise direct integration with facility loudspeakers or automatic lightning detection. Staff remain responsible for emergency procedures and closure decisions.