The plenum for HVAC operations.

PlenumOps is your company's virtual plenum, carrying the right job context from the first call through dispatch, field service, billing, QA, and truck stock.

Your field-service platform remains the source of truth. PlenumOps coordinates the handoffs around it.

Book a demo Follow one service job

Works with the field-service platforms your team already knows

ServiceTitan

Keep one service job together across five handoffs.

A no-cool call should become a complete service record and a replenishment task. Each team adds to the same job information instead of rebuilding it.

Front office

Captures the symptom, equipment clues, urgency, and preferred arrival window.
Dispatch

Matches the job with technician skills, drive time, workload, and useful truck stock.
Field

Records diagnosis, readings, photos, equipment data, and parts used at the jobsite.
Billing and QA

Reviews invoice language and required evidence before the record is written back.
Inventory

Turns confirmed parts usage into a truck-stock update and a replenishment task.

Support the work between your teams.

PlenumOps gives each team a complete input and a reviewable output without adding another board to watch.

Turn a missed call into a dispatchable request.

After-hours and overflow calls often leave dispatch with a phone number and a vague message. PlenumOps can continue the conversation, collect service-specific context, and attach it to the request for office review.

Preserve the homeowner's own description
Ask about equipment, symptoms, and safety concerns
Keep a human in control of booking and escalation

Call desk / Follow-up intake Overflow queue

Prepared transcript and call context

Dispatch review Unassigned

PlenumOps Can you describe what the system is doing?

Caller “Upstairs is 82°. The outdoor unit hums, but the fan barely turns.”

System: Split heat pump
Observed: Outdoor fan turns slowly
Attention: Same-day review requested

Next office actionOffer the next available arrival window

Confirm arrival window

Build the field record where the work happens.

Technicians can capture voice notes, equipment plates, readings, and required photos without composing long summaries on a phone. Evidence stays available through a weak connection and syncs when service returns.

Capture notes while hands stay on tools
Structure model and serial information
Keep incomplete requirements visible before closeout

9:41LTE 87%

Today's job · Stop 3

1420 Cedar Ridge Lane

Voice note0:32

Run capacitor measured 31 µF. Replaced 45/5 µF capacitor and verified operation.

Closeout evidence 2 of 3 collected Equipment plate Final readings Disconnect photo

Closeout paused Add the required disconnect photo when safe.

Give the office a packet it can verify.

Field details can arrive as invoice-ready language, linked evidence, and a parts movement for review. Billing, QA, and supply work from the same service record instead of interpreting separate notes.

Draft clear work-performed language
Surface missing evidence before writeback
Carry confirmed parts usage toward replenishment

ops.plenumops.test / Review Back office

Job 2087 · Truck 04

QA gate 1 item open

Review area	Prepared detail	Gate
Invoice	45/5 µF capacitor replaced; operation verified	Ready
Evidence	Readings attached; disconnect photo still required	Open
Inventory	Truck 04 capacitor count changes from 3 to 2	Ready

Keep your field-service platform in place.

Job information moves from your field-service platform into the workflows that need it. Your team stays in control, and approved updates return to the original record.

Your source of truth

Field-service platform

Owns customers, jobs, schedules, pricebooks, and the official service record.

ServiceTitan

Job context

Approved updates

The operating layer

PlenumOps

Reads the job information needed for each handoff, keeps the record together, checks required steps, and prepares updates for review.

Prepared work

Human review

The people in control

Operating teams

Keep authority over schedules, field work, invoices, quality checks, and replenishment.

Front office
Dispatch and field
Billing, QA, and supply

The connection runs both ways. PlenumOps reads only the information needed for the workflow and returns changes through the review path your team approves.

Scale the operating model to your fleet.

This transparent planning model scales a reference scenario by active service vans. It is an illustration, not a forecast or promise of savings.

Active service vans

vans

Illustrative annual opportunity

$647,000 About $53,917 per month

Call capture: $290,000
Field admin capacity: $165,000
QA and callback prevention: $72,000
Permit and rebate admin: $36,000
Supply-run capacity: $84,000

Read the assumptions

The reference scenario is $32,350 per van each year: $14,500 from call capture, $8,250 from field admin capacity, $3,600 from QA and callback prevention, $1,800 from permit and rebate administration, and $4,200 from supply-run capacity.

Actual results depend on call volume, booking rate, labor cost, callback frequency, install mix, geography, seasonality, current processes, and adoption. Use your own operating data before making a purchasing decision.

Bring your field-service setup and one example job.

We will trace the job from the first call through dispatch, field work, office review, and the final service record.

Show us the handoff that slows your team down
See where PlenumOps would read, coordinate, and return details
Leave with a concrete workflow map for your operation

30 minutes with the PlenumOps team

Book a demo