Module: booking and dispatch

A Booking and Dispatch Board You Own: Who Is Where, What Is Next, and Why It Is the Hardest Module to Build

Dispatch is the room where a field service platform earns its fee. Replacing it is possible, and for the right shop worth it, but it is the module we quote most carefully and the one we tell owners to build last.

November 11, 2026 · 9 min read

app.acmeairandplumbing.com · dispatch, Tuesday
Booked hours against shift hours, by technician
Two techs full, one with room for the 2 p.m. call
Sample
Tech A, HVAC8 of 8 h
Tech B, HVAC7.5 of 8 h
Tech C, plumbing4 of 8 h
Tech D, plumbing6 of 8 h
Unassigned queue3 jobs waiting
Illustrative: a sample dispatch day for a fictional HVAC and plumbing company

The short answer

A custom dispatch board shows every technician's day on one screen, holds unassigned jobs in a queue, and lets a dispatcher drag a job to another tech and tell the customer. It is the heaviest module, because dispatch touches capacity, skills, zones and the technician app. A first version can skip route optimization and automatic assignment. Pricing starts from $575, depending on complexity; dispatch sits well above that floor.

On this page
  1. The demo had 200 trucks on it. You run 14.
  2. Ten things a dispatch board has to understand
  3. Version one, and the features it is allowed to skip
  4. Why dispatch costs more than the dashboards ever will
  5. Running your board beside ServiceTitan's for a while
  6. What the board costs, and what keeps costing after launch
  7. Shops that should leave dispatch alone

The demo had 200 trucks on it. You run 14.

The sales demo is always beautiful. A wall of colored blocks, technicians sorted by skill and zone, a map with little vans gliding between rooftops, a capacity meter for next Thursday. It was built to impress the operations director of a company with 200 trucks and three call centers. You have 14 trucks, one dispatcher, and a whiteboard the dispatcher still trusts more than the screen.

That gap is the whole argument for a board of your own: you pay every month, per technician, for scheduling machinery sized for someone else. It is also the argument for caution. Dispatch is where ServiceTitan is strongest. Its pricing page, as of November 2026, lists Dispatching on every package, and its menu lists a separate Dispatch Pro among its Pro products, with no published price for either. Its Scheduling Pro page promises "real-time availability based on your dispatch board." That is years of work, and it shows. Our fair look at Scheduling Pro covers that product for owners who are staying.

So this page does two things. It describes what a custom booking and dispatch board does, and it tells you plainly how much work that is, so you can decide whether to build it, rent it, or keep ServiceTitan's while you replace the easier modules first.

Ten things a dispatch board has to understand

The most honest description of dispatch we know of was written by ServiceTitan itself, in the list of resources under the Dispatch family in its API reference, as of October 2026: "Appointment assignments, arrival windows, business hours, capacity, non-job appointments, teams, technician shifts, technician skills, technician tracking, zones." Ten nouns. Each is a feature, a set of rules and a screen. Here is what each means for a board you own, and whether a first version needs it.

The ten parts of dispatch, what each means in a custom board, and whether version one needs it
PartWhat it means for your boardVersion one?
Appointment assignmentsWhich technician owns which visit, and the drag that changes itYes, it is the board
Arrival windowsThe promise made to the customer, such as 8 to 10 a.m.Yes, your current windows
Business hoursWhen jobs may be booked at all, including after-hours ratesYes
CapacityHow many more jobs fit, which online booking also readsSimple version: open hours per tech
Non-job appointmentsMeetings, training, a truck at the shop, a dentist visitYes, or the board lies
TeamsGrouping techs by trade or crewYes, as a filter
Technician shiftsWho works when, including on-call weeksBasic shifts yes, rotations later
Technician skillsWho may be sent to a commercial rooftop unit or a tankless heaterAs tags the dispatcher sees, no auto-matching
Technician trackingWhere each truck is right nowLater; status buttons first
ZonesWhich part of town each tech coversAs a color, not a rule

Read the right column again. A first version is a board a good dispatcher can run by eye, with the information in front of them. Automation that decides for them comes later, if at all, because a rule that sends the wrong tech to a commercial job costs more than the minute it saved.

Version one, and the features it is allowed to skip

Layered colored-paper scene of small service vans on paper streets between houses, with a paper dashboard panel floating above, soft shadows
A first dispatch board shows who is where and what is next; the clever routing can wait.
  • A day and week grid by technician, with each job as a block showing customer, job type, window and status.
  • An unassigned queue where new bookings from the phone, the website and the online booking module wait for a person to place them.
  • Drag to assign or reassign, with a warning when a move breaks a promised arrival window or double-books a technician.
  • Status from the field: en route, on site, done, needs a return visit, set from the technician app and shown on the board.
  • A customer notice when a job moves or a tech is on the way, by text at carrier cost or by email.
  • Job history at a click, so the dispatcher sees the last three visits before sending anyone back.

What version one skips: route optimization, automatic assignment by skill and zone, live GPS on a map, capacity forecasting, multi-location rules and a drag-and-drop editor for business units. Every one of those is real. None of them is needed to dispatch fourteen trucks on Monday, and each can be added once the board has earned trust. Leaving them out is how a heavy module stays within a written estimate an owner can sign.

Why dispatch costs more than the dashboards ever will

A dashboard reads. A dispatch board writes, all day, while other people write too. Two dispatchers drag the same job at the same moment. A technician marks a job done from a basement with one bar of signal, and the update arrives eight minutes late. A customer books online for a slot the dispatcher just filled by phone. Each of those needs a rule, a test and a screen that explains what happened.

Dispatch is the only module where a bug sends a truck to the wrong house.

Everything else leans on it. Invoices start from the job. The invoicing module needs the job's lines and status. Online booking needs honest availability. The KPI dashboard counts booked capacity from it. Change how the board stores a job and four modules feel it. That is why we build it carefully, test it alongside the system it replaces, and price it well above the floor.

There is also the dispatcher. Your best one can run the day from memory and has opinions about every screen they have ever used. That person should sit with us before anything is drawn, and their objections are the most useful requirements document the project will get.

Running your board beside ServiceTitan's for a while

Nobody should switch dispatch systems on a Monday in July. The safer route is a parallel run, and the connection that makes it possible goes live the same day. While both run, the custom board can read ServiceTitan's schedule and write jobs back. ServiceTitan's API reference, as of October 2026, documents adding an appointment to an existing job and rescheduling one. Its release notes of November 20, 2025 say a capacity request's date range "is now limited to 14 days." Its Developer Portal says customer-built apps require the Works or Ent Plus package, so check yours.

  1. 1

    Shadow week

    The custom board mirrors ServiceTitan's schedule, read-only. The dispatcher looks at both and lists every difference.

  2. 2

    One trade, one dispatcher

    Plumbing, say, is dispatched from the new board while HVAC stays put. Jobs still write back so billing and reports stay whole.

  3. 3

    Fix what the week found

    Every surprise becomes a rule or a screen change. This is where the written estimate's contingency gets spent, if it gets spent.

  4. 4

    Cut over on a slow day

    All trades move. ServiceTitan stays readable for records until you decide otherwise. Our migration guide covers what to export and keep.

If the parallel run tells you the board is not ready, keep ServiceTitan's dispatch and keep the modules you have already moved. That is a fine outcome. The section hub explains why a partial replacement can still lower the bill.

What the board costs, and what keeps costing after launch

The booking and dispatch module is from $575 to build, depending on complexity, as of November 2026, and dispatch is one of the heavy modules that land well above that floor. You get a fixed written estimate before work starts, and that estimate, not a promise on this page, sets the schedule. Hosting and maintenance are from $55 a month. On-my-way and reschedule texts are billed at carrier cost through the SMS module. The connection to ServiceTitan for the parallel run goes live the same day.

The arithmetic is still worth doing. ServiceTitan does not publish its prices, and owners with five or more technician licenses tell us their bill runs $2,500 a month or more. That is $30,000 a year. A board you own costs a build and a hosting plan, not a seat for every truck you add. Run your own figures in the savings calculator, and see the full module menu for how dispatch fits with the rest.

Shops that should leave dispatch alone

Keep ServiceTitan's dispatch if

  • You run several locations or call centers and depend on its capacity rules
  • You rely on skill-based automatic assignment across a large crew
  • Nobody on your team has time to sit through a parallel run
  • Your other modules are not replaced yet; build the easy wins first

A board of your own fits if

  • One dispatcher runs the day by eye and the platform gets in the way
  • You add trucks often and the per-technician bill climbs with each one
  • Booking, invoices and the tech app are already moving to your own app
  • You want online booking to read the same board your dispatcher sees

If you are not sure which column you are in, read when to keep ServiceTitan first. Then call (210) 346-0848, or send a screenshot of a typical Tuesday on your current board. DataCram has built for the web since 1999 from San Antonio, and we would rather talk you out of a dispatch build than sell you one you cannot use. Our web app development page describes how we build.

Questions owners ask about replacing ServiceTitan

We do not quote a schedule on a web page. The fixed written estimate we give before work starts sets both the price and the schedule, based on what version one includes. A board a dispatcher runs by eye, without route optimization or automatic assignment, is far smaller than one that decides for them. The parallel run with your current system adds time and is worth it.

Yes. The connection goes live the same day, and the custom board can read ServiceTitan's schedule and write appointments back while both run. ServiceTitan's Developer Portal, as read in October 2026, says customer-built apps require the Works or Ent Plus package, and its November 20, 2025 release notes limit capacity requests to a 14-day range. Check your own agreement.

Not in version one. Status buttons in the technician app (en route, on site, done) tell the dispatcher most of what a map would, at a fraction of the build. Live location can come later if the dispatcher still wants it after a month on the board. It also raises questions about tracking employees after hours that you should settle first.

The board has to decide, and that rule is part of the build. Ours saves the first move, refuses the second, and shows the second dispatcher what changed and who changed it. Conflicts like this, plus late updates from technicians with weak signal, are a large part of why dispatch costs more than other modules.

It should. When the online booking module and the board share one database, the website offers only slots the board can fill, and a booked slot disappears for the dispatcher at the same moment. Version one usually counts open hours per technician and trade; smarter capacity rules come later.

From $575 to build, depending on complexity, as of November 2026, and dispatch is one of the heavy modules that land well above that floor. You get a fixed written estimate first. Hosting and maintenance are from $55 a month, and customer texts are billed at carrier cost.

Keep reading

Free · No obligation

Get an honest read on your dispatch build

Describe your crew, your trades and how your dispatcher works today. A person at DataCram replies with what version one would include, what it would skip, and whether you should build it at all yet.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote