Is the dashboard backed by real data now?

Yes. The admin dashboard runs on real-time queries — stats are live counts, the active-incidents list shows actual rows, the unit roster is your real fleet. Settings save with one click and persist immediately.

What's the difference between emergency_response (slug) and 'Dispatch & Fleet' (display name)?

Same module. The internal identifier is 'emergency_response' (kept consistent for existing customers). The display name is 'Dispatch & Fleet' because the broader name better fits service-contractor and fleet use cases — not just 911-style emergency response.

How do I migrate from a hardcoded dispatch app to Dispatch & Fleet?

Three steps: (1) Activate the module + run the migration page; (2) Bulk-import your fleet units (each unit needs a code, type, name, and optional GPS info) or add them by hand from the CRM Fleet Units tab; (3) Configure your dispatch types in the dashboard so the categories match your operation. Existing incident history doesn't import (importer is on the roadmap). Going forward, every new dispatch links to a customer in your CRM with a complete audit trail.

Dispatch & Fleet — Real-Time Incident Dispatching with Live Fleet Map and CRM-Linked Incidents

Dispatch incidents to fleet units in real time. Customer-FK incident records, live Leaflet fleet map, customizable dispatch types, GPS-tracked units, per-tenant dispatch protocols, and a tenant-admin dashboard backed by real queries (no mock data). 9 schema tables for service-contractors, security firms, mobile health, fleet ops, and emergency response.

Incidents linked to your CRM customers · Live fleet map · Real-time admin dashboard · Per-tenant dispatch types

Real-time incident dispatching with a live fleet map. Every incident is tied to a customer in your CRM, so dispatch history rolls up on the customer timeline alongside calls, payments, and projects.

What's in the box

Customer-FK architecture

Every incident links to a customer in your CRM. No duplicate customer records. Dispatch history rolls up on the customer timeline alongside calls, payments, and projects.

Live fleet map (Leaflet.js)

Open-source mapping, no per-map API fees. Unit markers colored by status (available=green, dispatched=amber, on-scene=red). 30-second polling refresh; WebSocket push is on the roadmap.

Per-tenant dispatch types

Customize categories per operation: a service-contractor's "Service Call / Delivery / Installation" coexists with an emergency shop's "Medical / Fire / Accident". Each type has its own icon, color, default priority, and is_emergency flag.

Real-data dashboard

Stats grid (active / units available / personnel / avg response time / today / resolution rate) runs on real-time queries. Settings save securely with one click.

5-tab CRM-side module

Dispatch Center (incident creation), Active Dispatches (filter board), Fleet Units (status + assignment), Live Fleet Map, History (audit trail).

9 schema tables

Incidents, units, personnel, dispatches, protocols, communications, GPS history, resources, and dispatch types — all stay private to your team.

Response-time analytics

Every status transition timestamps a column (dispatched_at / arrival_at / resolved_at) and computes response_time_seconds + resolution_time_seconds automatically. Dashboard shows 30-day rolling averages.

Tenant isolation + audit

Every query is automatically scoped to your account. The admin overview surfaces per-tenant rollups for support oversight (read-only, no cross-account write paths).

Setup steps

Activate the module. RubiMine → Dispatch & Fleet → Activate ($299.99/mo).
Apply the schema migration. A system administrator visits the migration page and clicks Apply schema. Safe to re-run anytime.
Verify state. Open /admin/view-dispatch-state.php — every Dispatch-active tenant should appear in the rollup. Library counts non-zero on a deployment with seed data.
Configure dispatch types. Tenant admin opens /tenant-admin/modules/emergency-dashboard.php → Dispatch Types tab. Add types matching your operation (icon, color, default priority, emergency flag).
Configure dispatch settings. Same dashboard → Dispatch Settings tab. Toggle auto-dispatch, GPS tracking, set response time target, pick alert channels. Settings save securely with one click.
Add fleet units. CRM Dispatch module → Fleet Units tab → Add Unit. Each unit needs a unit_code, unit_type, unit_name, optional radio_channel + base_station.
Create an incident. CRM Dispatch module → Dispatch Center tab → New Incident. Pick a customer (links incident to CRM), pick dispatch type, set priority, fill location + caller info.
Dispatch units. From the incident detail, assign units. Watch them appear on the Live Fleet Map.
Track resolution. Update incident status as the situation evolves. Stats refresh in the dashboard automatically.

FAQ

What's Dispatch & Fleet for?

Real-time incident dispatching for service-contractor fleets, security firms, mobile-health, fleet ops, and emergency response. Customer-FK records, live fleet map, customizable dispatch types, real-data dashboard.

Is the dashboard backed by real data?

Yes. Every stat is a real-time count, and settings save with one click and persist immediately.

Do incidents have to link to a CRM customer?

No — customer_id is nullable. Walk-up dispatches and anonymous calls work without a link. When linked, the incident appears in the customer timeline.

How does the live fleet map work?

Leaflet.js — open-source, no per-map fees. Unit markers colored by status. 30-second polling refresh in V2; WebSocket push reserved for V2.1.

What are dispatch types?

Per-tenant customizable incident categories. Each has icon / color / default priority / is_emergency flag. Manage in the tenant-admin dashboard's Dispatch Types tab.

Why is the slug emergency_response but the display name "Dispatch & Fleet"?

Slug preserved across V2 to keep activations working. Display name was standardized to "Dispatch & Fleet" because "Emergency Response" sounded 911-only and didn't fit service-contractor or fleet use cases.

What permissions are needed?

CRM-side module: agents AND admins (slug is in ModuleManager's 'both' allowlist). Tenant-admin dashboard: requires is_tenant_admin. State viewer + migration page: is_system_admin only.

Is your data private to your team?

Yes — every query is automatically scoped to your account. Cross-account access returns empty.

What's on the roadmap?

Future enhancements: real-time WebSocket location push, mobile dispatcher field app, AI protocol suggestion, Twilio SMS, multi-agency mutual aid, personnel shift scheduling.

Resources

Last updated: 2026-04-28.