Community Notifications

Community Notifications sends automated SMS updates to 911 callers at key moments, like during a response, before officers arrive, when a response is delayed, and after contact is made. Keeping community members informed in real time improves transparency, sets accurate expectations, and supports safer encounters.

Community Notifications give administrators powerful tools to shape clear, timely communication with the public. Admins can customize message templates, define quiet hours, and set automated rules for pre-arrival, delayed-arrival, and post-contact messaging. The platform also offers full visibility into message history, ensuring every interaction can be reviewed and understood.

Community Notifications also integrates with other Axon Community products including Community Request, Community Forms, and Community Surveys. These integrations allow users to:

  • Upload evidence with Community Request prior to arrival
  • Complete digital forms such as statements with Community Forms
  • Provide feedback following the interaction with Community Surveys

Only agency administrators can access and configure Community Notification settings and integrations.

Overview

When a call for service is created in your CAD system, Community Notifications identifies the call type and sends the right message. Messages go to the phone number on the call and are automatically filled with real-time CAD data, with no extra steps for dispatchers or officers.

  • Pre-Arrival: Messages sent before officers reach the scene.
  • Delayed Arrival: Alerts triggered when response time exceeds an agency-defined threshold.
  • Post-Contact: Follow-up messages or survey links sent after the call is closed.

Watch this video to learn more.

Permissions

  • Administrator: Has full access to all features and settings within Notify.
  • Manage Template and Rules: Can manage message templates, links, call types, and all rule configurations within the system.
  • View / Export Message History: Cannot modify any settings or rules. This role is limited to viewing and exporting message history.

At launch, Community Notifications will be available to customers using a Fusus CAD Core integration and Axon Nexus. In 2026, additional connection options will be released, expanding access so all customers can take advantage of Notifications.

Settings and configuration

Master On/Off toggle

  1. Select the Admin tab.
  2. From Evidence Settings, select Community Notifications.

Administrators can manage a master toggle, which allows the agency to turn all messaging on or off without Axon support. While disabled, messages will not be queued or stored. When re-enabled, new messages begin sending immediately. Messages that would have been sent during the disabled period will be discarded and not delivered.

Post-contact quiet hours

Quiet hours prevent post-contact messages from sending during specific time periods (such as overnight).

  1. From the General Settings tab, select Post-Contact Quiet Time.
  2. Choose the desired start and end times.
  3. Any post-contact messages triggered during quiet hours will automatically queue and send once the quiet period ends.

Pre-Arrival and Delayed Arrival messages are not affected by quiet hours and will send based upon the specified timing if enabled.

Message templates

Templates define the content of each automated message, and agencies can create multiple templates based on their needs.

To create a new template:

  1. Select the Templates tab.
  2. Select Create Template.
  3. Enter a Template Name.
  4. Add message text (up to 800 characters).
  5. Insert Variables pulled from CAD data.
  6. Optionally, insert links.
  7. Select Save.
  8. Set the template status to Active.

Preview message templates

  1. Select Preview in the template view.
  2. Choose a verified user and send a test message.
  3. The preview message uses sample data.
  4. A confirmation message appears when the message sends successfully.
  1. Select Add Link.
  2. Enter a link name, description, and full URL.
  3. Save the link.
  4. Use the Insert Link dropdown when editing templates.

Manage Call Types and Message Rules

Importing Call / Incident Types

  1. Open the Call Type Manager tab.
  2. Download the call template (CSV).
  3. Add your agency’s CAD call type and a corresponding friendly name. The Friendly Name allows an agency to change the CAD Reference Name to a community distinguishable phrase. (Example. CAD: Call Type: SUSC Friendly Name: Suspicious Circumstance). The Friendly Name can be inserted into the templates as an available variable.
  4. Import the updated CSV back into the system.

Managing Rules and Message Types

  1. Select a call type and select the Edit icon.
  2. Activate the desired message types. Message types can be activated independent of other message types on a call (Example. Pre-Arrival Message active, but Delayed Arrival is disabled).
  3. Assign templates for each message type.
  4. Set message timing for Pre-Arrival, Delayed Arrival, and Post-Contact.
  5. Select Save.

Message History

The Message History tab provides a complete record of all notification activity.

  • Incident or call number
  • Message type
  • Call type
  • Recipient information and delivery status

Filters can be applied and records can be exported in formats including CSV, Excel, JSON, and PDF.

Permissions

Users with Admin, Manage, or View Message History access can view this information.

Disposition codes

Agencies using the Unified CAD (UCAD) integration can view disposition codes for CAD events directly within Community Notifications. Disposition codes reflect the outcome or classification of a dispatched call as recorded in your CAD system. When a CAD event is closed with a disposition code, that code is displayed alongside the corresponding notification record, giving administrators and supervisors greater visibility into call outcomes without leaving the platform.

Requirements

Your agency must have the UCAD integration enabled. Contact your Axon representative to confirm your integration status.

Where disposition codes appear

Disposition codes are visible in the Message History tab, associated with the relevant CAD event record.

Audit events

Actions within the settings page are tracked and audited, including:

  • General settings changes
  • Template actions (create, editing, deleting, active/inactive status)
  • Links (create, editing, deleting)
  • Call Type Management (create, editing, deleting, enabling/disabling messages, timing)
  • Message History (viewing and exporting)