Customer and service / Warranty and service

Solar warranty, maintenance, and field service workflow

Carry approved installation and equipment context into service so each case has the right entitlement, owner, field evidence, and commercial path.

Illustrative workflowWarranty and service
Record
Installed system
Installed equipment
Service case
Service work order
Current reviewReceive and classify the service need
Configured during assessment
  1. 01
    Receive and classify the service needCurrent decision
  2. 02
    Identify system, equipment, and entitlement contextNext controlled handoff
  3. 03
    Triage and plan the responseNext controlled handoff
  4. 04
    Perform approved field or remote workNext controlled handoff
Why this workflow breaks

Service teams need installed equipment, design, warranty, customer, prior-work, parts, and cost context before dispatch. A sales-only record cannot distinguish workmanship, manufacturer warranty, paid service, maintenance, or an inherited system.

Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.

Workflow sequence

Keep the handoff visible from first review to accepted outcome.

  1. 01Receive and classify the service need
  2. 02Identify system, equipment, and entitlement context
  3. 03Triage and plan the response
  4. 04Perform approved field or remote work
  5. 05Resolve commercial, warranty, and follow-up actions

What to configure

Specific controls, qualified by implementation.

01

Define service categories, entitlement checks, priority, and triage evidence.

02

Link installed equipment, diagnostics, prior visits, and approved design context.

03

Map work orders to qualified technicians, parts, time, findings, and resolution.

04

Route warranty, return, invoice, credit, rework, or upgrade decisions to the right owner.

Assessment output

A shared definition of the records, owners, and acceptance checks.

Records in scope
  • Installed system
  • Installed equipment
  • Service case
  • Service work order
  • Warranty claim
Roles in the decision
  • Service coordinator
  • Service technician
  • Warranty administrator
Checks before rollout
  • Define service categories and entitlement evidence.
  • Map equipment, parts, and technician eligibility.
  • Test warranty, paid, rework, return, and inherited-system paths.

Continue the workflow

Adjacent records rarely stop at one team.

Questions to settle

Questions to settle before configuring warranty and service.

Can service cases include systems installed elsewhere?

An inherited-system onboarding path can be assessed without fabricating an earlier sales or project history.

How are warranty and paid service separated?

Classification, entitlement evidence, approval, parts, labor, billing, and recovery rules can remain distinct throughout the case.

Can service cost remain linked to the original job?

Rework and warranty records can preserve original project context while finance defines the treatment in installation and service reporting.

Next step

Assess warranty and service using representative project records.

Bring the current records, owners, approvals, exceptions, and tools. The assessment turns them into a reviewable rollout boundary.
Book an assessment