Appliance Repair Software

An appliance repair office may take requests for a refrigerator that stopped cooling, a noisy washer, a dishwasher that will not drain, and a range with an unresponsive control panel in the same morning. Each call has its own customer, appliance, address, access situation, and requested timing. Intake staff also need to distinguish the caller's description from anything a technician may later determine.

In Roll On Call, staff create the customer and job records and separately select the service location. They can record reported scope and chosen notes or instructions. A dispatcher reviews those entries, selects a time, and assigns a technician. Safety, diagnosis, qualifications, estimates, warranties, parts, and follow-up remain business responsibilities. See how the same boundary applies across other industries.

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.

Refrigerators, freezers, and wine coolers can prompt time-sensitive requests when stored contents may be affected. Staff can create a job, select its service location, and record what the caller observes. Reports may include constant running, a warm freezer compartment, frost buildup, unusual sound, or water beneath the unit. These are customer descriptions, not findings produced by the product.

A dispatcher can review that scope under the company's priority rules. The business handles technical inspection, sealed-system work, safety advice, and urgency decisions. If staff give the caller instructions, those selected instructions can be included in notes. Appliance repair and HVAC service both receive temperature-related reports, while each business determines its own response.

Requests for ranges, ovens, cooktops, and microwaves may mention an oven that does not reach its setting, a burner that will not ignite, or a flashing code. Intake staff can record those reports and the customer's statement that the appliance uses gas or electricity. Odors, sparking, heat, installation type, and control behavior should remain attributed to the caller until the business evaluates them.

The business sets gas and electrical safety procedures and decides whether to escalate a request. Dispatchers consult their own qualification information when assigning work.

Washer callers may describe a mid-cycle stop, failure to spin, vibration, or water on the floor. Dryer requests may involve no heat, unusual sounds, long drying time, or a drum that will not turn. Staff can identify the appliance category, create the job record, separately select the location, and enter the customer's words as reported scope.

Notes can include a stacked installation, tight closet, stairs, laundry-room access, call-ahead request, or other staff-selected instruction. The business evaluates site and safety requirements. If conditions change the plan, the team communicates directly and staff can update the job or schedule a return. See technician communication for the office and field handoff.

Dishwasher, ice-maker, and built-in coffee-machine requests may involve water supply or drainage. A caller may mention standing water, poor cleaning, a door leak, failure to fill, or an intermittent symptom. Staff can enter those details as reported scope and note that the request concerns a water-connected appliance.

A customer's theory, such as a failed pump, is not a confirmed fault. Staff can label it as the caller's belief, while the business decides how diagnosis is performed and where appliance work ends and plumbing work begins. Staff record human scheduling and assignment choices rather than an automated service determination. Similar service-boundary decisions appear on the plumbers page.

During intake, staff may ask a caller to read the brand, model number, and serial number from an appliance label. They can enter that text in notes or instructions. Staff can also record part context reported by a customer or later supplied by the team. Each entry is human-entered reference material, not verified equipment data.

A transposed character remains possible. Staff can revise a note when the team supplies better information and identify whether a number came from the caller or technician. Research, warranty checks, parts identification, compatibility, and purchasing remain business tasks.

A customer might say a refrigerator needs a defrost timer or request a diagnostic service visit after seeing a displayed code. Intake staff can record that language as the customer's report, not a confirmed diagnosis, approved repair, or parts instruction. The job scope can state that inspection was requested without predicting what the technician will find.

After the business performs its diagnostic process, the field team may report context to the office for staff to add to the record. Notes can identify what came from the caller and what was supplied after inspection. Diagnosis, estimates, authorizations, and customer explanations stay with the business. See job management for more on recorded job context.

A homeowner may request work at their own address, while a landlord or property manager may call about a tenant-occupied unit. Staff create the relevant customer and job records, then separately select the location where service is requested. The reporting contact, authorization contact, occupant, and site contact may differ, so notes can identify each person's role.

Staff can note a narrow access window, tenant call-ahead request, gate instruction, or landlord direction. The business reviews the notes and confirms access directly. Customer records and separate service locations are discussed further in customer management.

Appliance repair companies may also serve office breakrooms, small cafes, churches, community spaces, or similar light commercial locations. A customer might report an ice machine problem in a staff kitchen or a range issue at a childcare facility. Staff create the job, select the site, and capture the reported appliance scope as they would for a residential request.

Notes may specify a delivery entrance, front-desk sign-in, loading limits, operating hours, or a site contact. Dispatchers use their own knowledge to choose an assignment and time, and the business confirms site requirements. The electricians overview presents another field-service setting with commercial access constraints.

Property managers, housing operators, and local businesses may request service across several addresses. Intake staff can ask which property, building, floor, and unit need attention, then separately select the service location for the job. Notes can distinguish the reporting contact, authorizing contact, occupant, and person the technician should meet.

Dispatchers review the entered destination and communicate changes directly before adjusting the schedule or assignment. The multi-location management section offers additional context for teams serving several properties.

A repeat customer might call about a dishwasher visited a year ago or ask about a different appliance. Staff can review the customer record, prior jobs, previously selected service locations, and team-entered notes. That history can prompt intake questions, but it is earlier recorded context rather than a current equipment profile.

If an earlier note contains an oven model, staff can ask whether the current request concerns the same unit. The appliance, address, installation, or instruction may have changed. The business decides what needs checking during a visit and how history informs new work. The field service CRM guide covers customer and job record history in more detail.

A busy office may balance refrigeration requests, diagnostic service visits, routine washer calls, schedule changes, and parts installation returns. The dispatch board displays jobs, selected service locations, and current scheduling choices. A dispatcher reviews that recorded workload and chooses the order, time, and technician assignment under the business's own policies.

If plans change, a dispatcher decides which appointments to move, updates the selected schedule, and contacts affected customers through company procedures. A board change is not customer confirmation. This human decision model is central to dispatch management.

A diagnostic visit may end with the business deciding that another appointment depends on a part. After the field team reports that context, staff can note that work is paused, record the part description supplied by the team, and identify the proposed next step. Once the business confirms readiness, staff can create or schedule the appropriate return visit.

The business handles approval, purchasing, receipt, and customer follow-up. Staff update notes and scheduling choices only when people in the business decide that the information and timing are ready.

Assigning appliance work may require knowledge of sealed-system qualifications, brand experience, gas authorization, lifting needs, or company service boundaries. Dispatchers consult information maintained by their business and make the assignment themselves.

When traffic, access, job duration, or a changed customer request affects the day, the dispatcher communicates with the team and manually changes the appointment or assignee. There is no automatic reassignment or self-updating schedule. The office and field relationship is discussed in field workforce management.

After choosing an assignment, a dispatcher can send a job brief to the technician. It can include the selected service location, reported scope, and notes or instructions. A call-ahead request, access detail, or entered model text may be useful, but the dispatcher decides which available context belongs in the brief.

For urgent changes or safety instructions, the business applies its own direct communication and acknowledgement procedures.

Job status in Roll On Call is team-recorded. An office user can update it from information received from the field, or an authorized field user can select a status under company policy. The dashboard then displays that administrative state.

If a job reads as in progress, that means a team member selected the status. The business defines the meaning and update rules for its statuses. Dispatchers use direct communication when they need current field context, then the team can revise the record according to those rules.

When a technician reaches a stopping point, the team can report context to the office for entry in the job record. A note might say the technician reported the unit cooling at departure, that the visit ended pending a part, that no repair was authorized, or that another appointment may be discussed. The wording records what the team supplied rather than independently verifying appliance condition.

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.

The appliance repair business defines its operating standard. That standard covers intake, safety, diagnosis, technician qualifications, estimates, warranties, parts, customer authorization, technical work, and follow-up.

Within that boundary, staff create customer and job records, separately select service locations, capture reported scope, and enter notes or instructions, including model, serial, or part context. Dispatchers schedule and assign technicians. The office can send job briefs, while the team records status and completion context. Completed jobs become invoices that customers can pay by card through Stripe. Compare another service workflow on the garage door page, or return home.