ServiceTitan Voice Agents Dashboard [Roofing Impact]

ServiceTitan's Voice Agents Dashboard and Spanish-language call booking shipped as of July 11, 2026, and roofing is one of the trades this release maps onto most directly: call volume that spikes hard and fast after a storm, a chronic shortage of people to answer those calls, and a Spanish-speaking crew and customer base in many markets.

Who Should Care

Role: Owners, GMs, and office managers at residential and storm-restoration roofing companies, plus sales managers who depend on fast inspection scheduling.

Firm size: Roughly 3 to 75 crews — from single-market storm-chasing operations to regional roofing companies already running ServiceTitan for scheduling and CRM.

Current stack: ServiceTitan on Phones Pro or Contact Center Pro, with call volume that is anything but steady — quiet for weeks, then a hail or wind event that generates hundreds of inbound calls in days.

The pain this touches: Storm-surge call volume that outstrips any fixed-size office staff, plus a labor market where finding and keeping CSRs and estimators is already difficult before a surge hits.

Red flags: This isn't for you yet if (1) your business is closer to 100% commercial/insurance-adjuster-routed leads with minimal inbound consumer calling, where a phone-answering AI has little to book, (2) you don't run storm-restoration or reroof work where surge volume is the actual problem, or (3) you're not yet on a ServiceTitan phone tier that supports the Voice Agent, since the dashboard has nothing to report without it.

What Changes for Roofing Companies

Roofing call volume doesn't arrive evenly — it arrives in bursts after a storm, then goes quiet. According to ServiceTitan's release-hub documentation, the dashboard reports 8 measures in a single view — call volume, booked jobs, booking rate, revenue, call outcomes, escalation reasons, transcripts, and recordings — on Basic Phones, Phones Pro, and Contact Center Pro.

Sources: ServiceTitan Release Hub, Voice Agents Dashboard; ServiceTitan Release Hub, Spanish Language Support.

For a storm-restoration company, the escalation-reasons field matters more than it does for a steady-volume trade: it's the difference between "the AI is overloaded" and "the AI is correctly routing complex insurance-adjuster questions to a human," and only one of those is a problem worth fixing.

The Proof Point: What One HVAC Contractor Reported

Roofing companies don't yet have a published roofing-specific Voice Agent case study, but the one detailed deployment ServiceTitan has publicly released is instructive for any trade with volatile call volume. According to StockTitan's coverage of a ServiceTitan customer release, more than 90% of AI-handled calls became booked jobs for HVAC contractor Bill Joplin's Air Conditioning and Heating, across more than 1,300 calls in just over three months.

Source: StockTitan, ServiceTitan customer release, June 9, 2026.

The honest caveat: this is an HVAC contractor's steady, seasonal call pattern, not a storm-surge pattern. Roofing companies evaluating the Voice Agent should treat this table as evidence the underlying booking mechanics work, not as a benchmark for how it performs under a 10x call spike three days after a hailstorm — that's a scenario this specific case study doesn't cover.

Worked Example: A Hail Event, Three Days In

Consider a regional roofing company running ServiceTitan Contact Center Pro across four branches, three days after a significant hail event. Call volume has jumped from a baseline of roughly 40 calls a day to an illustrative 300 calls a day — homeowners wanting a free inspection, some already holding an insurance claim number, some just checking for damage.

If the Voice Agent converts inbound calls into booked inspections at a rate anywhere near the 90%+ figure reported for the one published deployment, then out of that illustrative 300-calls-a-day surge, roughly 270 would convert to booked inspections without an office team of four having to answer all 300 themselves — freeing the human team to handle exactly the escalations the dashboard's own escalation-reason field would flag, like complex adjuster disputes. This is illustrative arithmetic scaled from the sourced Bill Joplin's figures, not a roofing-specific benchmark ServiceTitan has published. On the data side, each converted call generates a job.created event in ServiceTitan's platform — the same webhook a manually booked inspection would trigger. A workflow that filters job.created records by booking source can route AI-booked storm inspections into a separate scheduling queue from walk-in leads, which matters operationally because storm-surge inspection routing usually needs geographic batching (grouping inspections by neighborhood) that a general dispatch queue doesn't handle by default.

The Labor Shortage This Sits Against

Roofing's staffing problem predates this release and shapes why an AI Voice Agent is worth evaluating in the first place. According to the Bureau of Labor Statistics' May 2025 occupational wage tables, median pay for roofers was $55,440 a year in May 2025, and BLS separately projects employment will grow 6% from 2024 to 2034 with about 12,700 openings projected each year — growth that assumes a workforce that shows up to fill those openings. A second federal-data source, O*NET OnLine's occupational summary, independently confirms the same 12,700 projected annual openings figure, the same $55,440 median wage, and classifies the occupation's growth as "faster than average," consistent with BLS's 6% estimate.

That assumption is under real strain. According to NRCA's coverage of Associated Builders and Contractors' workforce model, construction — roofing included — will need 349,000 net new workers in 2026 to meet anticipated demand, with ABC's chief economist noting that most of that need comes from retirements rather than new project demand.

Sources: Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025; Bureau of Labor Statistics, Roofers (employment projections); NRCA, citing Associated Builders and Contractors.

That's the case for why call-handling automation matters more in roofing than in a trade with steadier staffing: office and estimating staff are themselves hard to hire and retain, and asking that same tight labor pool to absorb a 5-10x call spike after every regional storm is a structurally weak plan regardless of budget.

Before and After: Storm-Surge Call Handling

Source: ServiceTitan Release Hub, Voice Agents Dashboard and Spanish Language Support.

Signal vs Speculation

Sourced facts (as of July 11, 2026):

• The dashboard reports 8 measures of AI call performance, available on all three ServiceTitan phone tiers in the USA and Canada, per ServiceTitan's release-hub documentation

• Spanish-language booking is documented for the USA only

• One HVAC contractor reported a 90%+ booking rate and 72% full-automation rate across 1,300+ calls in roughly three months — no roofing-specific case study has been published

• Median roofer pay is $55,440/year (May 2025) with 6% projected growth, while the broader construction industry needs an estimated 349,000 net new workers in 2026, per BLS and NRCA/ABC

Our read: roofing's call pattern — long quiet stretches punctuated by storm-driven surges — is arguably the strongest fit among the trades this release touches, precisely because staffing up temporarily for a surge has never worked well and the labor shortage behind it isn't easing. Over the next 12-36 months, the roofing companies that benefit most are the ones that treat the dashboard as a storm-event scorecard — checked after each surge, not just once at setup — rather than a one-time deployment decision. Firms already routing inspection-booking data through US Tech Automations workflows to trigger a follow-up sequence or update a CRM pipeline stage will find the dashboard's call-outcome data plugs into that same routing logic without a rebuild.

Whether AI-handled storm calls convert at anything close to the one published non-roofing case study's rate is the real open question, and it's one only a roofing-specific deployment, run through an actual storm season, can answer.

Related Reading

Booking the inspection is only the first step; keeping that customer engaged afterward is where roofing companies often lose ground. See why happy customers never get asked for referrals and stopping churned customers in roofing for what happens after the AI books the call. On the operations side, the best helpdesk software for roofing companies and stopping duplicate data entry in roofing cover the systems that need to receive the dashboard's booking data cleanly.

Companies pairing this with US Tech Automations' customer-service workflow automation can route the escalation-reason field straight into a claims-triage queue the moment a storm-surge call gets kicked to a human — the specific step that turns a dashboard reading into a faster response during the exact week response speed matters most.

Key Takeaways

• Roofing's storm-driven call pattern is a strong fit for the dashboard's booking-rate and escalation-reason visibility, even though no roofing-specific case study has been published yet

• One HVAC contractor reported a 90%+ booking rate and 72% full-automation rate across 1,300+ calls — treat it as evidence the mechanism works, not a storm-surge benchmark

• Roofing's labor shortage (349,000 net new construction workers needed in 2026, per ABC/NRCA) is the structural reason surge staffing doesn't scale, making automated call handling more relevant here than in steadier trades

• The escalation-reason field is the most useful new data point for triaging complex insurance-adjuster calls away from routine inspection bookings

• Spanish-language booking is USA-only in this release; the dashboard itself covers USA and Canada

• Value depends on reviewing the dashboard after each storm event, not just checking it once at setup

Frequently Asked Questions

Does the ServiceTitan Voice Agents Dashboard help with storm-surge call volume?

There's no published roofing-specific case study, but the mechanism — booking-rate and escalation-reason visibility per call cohort — directly addresses the problem of verifying AI performance during a short, intense surge, according to ServiceTitan's documentation.

Is there a roofing-specific case study for the ServiceTitan Voice Agent?

Not as of July 2026. The one detailed public case study is an HVAC contractor, Bill Joplin's Air Conditioning and Heating, reported via StockTitan, which reported a 90%+ booking rate.

Can the Voice Agent handle Spanish-speaking homeowners after a storm?

Yes, in the USA, on Basic Phones, Phones Pro, and Contact Center Pro, according to ServiceTitan. It detects the caller's language and completes the booking without escalating to a human.

Why is roofing's labor shortage relevant to an AI phone feature?

Because surge staffing for storm response competes with an already-tight labor pool. According to NRCA's coverage of ABC's workforce model, construction — including roofing trades — needs an estimated 349,000 net new workers in 2026, making temporary surge hiring an unreliable plan.

What does the escalation-reason field actually show?

Per ServiceTitan's documentation, it categorizes why a call was handed to a human — which, for a roofing company, is the difference between the AI being overloaded and the AI correctly routing a complex adjuster question.

How fast can a roofing company set up the Voice Agent before storm season?

The one publicly reported implementation, per StockTitan, took approximately 20 minutes — though that figure comes from an HVAC deployment, not a roofing-specific one.

Conclusion

Roofing's call pattern — quiet, then suddenly overwhelming — is exactly the shape of problem a checkable AI phone agent is built for. The dashboard doesn't change whether the AI can handle a storm surge; it changes whether a roofing company can prove it did, and where it didn't.

See how agentic workflow automation from US Tech Automations routes storm-surge booking and escalation data into a claims-triage workflow — so the days right after a hailstorm are handled by process, not by however many people happen to be in the office.