01The HVAC Operational Environment
HVAC offices coordinate several kinds of work at once. A planned maintenance appointment, a repair request, and an installation inquiry carry different customer expectations, preparation steps, and safety considerations. They are job contexts, not automated workflows in Roll On Call. Staff create the customer and job records, choose the service location, enter the reported scope, and decide how each request belongs on the schedule. Like locksmith businesses, HVAC companies must apply trade knowledge and company policy when circumstances change.
Roll On Call is limited to the shared record around that work. Staff may enter a reported equipment type, symptom, access instruction, or prior service detail. They may then review the schedule and assign a technician through a process. Our field service management software guide describes the broader administrative pattern.
Texts to technicians and customers go out from your business number on Team and Pro, which include integrated phone and SMS with one included number. Solo does not include integrated phone or SMS, so a Solo owner works from the job record and calls or texts from their own phone.
02Managing the Seasonal Workload
The first hot week or hard freeze can bring a mix of no-cooling calls, no-heat reports, maintenance appointments, and existing installation work. Intake staff can create records for these requests and select the location where service is requested. Useful intake distinguishes the customer's words from confirmed technical facts. A caller may report weak airflow, an unresponsive thermostat, or an unusual sound, but the office should not turn that report into a diagnosis. This recordkeeping approach complements customer record management.
The dashboard gives staff a view of jobs they have created, scheduling choices, selected service locations, and recorded status. Dispatchers review the information, apply the company's priority rules, contact customers through the business's chosen channels, and enter schedule or assignment changes. During a seasonal surge, the value lies in maintaining usable records while people make the day-to-day decisions.
A practical seasonal intake rhythm starts with confirming whether the caller already has a customer record, selecting or adding the requested service location, and recording what the caller observes. Staff can note relevant access windows and customer contact context, then place the job for dispatcher review. If weather or workload changes the office's plan, staff make the customer call and edit the record. The software records those choices without making them.
03Emergency No-Heat and No-Cooling Calls
A no-heat report during freezing weather and a no-cooling report during extreme heat may require the office to apply its emergency intake procedure. Staff can create a job, confirm the requested service location, record callback details, and enter the customer's description. Details about occupants, odors, sounds, water, or other conditions remain reported unless the business later confirms them.
Dispatchers decide priority, technician assignment, and customer communication according to company policy. See emergency service management for related job context.
04Customer-Reported Symptoms and Intake
Customers usually describe what they can observe: rooms are warm, vents have little airflow, the thermostat display is blank, the furnace cycles, or an outdoor unit sounds unusual. Staff can place those observations in the job scope and identify them as customer-reported. Specific wording matters because a reported symptom is not a confirmed failed component, refrigerant condition, electrical fault, or control problem. Diagnosis begins under the HVAC business's technical process, not in the intake record.
Staff may also record the caller's account of equipment age, thermostat location, prior work, access limits, or steps already attempted. Later notes can identify what staff or field personnel reported through the company's own communication process.
05Diagnostic Intake vs. Technical Diagnosis
For a repair request, office preparation can include a job, the selected service location, the customer's reported symptoms, access notes, and relevant history. A standard job brief may carry selected details after a dispatcher assigns the job. None of that is a technical assessment. A qualified person follows the HVAC business's inspection, testing, safety, and diagnosis procedure at the appropriate time.
If the field team reports findings to the office, staff can add that context to the job record and update the recorded status. Estimates, customer authorization, warranties, parts selection, procurement, and return-visit decisions remain outside the product. Staff should enter only context their business wants retained, using the company's standards for technical accuracy and customer communication.
06Planned Maintenance Visit Preparation
A maintenance appointment differs from a repair call because the scope comes from the HVAC business's maintenance procedure or agreement, not from a software workflow. Staff can create the appointment as a job, choose the customer's service location, enter the agreed visit context, schedule it, and select an assignee. Any checklist, inspection sequence, filter policy, measurement standard, or agreement obligation remains the business's responsibility.
Staff decide when to contact a customer and manually create each future visit. Prior jobs or notes may contain equipment or filter context, but the team must verify current details. Preparation, parts checks, maintenance-agreement administration, and any rescheduling remain human tasks under the company's procedures.
07Installation Inquiry Handoffs
An installation inquiry may begin with a customer asking about replacement, or it may follow information reported during a repair visit. Staff can record the inquiry and relevant customer or field context. They decide whether to create a separate job, whom to assign, and when to schedule the next business step.
Installation is a distinct job context. Roll On Call can hold scope, selected location, schedule, assignment, notes, status, and completion context around it. Qualification, surveys, pricing, authorization, licensing, safety, and equipment procedures stay with the HVAC business. Staff record scheduling decisions only after those decisions are made through the business's process.
08Residential and Commercial Context
Residential, commercial, and multi-unit properties produce different intake questions. A home request may involve a gate, pet, tenant, landlord, attic, or crawlspace. A commercial request may involve an on-site contact, loading area, restricted mechanical room, rooftop-access procedure, unit identifier, or operating-hours constraint. Staff can enter applicable reported or business-verified context in the customer, location, or job record according to company practice.
Office staff choose the service location and decide which context to include in an assignment or job brief. The HVAC business must verify access, site rules, equipment identification, technician qualification, and safe-work requirements through its own process.
09Multi-Location Service Management
Property managers, retail operators, and other customers may request HVAC work at more than one address. Staff can keep selected service locations with the customer record and choose the applicable location when creating a job. Intake should distinguish the requesting contact from the physical destination and capture a unit, suite, store, or building reference when the business requires one. Selection remains a staff action rather than an automatic match.
The office confirms the destination, selects the location, reviews relevant prior jobs, and follows the customer's authorization requirements. This is particularly important when different sites have separate contacts or access procedures. The multi-location management page covers this record structure in more detail.
Multi-unit work adds another layer. A street address alone may not identify the apartment, mechanical area, rooftop unit, or tenant contact involved in the request. Staff can enter the unit or site context supplied by the customer and include selected details in the job brief. Building rules, keys, escorts, roof access, shutdown permission, and equipment identification still require confirmation through the property and HVAC company's procedures.
10Preserving Service History
Repeat customers often refer to a previous visit, a familiar piece of equipment, or an unresolved concern. Staff can review prior jobs and notes associated with the customer or selected service location. That history may help the office ask whether the current request concerns the same address or equipment described before. It can also provide context for a dispatcher preparing a new assignment. See the field service CRM guide for the customer-record perspective.
History reflects what people entered at the time. Equipment may have changed, notes may be incomplete, and a customer report may differ from a field finding. Staff and qualified field personnel must verify current facts and use the HVAC business's procedures for warranty research, serial information, maintenance agreements, and technical records.
For a repeat customer, the office can compare the new request with prior context before scheduling. The dispatcher may pass selected history in a job brief, while field findings return through the business's communication procedure for staff to record. This office and field handoff keeps authorship clear: past notes remain historical entries, current symptoms remain reported until assessed, and completion context reflects what the team chose to record.
11Scheduling and Dispatch
On a mixed workday, dispatchers may review maintenance appointments, repair requests, installation jobs, and urgent calls together. Roll On Call displays job records and entered scheduling context so the office can make choices. A dispatcher sets timing and selects an assignee based on the information and policies available to the business.
When conditions change, a person reviews the schedule, contacts affected people, and enters any reassignment or timing change. The HVAC business is responsible for staffing decisions and customer commitments. Our dispatch management page explains this model.
12Technician Assignment and Rescheduling
Technician assignment is a decision made by the HVAC business. Staff review the reported scope and their own records or knowledge, then select an assignee for the job. The business maintains qualification records and decides what supervision, credentials, tools, and safety preparation are required.
A visit may take a different amount of time than the office expected, weather may affect travel, or a customer may request another date. The dispatcher determines what to change and communicates through the business's chosen channels. Staff can then edit the schedule or assignment. No technician self-update, automatic reassignment, or availability check is implied. The field workforce management page discusses related office and field coordination.
13SMS Job Details and Field Communication
After a person makes an assignment, the office can send a job brief with selected details such as the service location, reported scope, and access context. Staff decide what belongs in the record and message. Sensitive or safety-critical content should be handled under company policy.
The office should use its own confirmation method when urgency or safety calls for it. A later schedule or job-record change also should not be treated as proof that a technician saw an earlier message. See technician communication for more on this channel.
14Recording Progress and Team Status
Team-recorded job status gives the office an administrative reference based on a human entry. The HVAC business decides when and why staff update it and how that information is used.
Because status is manually recorded, it can be incomplete or out of date. Dispatchers use judgment and direct communication when they need current confirmation. Rather than assume universal status names, each office should follow the conventions and permissions established for its own users and keep technical conclusions in the business's appropriate records.
15Completion Context and Handoffs
When the field team communicates what happened during a visit, an authorized user can enter completion context in the job record. The note might distinguish work reported as performed from an open customer question or a business decision still required. Staff may also record a job status according to office procedure. These entries support an office handoff but do not certify workmanship, equipment condition, or customer approval. The job management overview covers the broader record.
Repair, maintenance, and installation records should preserve their different contexts. Any recommendation, unresolved condition, material need, or next step is entered by staff based on information received through the company's process. The business decides whether another visit, estimate, customer authorization, or technical document is needed and then makes any new record or scheduling choice.
16Invoices and Card Payments
When the visit is done, the office or the crew lead turns the job into an invoice. The customer, service address and line items come straight from the job, so nobody retypes them.
Customers can pay the invoice by card through Stripe, and the job shows whether it is sent, paid or overdue. The office sees which finished work is still open without checking a separate spreadsheet.
Roll On Call covers invoicing and collection for the work itself. Bookkeeping, payroll and tax stay in the accounting software the business already uses.
17The HVAC Operational Standard
An HVAC operating standard belongs to the business. It defines intake questions, emergency escalation, maintenance-agreement handling, licensing checks, assignment criteria, technical work, estimates, installations, materials, safety, completion documentation, and customer communication. Roll On Call has a narrower role: staff create customer and job records, select service locations, review prior jobs and equipment context, schedule and assign work through human decisions, send job briefs, and record job status, completion context, and invoices and payments.
Teams should label customer reports as reports, treat history as entered context, and verify current conditions through qualified people and company procedures. Schedule, assignment, and status entries remain human-maintained. Financial processing and trade-specific systems stay separate. This boundary keeps the product description focused on office and field coordination without assigning technical judgment to software. Explore other field contexts on the industries page or return to the home page.

