Automatic Dispatch and Call Routing With No Dispatcher Online

Ask any roleplay community owner what position they cannot fill. It is not officers. It is not command staff. It is dispatch.

People join police roleplay to drive fast and talk on the radio. Almost nobody joins to sit in a browser tab assigning other people to calls. So most servers run without a dispatcher, and the call queue ends up with nobody managing it.

Automatic call routing exists to fix that. Here is how it works.

Why Self Dispatch Falls Apart

Self dispatch is not a bad idea. It is just an unmanaged one.

Without rules, four units respond to the same traffic stop because it popped up on everyone's screen at once. A structure fire sits open for eleven minutes. Two officers both mark themselves as primary on the same call and neither notices until they arrive together. Somebody goes out of service and never comes back, so the roster shows nine units available when three actually are.

None of that is a discipline failure. It is what happens when a queue has no scheduler.

The seat goes unfilled because the work is genuinely different from the work people signed up for. Nobody joined to read a queue and assign other people to it, and asking harder does not change that. The scheduler has to be software.

What Automatic Call Routing Actually Does

Routing is the part of a CAD/MDT system that decides who gets what, without a person in the middle.

One call, one unit, no shouting

When a call is created, routing looks at who is currently marked available and attaches a unit to it. The officer gets the call already assigned to their name rather than a notification everyone races to answer.

That single behavior removes most of the pile on problem. A unit that is already assigned is not in the pool, so nobody stacks four cars on a stalled vehicle while a robbery waits.

Priority ordering

Not every call deserves the same urgency. Routing in PlateNet CAD/MDT sorts the queue by priority, so a pursuit or shots fired call pulls units off lower priority work, while noise complaints and abandoned vehicles wait until somebody is free.

You set the priority tiers once. After that the queue sorts itself, including when a low priority call has been open long enough that it should escalate.

Stale Units and Why They Wreck a Shift

Here is the failure mode nobody plans for. An officer marks themselves available, then alt tabs to Discord for twenty minutes. As far as the system is concerned they are ready. Calls route to them. Nothing happens.

PlateNet CAD/MDT tracks how long a unit has held the same status and flags anyone who has gone quiet. Flagged units drop out of the routing pool automatically, so calls skip them instead of dying on them. When the officer comes back and touches anything, they return to the pool.

Why timers beat manual checks

The manual version of this is a supervisor calling a status check over the radio every fifteen minutes. That works and everyone hates it. Timers do the same job silently, and they do not stop working when the supervisor logs off.

Running a Shift With Zero Dispatchers

A routed server behaves differently in a way you notice within one patrol.

A call is created, routing assigns it, and the officer works it and clears with a report attached. Any officer can also claim an unassigned call directly from the queue, which is self dispatch done properly, because the system already knows who is free and what is waiting.

Supervisors see the whole board. They can reassign anything, but they rarely need to.

The goal was never to replace dispatchers. It is to keep the server working on the four nights a week when nobody signs up to be one.

What still needs a human

Routing does not do scene narration, escalation calls, or judgment about when a pursuit should terminate. A live dispatcher still makes those nights better. The difference is that your server no longer collapses without one.

If you run on FiveM, the FiveM setup guide covers how a CAD fits alongside the server you already have.

Tuning the Rules Without Overthinking It

Start with defaults and change one thing at a time.

The two settings that matter most are the stale timer length and how many units a high priority call pulls. Set the stale timer too short and active officers get bumped mid scene. Set it too long and calls keep routing to people who left. Two hundred and forty seconds is a reasonable starting threshold for most servers.

Review the queue history after a week. If the same call type keeps waiting, raise its priority. If units complain about getting yanked around, lower how aggressively high priority calls reassign. Your server administrators can adjust all of it from the backend without editing a config file or restarting anything.

Comparing systems on this specifically? The CAD/MDT selection checklist lists the routing questions worth asking before you buy.

Frequently Asked Questions

What is self dispatch in roleplay?

Self dispatch means officers assign themselves to calls instead of waiting for a dispatcher. It is how most communities operate. It works well when the system enforces availability, priority, and one primary unit per call.

Does automatic dispatch replace a human dispatcher?

No. It covers the shifts where no dispatcher is online, which for most servers is the majority of them. When a dispatcher logs in, they take manual control and the routing steps back.

How does the system decide which unit gets a call?

It works from unit status. Routing picks from units currently marked available, skips anyone already assigned, and skips anyone flagged stale, so a call lands on somebody who is actually free to take it.

What stops four officers from responding to one call?

Once routing assigns a primary unit, the call leaves the open queue. Other officers can still attach as backup, but they do so deliberately instead of by accident.

Can I turn automatic routing off?

Yes. Communities that always staff dispatch usually run in manual mode and enable routing only as a fallback for off peak hours.

Does this work on platforms other than FiveM?

Yes. Routing works from unit status and the call queue, which behave the same whatever you play. See CAD/MDT across roleplay platforms.