Dashboards by role: dispatch

A Capacity Dashboard on ServiceTitan Data: Booked Hours Against Open Hours, 7 and 30 Days Out

Marketing spends hardest in the week dispatch is already full, then goes quiet in the week the calendar is empty. Nobody is careless. They are looking at different screens. A capacity dashboard puts the hours you can sell and the hours you have sold on one.

November 13, 2026 · 9 min read

dash.acmeairco.com · capacity, HVAC service
Skill-based availability, next 30 days
This week is full. Week three is wide open.
Booked share of available hours-78 pts
TodayBooked share falls below 60% in week twoDay 30
Illustrative: a sample 30-day view for a fictional HVAC company

The short answer

A capacity dashboard compares booked hours with available technician hours for the next 7 and 30 days, split by skill, zone and business unit. Built on ServiceTitan's Dispatch API, which reports total and open availability in hours, it shows which days are full, which are thin and who could take the work. DataCram builds one starting at $575, with hosting from $55 a month.

On this page
  1. Full on Thursday, empty on the 19th, and nobody told marketing
  2. Hours you can sell, hours you have sold
  3. Skill and zone: where an empty calendar is lying
  4. Thirty days, asked for fourteen at a time
  5. Booked is a plan. Worked is what happened.
  6. One screen, three people, three different decisions
  7. Price, and when a capacity screen is overkill

Full on Thursday, empty on the 19th, and nobody told marketing

Take a twelve-technician company in the first warm week of May, as an illustration. Dispatch knows Thursday is full. The office manager knows the 19th has holes. Marketing knows only that last month's ad budget was approved. The ads run evenly, so the calls arrive evenly, so Thursday turns work away and the 19th sends two technicians home early. Each person did the job in front of them. The schedule simply never reached the people who could have changed it.

A capacity dashboard is the cheapest fix we know for that. It reads shifts and bookings from your ServiceTitan account through the API and shows one thing: how much of the time you could sell is already sold, day by day, for the next week and the next month. It sits among the role dashboards we build as custom ServiceTitan dashboards, and its seven-day row feeds the capacity panel on the general manager dashboard.

Hours you can sell, hours you have sold

ServiceTitan's Dispatch API already does the hardest arithmetic. Its OpenAPI document, which we read on the Developer Portal in November 2026, describes a capacity request that returns, for each time frame, a totalAvailability ("Number of hours that total capacity can allow to be booked during this time frame") and an openAvailability ("Number of remaining hours that can be booked during this time frame"). Each frame also carries a flag for when the ideal booking percentage is exceeded, and the technicians available in it.

From those two figures, booked share is plain division: total hours minus open hours, divided by total hours. That calculation is ours, printed on the screen, not a metric ServiceTitan publishes. The dashboard shows it across four horizons, each for a different person:

Four capacity horizons, the question each answers, and who acts on it
HorizonThe question it answersWho acts on it
Today and tomorrowWhere is there room for an emergency call, and who has the skill for itDispatch and the CSRs
Next 7 daysWhich days and business units are thin enough to call members due for maintenance, or full enough to stop pushingThe general manager and the office
Next 30 daysWhich weeks need more calls from marketing, and which need fewerThe owner and whoever runs the ads
Past 30 daysHow booked share compared with the hours technicians actually workedThe service manager, at the monthly numbers review

Skill and zone: where an empty calendar is lying

A day can look half empty and still have no room for the call that just came in. If the open hours belong to a technician who does not install mini-splits, or to one working the far side of the county, that space is not for sale. ServiceTitan's capacity request requires a skillBasedAvailability setting ("Indicate whether to use skill-based availability matching"), accepts a list of business units, and takes a jobTypeId, described as the "Job type whose duration should be used to calculate availability."

A row of glowing cyan columns, tall on the left and shrinking to the right, over a deep blue and violet field with a thin grid of calendar squares
Open hours only count when the right technician, in the right zone, owns them.

So the dashboard asks the question several ways. ServiceTitan's API reference, as read in October 2026, lists the Dispatch family's resources as including "capacity, non-job appointments, teams, technician shifts, technician skills, technician tracking, zones." A shift's shiftType field is described as "How the shift is displayed and contributes to availability calculations," so a technician on call or on a half day counts the way your dispatchers already set it up. The screen splits open hours four ways:

  • By business unit: HVAC service, HVAC install and plumbing, each on its own row.
  • By skill: the hours that can actually take an install, a commercial call or a gas line.
  • By zone: open hours where the trucks will be, not where the office happens to be.
  • By technician: who has room on which day, for the dispatcher deciding where the 3 p.m. call goes.

Thirty days, asked for fourteen at a time

One technical detail shapes the 30-day view. ServiceTitan's release notes for ST-75, dated October 28, 2025, added a "14-day request limit for capacity endpoints," effective 11/13/2025, and state that "you must split the request into 14-day chunks." A month of capacity is three requests stitched together. That is routine work. We mention it because a vendor who promises a month of capacity in one call has not read the release notes.

  1. 1

    Ask in chunks

    Days 1 to 14, days 15 to 28, then the remainder, for each business unit and skill setting the screen shows.

  2. 2

    Refresh near days more often than far ones

    Tomorrow changes every hour as calls book; the fourth week changes slowly. The schedule reflects that and stays well inside ServiceTitan's published limit of "600 calls per 10 seconds per application per tenant" for non-reporting APIs, per its developer FAQ as read in October 2026.

  3. 3

    Rebuild rather than hoard

    ServiceTitan's API Terms of Use, dated April 15, 2026, restrict keeping API content beyond 24 hours except where the terms or documentation permit. The view is rebuilt from fresh requests instead of a growing archive. Confirm what your own agreement permits.

  4. 4

    Stamp every row

    Each row shows when it was last asked, so a stalled connection reads as stalled, not as a suspiciously empty Thursday.

ServiceTitan's Marketing Ads family also lists "capacity warnings" among its resources, in the same API reference. If your ad setup already relies on them, the dashboard sits alongside rather than replacing anything. The API data page covers the rest of the plumbing, from rate limits to what happens when ServiceTitan changes an endpoint.

Booked is a plan. Worked is what happened.

Forward capacity is a promise. Looking back tells you whether the promise was any good. ServiceTitan's Payroll API job timesheets carry dispatchedOn, arrivedOn and doneOn for each technician on each job, per its Payroll OpenAPI document as read in November 2026. Pricebook items carry sold hours, which ServiceTitan's help center describes as "the estimated labor hours tied to a pricebook item."

Put those beside last month's booked share and patterns appear. A business unit that books, say, 90 percent of its hours but works far fewer may be scheduling jobs too long. One that is always full and always running late may be scheduling them too short. ServiceTitan's legacy Daily Sold Hour Tracker guide defines efficiency as "([Total Sold Hours] x [Technician splits]) / [Hours the technician spent on a job] *100." The revenue per hour guide explains how hours and dollars fit together. Judging individual technicians is a job for the technician scorecard, done carefully, not for this screen.

One screen, three people, three different decisions

Dispatch

Today and tomorrow by technician and zone. The question is where the next call goes, and the answer has a name on it.

The office and the GM

The next seven days by business unit. Thin days become outbound calls to members due for a visit, a list the memberships dashboard keeps. Full days end the discount offers.

The owner and marketing

The next 30 days by week. Thin weeks ask for more calls; full weeks ask for fewer. Spend by source lives on the marketing ROI dashboard.

That restraint is deliberate. A capacity screen that guesses is one more opinion in a room full of them. A capacity screen that counts is a fact everyone can plan around, which is the whole reason to build it.

Price, and when a capacity screen is overkill

The build begins at $575 and the final figure depends on complexity (prices as of November 2026), set out in a fixed written estimate before anything starts. One location with three business units sits near that floor; several locations, many skills or zone maps push it up. Hosting starts at $55 a month. The ServiceTitan connection goes live the same day. Before you commission it, check your package: ServiceTitan's integration paths page said in October 2026 that customer-built apps call for the "Works or Ent Plus package." A monthly numbers review to read the screen with you starts at $575 a month, no long contract.

The dispatch board is enough if

  • You run fewer than five technicians and the dispatcher sees the whole week at a glance
  • Nobody changes marketing spend based on the schedule
  • Every technician can take every kind of call

A capacity screen pays its way if

  • Marketing and dispatch disagree about whether you are busy
  • Skills or zones mean an open hour is not always a sellable hour
  • You want next month's thin weeks visible while there is still time to fill them
  • You want booked hours compared with worked hours each month

If customers book online through Scheduling Pro, our Scheduling Pro guide covers how it fits a website. If you are leaving ServiceTitan instead, see the dispatch board you own. DataCram is a studio in San Antonio, Texas that has built web software since 1999 and works with companies nationwide by phone and video, with a shared project page. We are not affiliated with ServiceTitan or one of its partners. The build sits under our API integrations work. Read about DataCram or call (210) 346-0848.

Questions owners ask about ServiceTitan dashboards and numbers

Start with ServiceTitan's Dispatch API, which returns total availability and open availability in hours for each time frame, by business unit, with optional skill matching and a job type's duration. Booked share is total minus open, divided by total. Compare it across the next 7 and 30 days, then check past weeks against timesheets to see whether bookings matched the hours worked.

ServiceTitan's release notes for ST-75, dated October 28, 2025, added a 14-day limit to capacity requests, effective November 13, 2025, and say requests must be split into 14-day chunks. A 30-day view is three requests joined together. It is routine, but any build that ignores the limit will fail quietly.

Yes, as far as your ServiceTitan setup does. The capacity request takes a skill-based matching setting and business units, and the Dispatch family covers technician skills, shifts and zones. If skills and zones are maintained in ServiceTitan, the dashboard can show open hours that can actually take a given job, not just empty space.

We set the schedule with you. Today and tomorrow refresh often, because they change as calls book; the third and fourth weeks refresh less often. Every row shows the time it was last asked, so a stalled connection is obvious. The refresh plan stays inside ServiceTitan's published rate limits.

No, and we will not pretend it can. It shows what is already booked and how many sellable hours remain. Weather and demand are not on the calendar until customers call. What it does do is show thin weeks early enough for marketing or member outreach to fill them.

From $575 to build, depending on complexity, under a fixed written estimate, with hosting from $55 a month (November 2026 prices). The API connection goes live the same day. A monthly numbers review is available from $575 a month if you want help acting on what it shows.

Keep reading

Free · No obligation

See next month's thin weeks now

Tell us your technician count, trades and zones. A person at DataCram replies with what a capacity screen would show for your setup and a fixed written estimate on request.

Which of these sounds like you? (pick any)

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

CallGet a quote