---
title: "Dispatch & CAD"
slug: "dispatch"
category: "Departments"
order: 2
description: "Run real-time CAD dispatch with units, calls, assignments, map context, and notifications."
---

# 1 - Introduction

Dispatch is CADLY's real-time Computer-Aided Dispatch system for ER:LC roleplay. It tracks units, active calls, completed calls, assignments, statuses, and map context.

Dispatch requires the Dispatch permission and an enabled ER:LC integration. If Roblox linking is required, users must link Roblox before accessing dispatch.

Use Dispatch when your RP scenes need coordination between units. It gives dispatchers a shared view of calls, locations, available units, assignments, and status changes instead of relying on scattered Discord messages.

Dispatch works best when staff also use shifts correctly. CADLY can use shift state to decide who is available, who is on duty, and whether someone should be allowed to act inside dispatch.

## 1.1 - Table of Contents

| Section | What it covers |
|---|---|
| [Calls and Units](#2---calls-and-units) | Creating calls, assigning units, and status lifecycle |
| [Panel Behavior](#3---panel-behavior) | Real-time refresh, self-assignment, and notifications |
| [Settings](#4---settings--configuration) | Dispatch settings reference |
| [Troubleshooting](#5---troubleshooting-common-issues) | Common dispatch issues |

## 1.2 - Links to Related Documents

- [Departments](/docs/departments)
- [ER:LC Integration](/docs/erlc)
- [Shifts & Duty](/docs/shifts)

# 2 - Calls and Units

Dispatch calls have type, title, description, priority, status, map location, postal code, street name, icon, creator, timestamps, and assigned units.

Call priorities are low, medium, and high. Call types are standard, backup, and panic.

Use priority to communicate urgency, not importance to a specific department. A high-priority call should mean staff need to respond quickly. Use call type to communicate the nature of the request, such as backup or panic.

Locations can come from the map, postal code, street name, or ER:LC-derived data depending on how the call is created. More precise locations help units respond faster.

```cadly-mock
type: call
title: Backup requested at River City Bank
meta: Postal 703, created from dispatch panel
status: High priority
items:
- Status | active
- Assigned Units | 2L-14, 3S-22
- Type | backup
- Last Update | 38 seconds ago
```

## 2.1 - Call Lifecycle

| Status | Meaning |
|---|---|
| active | Call is open and visible in active calls. |
| completed | Staff completed the call. |
| auto_completed | CADLY completed the call after idle timeout. |
| cancelled | Call was canceled. |

## 2.2 - Unit Statuses

Units can be available, enroute, on scene, returning, or unavailable. Assigned units track status per call and can leave or update their call status.

## 2.3 - Assignment Notifications

When a unit is assigned, CADLY can send a Discord DM and an in-game ER:LC `:pm`. The in-game PM requires ER:LC integration and a valid key.

DM assignment is useful when users have Discord open. PM assignment is useful when units are already in-game and may not be watching Discord. Use both if your staff split attention between the game and panel.

# 3 - Panel Behavior

The Dispatch page refreshes units, active calls, completed calls, and ER:LC players. Active calls are sorted by priority.

When a call becomes assigned to you, the panel tracks it as your assigned call, displays it with a self-assignment marker, and plays a chime. New calls and panic escalations also trigger audio by priority.

The self-assignment marker helps units quickly identify their work in a busy call list. The chime is local to the user's browser, so each dispatcher can control volume through their own client.

Completed calls remain available as recent history so dispatchers can review what just happened without reopening logs or asking staff for status.

## 3.1 - On-Duty Requirement

Several dispatch actions require you to be on duty on the relevant server. CADLY checks whether your shift is active or on break before allowing those actions.

# 4 - Settings / Configuration

## 4.1 - Dispatch Module

```cadly-mock
type: setting
title: Dispatch module settings
meta: Settings > Dispatch
status: Server A
items:
- Require Roblox Link | On
- Sync In-Game Calls | On
- Auto-Complete Idle Calls | 5 min
- Max Units Per Call | Unlimited
```

### Enable Dispatch
Turns dispatch features on or off.
**Default:** on | **Requires:** none

### Require Roblox Link
Requires dispatch users to have a linked Roblox account.
**Default:** on | **Requires:** none

### Sync In-Game Calls
Creates dispatch calls from ER:LC emergency calls.
**Default:** on | **Requires:** ER:LC key

## 4.2 - Call Behavior

### Auto-Complete Idle Calls
Automatically completes calls that have been idle.
**Default:** on | **Requires:** none

### Idle Minutes Before Auto-Complete
Minutes before idle auto-complete, from 1 to 60.
**Default:** 5 | **Requires:** none

### Default Call Priority
Pre-selected priority when creating a call.
**Default:** medium | **Requires:** none

### Default Call Type
Pre-selected type when creating a call.
**Default:** standard | **Requires:** none

### Max Units Per Call
Maximum assigned units. `0` means unlimited.
**Default:** 0 | **Requires:** none

### Require Description
Makes description mandatory.
**Default:** off | **Requires:** none

### Require Postal Code
Makes postal code mandatory.
**Default:** off | **Requires:** none

## 4.3 - Notifications

### Panic Call
Channel, ping role, and message for panic calls.
**Default:** no channel | **Requires:** none

### High Priority Call
Channel, ping role, and message for high-priority calls.
**Default:** no channel | **Requires:** none

### Call Completed
Channel, ping role, and message for completed calls.
**Default:** no channel | **Requires:** none

### Unit Status Change
Channel, ping role, and message for unit status changes.
**Default:** no channel | **Requires:** none

## 4.4 - Unit Behavior

### Hide Off-Duty Units
Hides on-break units from the dispatch roster.
**Default:** off | **Requires:** none

### Auto-Remove Unavailable Units
Removes a unit from active calls when they go unavailable.
**Default:** off | **Requires:** none

### Auto-Enroute on Assign
Sets a unit to enroute when assigned.
**Default:** on | **Requires:** none

Keep this enabled if your units normally start moving as soon as assigned. Disable it if dispatchers assign units before confirming they are actually responding.

### DM on Assign
Sends the unit a Discord DM when assigned.
**Default:** on | **Requires:** none

### PM on Assign
Sends the unit an in-game private message when assigned.
**Default:** on | **Requires:** ER:LC key

If PMs do not arrive, check the ER:LC key, command queue health, and whether the target unit can be resolved to an in-game player.

# 5 - Troubleshooting Common Issues

## 5.1 - Dispatch Says ER:LC Is Required

Enable ER:LC and configure an API key for the active server slot.

## 5.2 - User Cannot Access Dispatch

Assign Dispatch Access, confirm View Server permission, and verify Roblox linking if required.

## 5.3 - Unit Cannot Create or Assign Calls

The user must be on duty. Some cross-unit actions require Dispatch Manage.

# 6 - Getting Support and Resources

If you need help, several resources are available:
- [CADLY Documentation](/docs): Detailed reference for all features.
- [CADLY Support Server](https://discord.gg/cadly): Join for **fast help** from the team.
- [CADLY Email Support](mailto:admin@cadly.me): Reach out **via email** for direct support.