Dispatch

From the first call to the paid invoice.

Who is going where, to do what, by when, and for whom?

Field service lives or dies on that question, and on most days the honest answer is “give me a minute, let me check.” A request comes in by phone, another by email, a third through the portal. A technician is already booked but nobody flagged it. The emergency at 11 PM finds the on-call list out of date. Dispatch connects the front-door moment a service request arrives to the back-door moment an invoice is paid, with triage, scheduling, agent assignment, on-site execution, completion checklists, and billing in between. Field service is a coordination problem, not a paperwork problem.

Where Orbit handles the relationships, Foundry handles the documents, and Depot handles the assets inside a property, Dispatch handles the movement: who is going where, to do what, by when, and for whom.

How it differs

Heavyweight residential-trades platforms do that one job well but are sealed systems: your customer data lives there, your documents live there. Dispatch inverts the model. Properties, customers, work history, and documents are first-class records in the platform graph. Pull a property’s asset history from Depot into a work order. Attach a brand-themed Foundry invoice to a service agreement. Let Concierge’s email ingest spin up service requests automatically. No integrations. One schema.

Lightweight contractor tools work for one to ten technicians with a simple calendar and basic invoicing. Dispatch starts where those stop. Multi-unit and commercial property hierarchies, service agreements with per-priority SLA tracking, skill-based agent routing, checklist templates with photo evidence and measurement capture.

Spreadsheet schedulers work until a request gets lost, a technician double-books, a customer complains nobody called back, or an emergency hits at 11 PM. Dispatch keeps the same low friction at intake but adds the structure that makes “what is happening right now” answerable at a glance.

Who it’s for

Property managers and HOA operators managing a portfolio of properties with owners, on-site managers, primary tenants.

HVAC, plumbing, and electrical operators routing skill-tagged technicians by territory and current GPS location.

Schedulers and dispatchers working the dispatch board with split-view agent availability and today’s work orders.

Field technicians working from the linked checklist template that walks them through required steps, the parts-required list, and the completion notes that close the job for billing.

Mobile-team operators running recurring service against a portfolio through service agreements with iCal RRULE recurrence.

Billing and AR coordinators generating invoices automatically from completed work orders.

What it does

The dispatch board is the operational center. Two columns. Every agent on the left with status (available, en route, on site, off duty) and skill tags. Every work order on the right with status, scheduled window, and estimated duration. Color-coded status dots (emerald for healthy, blue for upcoming, amber for in-flight, red for emergency or breached SLA) let the dispatcher triage at a glance.

Checklists are the proof-of-work record. ChecklistTemplate defines the steps for a category of work; each step has a type (checkbox, measurement with captured value, photo required, text input) and a required flag. Built-in templates ship for plumbing (with PSI capture), HVAC (with refrigerant levels and before-and-after photos), and general property inspection. “The job is done” is not a status flag. It is a body of evidence.

Service agreements model the contractual side. Recurring grease-trap cleaning, annual HVAC plus plumbing plus fire inspection, monthly maintenance walkthrough. Each agreement carries cadence, iCal RRULE for recurrence, service categories covered, response SLA per priority level, and a link to the underlying signed contract document in Foundry.

How it fits the ecosystem

Dispatch reads from anywhere on the platform graph. Properties link to Orbit companies, so the property’s full deal history, contact graph, and brand kit travel into every work order. Service agreements link to Foundry-signed contracts. Assets inside a property come from Depot, so when a technician arrives the warranty status and prior maintenance history are visible. Service requests can be created from Concierge voice calls or SMS conversations.

Where this product is in development

Dispatch is feature-complete and in final validation against customer workloads. What is live today is in active use; production deployment timing and the next capabilities are firming up with the beta cohort.

[Join the Beta Cohort]

Beta products are feature-complete and in final validation against customer workloads. Early access available; production deployment timing is on the roadmap.