A working day organized by technician
See scheduled work and technician assignments together. Availability and overlap checks help the dispatcher catch a conflict before a second job lands on the same worker.
Give dispatchers one place to triage the board, compare the right technician for each call, send assignment changes, and follow the job into the field. Plenum connects the schedule to route-aware booking, technician notifications, and the working appointment record.
Dispatching is not dragging colored blocks until the calendar looks full. The dispatcher is protecting a live plan. A no-cool call arrives, an install runs long, a technician becomes unavailable, or a customer changes access instructions. Each event can affect assignments, drive time, and the messages already sent to the field.
The useful system keeps the decision and its consequences together. The dispatcher should be able to see the job, weigh technician fit, make the assignment, and know whether the field update entered a delivery path without rebuilding the story in a separate text thread.
Read the call, timing, property, and current board before deciding what moves.
Compare availability, location, skills, and load instead of assigning from memory.
Send the new assignment or changed plan through a notification tied to the job.
The schedule, assignment, notification, and field view operate on connected job data. That gives each role the context it needs without claiming the system can make every judgment for the dispatcher.
See scheduled work and technician assignments together. Availability and overlap checks help the dispatcher catch a conflict before a second job lands on the same worker.
Plenum scores appointment times by how they fit around nearby work, which helps build neighborhood clusters before the day begins. When it is time to assign, technician suggestions can be ranked by availability, distance, skills, and current workload to limit unnecessary drive time.
New assignments, reassignments, schedule moves, removals, and cancellations have worker notification paths. Configured email, SMS, and push channels keep changes tied to the job record.
Assigned technicians can open timing, address, contact details, scope, notes, instructions, checklists, line items without pricing, and job photos. The mobile workflow can also return prior service history for the same property or customer.
The job carries a durable status as work progresses. Field status updates return to the appointment record so the office can work from recorded state instead of a group-text guess.
A whiteboard, shared calendar, and group text can work for a small crew with a stable day. Everyone can see the broad plan, and there is little setup. The trouble starts when the number of technicians, appointment changes, or service territory outgrows what one person can hold in their head.
The failure is usually not dramatic. It is a set of ordinary gaps: two jobs placed on the same technician, a cross-town assignment that looked close on the calendar, a changed arrival window buried in a text thread, or no record showing whether the helper received the update. Dedicated HVAC dispatch software gives those decisions a shared record.
A calendar block can be moved without checking every assignment or overlapping window. Plenum checks assignment conflicts and availability before the change is accepted.
Street names and open times do not show route insertion cost. Route-aware slot scoring adds geography to the booking decision before the board fills up.
Group texts separate the message from the appointment. A job-linked notification path can record which channels were queued or why a channel was suppressed.
Evaluate the workflow with messy, normal service data. A prepared demo with one technician and two perfect jobs will not show how the product behaves when the board is full, reception disappears, or a notification cannot be sent.
Ask the vendor to start with an unassigned same-day call, not a polished dashboard. Count the actions needed to inspect the job, compare technicians, assign one, and verify that the message was queued. Then repeat it with three calls. A modal that closes after every assignment or hides the board is friction your dispatcher will feel every day.
Test a long customer name, an apartment unit, several contacts, detailed access instructions, multiple photos, and a job with no photo at all. The field view should remain readable and should not invent missing information. Confirm that the technician can tell which job, address, and instructions they are looking at before they tap a status action.
Do not accept “mobile friendly” as an answer. Ask what is available after the signal drops, which actions queue locally, how conflicts are resolved, and what the technician sees before a sync is complete. Basements, mechanical rooms, mountain roads, and new construction can all expose a workflow that quietly assumes perfect reception.
A success toast is not proof that a technician received the change. Look for delivery-channel settings, durable queueing, retry behavior, suppression reasons, and a clear office-facing outcome. The dispatcher needs to know when a worker was not reachable so they can use another channel before the truck goes to the old address.
Dispatch is not finished when a technician arrives. Ask how the appointment connects to the work scope, line items, completion state, and invoice. Re-entering job details after the call creates another opportunity for mismatched records. The useful test is whether office and field staff can follow one job from booking through billing.
An assignment is only useful if the technician can act on it. Plenum's worker job view can carry schedule timing, customer and property details, work scope, dispatch notes, access and safety instructions, checklists, line items, and photos. The endpoint verifies that the worker is assigned before returning the job. The mobile appointment workflow also provides role-scoped service history from prior work tied to the same property or customer.
As the technician updates job status, the office has recorded progress on the same appointment. That common record is the practical connection between dispatch and later operational work, including invoicing, without pretending a status replaces a conversation when the situation needs one.
HVAC dispatch software helps the office assign jobs to technicians, see the working day, communicate changes, and follow job status. Strong dispatch software also gives the dispatcher location, availability, workload, and job context before an assignment is made.
Scheduling reserves the time and capacity for a job. Dispatching decides who will handle it and manages the live day as priorities, locations, and timing change. Plenum connects both workflows to the same appointment record.
Route-based dispatch considers geography before the truck moves. Plenum scores booking slots by route insertion cost around nearby appointments to build neighborhood-focused days, then gives dispatchers technician suggestions that can account for availability, distance, skills, and current load. Actual drive-time results depend on territory and job mix.
Yes. Plenum has worker notification paths for new assignments, reassignments, schedule changes, removals, and cancellations. Delivery can use configured email, SMS, or push channels, and the system records queued and suppressed outcomes for the office workflow.
Yes. The worker portal can show assigned job timing, customer and property details, work scope, line items without pricing, notes, instructions, checklists, and appointment photos. The mobile workflow can also return role-scoped service history tied to the property or customer.
Plenum checks assignment windows for overlaps and technician availability. Authorized administrators can override a conflict when necessary, with the conflict presented as a warning instead of silently ignored.
Bring the calls and edge cases your team handles every day. See how assignments, route-aware scheduling, worker messages, and job details stay connected.
View Pricing