Managing Dispatch Sources

The Dispatch Sources infeature OPSCOM allowallows administrators to define and categorize the origins of dispatch calls or eventsevents, (e.g.,such "Phoneas Call,"a "Email,"phone "Officercall, Initiated").email, Thisor featurean enablesofficer-initiated alert. Its primary purpose is to enable better tracking of incident intake, facilitatesfacilitate efficient routing to relevant categories, and enhancesenhance reporting on the origins of dispatch activities. This article is intended for OPS-COM administrators responsible for configuring dispatch workflows and incident tracking.

Setup and Configuration

This feature is a core administrative tool used to establish the intake tracking metrics for dispatch operations.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the dispatch administration menus and manage dispatch sources.

Using this Feature

The Dispatch Category Link Administration page allows you to define where your dispatch calls originate from and seamlessly link them to relevant dispatch categories.

Accessing the Management Interface

1. 1.Hover Clickover System Administration,Administration, click Dispatch, then Dispatch, and click Manage Dispatch Sources.Sources.

Adding a Dispatch Source

1. Click the Add Dispatch Source button.

2. Type in

   Enter the origin name (e.g., Walk-In, Radio, or Internal Alert) into the Name (e.g.,field.

   "Walk-In," "Radio," "Internal Alert").

3. Select the categories that should be linked to this source from the connected dropdowndrop-down menu.

   • Note:

     Click the Save Changes button.

If you want to selectlink the source to all available categories, you can left-click on the first category and usehold the CTRL Clickkey while clicking to select them all.all simultaneously.

Click Save Changes

Editing a Dispatch Source

1. Choose

   Click the Edit button next to the specific source you wish to edit.modify.

2. Make the necessary changes andto clickthe source name or category links.

3. Click the Save Changes.Changes button to apply your updates.

---

Best Practices &and Considerations

• ComprehensiveEstablish Definitionscomprehensive definitions:: Define all common methods by which dispatch calls or alerts are received in your organizationorganization. (e.g.,Accurately "capturing options like Emergency Line," "Non-Emergency Phone," "Email," "or Mobile App Submission").Submission provides a clearer picture of your incident intake.

• LogicalImplement Categorylogical Linkingcategory linking:: Link each source to all relevant dispatch categories it might generategenerate. (e.g.,For "example, a standard Phone Call"Call source might reasonably link to "Parking Incident," "Security Alert," "and Maintenance Request").Request categories to streamline dispatcher workflows.

• ConsistencyMaintain data consistency:: Ensure consistent use of defined dispatch sources by all personnel involved in dispatch activitiesactivities. Uniform data entry is vital to maintain accurate reporting.reporting and prevent administrative confusion.

• ReportingLeverage Valuereporting value:: Properly categorized dispatch sources are invaluable for generating reports on call volume,volume and types of incidents by source,source. andThis identifyingdata allows management to identify long-term trends in how incidents are reported.reported across the property.

• ReviewConduct Regularlyregular reviews:: Periodically review your list of dispatch sources to ensure they remain currentcurrent. andRegular audits guarantee the options available to dispatchers remain highly relevant to your evolving operational needs.