Dispatch software for field service teams

Every open job sits on a live status board that changes as the work moves. When a job is assigned, picked up, or closed, the board reflects it — no one wipes a column at shift change, and no one photographs the whiteboard to remember what it said.

The board reads the same for everyone with a seat. A dispatcher in the office and an owner checking in from a phone are looking at the same jobs in the same state, because there is only one record to look at.

Every job pins to a map, and each pin carries two signals: urgency and service type. A dispatcher reading the map sees which jobs need attention first, what kind of crew each one needs, and what is near what — without opening a single job.

Routing stops being a mental exercise spread across a spreadsheet and a separate map tab. The geography of the day is on one screen, colored by what matters.

Assigned work lands in a driver pickup queue. Drivers see what is theirs to take next; dispatchers see what has been picked up and what is still waiting. The round of radio calls to find out who has which job becomes unnecessary, because the answer is already on the screen.

The iOS and Android app wraps the same workspace, so the queue a driver opens on a phone is the queue the dispatcher is watching. Coordination happens in the in-workspace chat, which sends push notifications.

Every assignment, status change, and reprioritization is written to an append-only audit log with a date and an author. Changes are logged, not overwritten, and nothing is silently lost. When a customer asks why a crew arrived Tuesday instead of Monday, the answer is in the record, not in someone's memory of a radio call.

Full-text search covers the record, so a job, an address, or a decision from three months ago is a query away. One record. Nothing lost.

The dispatch console runs inside your branded workspace at your own subdomain, in your colors, fonts, and logo, next to the inventory grid, ops views for fulfilment and exceptions, billing, and files. Members, roles, invites, and per-seat licensing decide who dispatches, who drives, and who watches.

Postgres row-level security keeps every tenant's data separate, and Google SSO handles sign-in. Dispatch is not a bolt-on to a generic field-service tool; it is one view of the same single live record the rest of the operation runs on.