Define service categories, entitlement checks, priority, and triage evidence.
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.
- 01Receive and classify the service needCurrent decision
- 02Identify system, equipment, and entitlement contextNext controlled handoff
- 03Triage and plan the responseNext controlled handoff
- 04Perform approved field or remote workNext controlled handoff
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.
- 01Receive and classify the service need
- 02Identify system, equipment, and entitlement context
- 03Triage and plan the response
- 04Perform approved field or remote work
- 05Resolve commercial, warranty, and follow-up actions
What to configure
Specific controls, qualified by implementation.
Link installed equipment, diagnostics, prior visits, and approved design context.
Map work orders to qualified technicians, parts, time, findings, and resolution.
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.
- Installed system
- Installed equipment
- Service case
- Service work order
- Warranty claim
- Service coordinator
- Service technician
- Warranty administrator
- Define service categories and entitlement evidence.
- Map equipment, parts, and technician eligibility.
- Test warranty, paid, rework, return, and inherited-system paths.
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