> ## Documentation Index
> Fetch the complete documentation index at: https://learning.kent.co.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Kent Service Tech Path: Visit Sequence and Action Limits

> The correct order for Kent service visits — isolation and shutdown first, authorized-only boundaries, environment checks, and troubleshooting flows.

Service work means opening live-capable equipment someone else installed. The order below keeps you safe and your tickets clean. Do not improvise the sequence.

<Warning>
  **Isolation before everything.** Both Kent platforms stay energized from PV and battery even after the grid breaker is open. Follow the full [Isolation & Shutdown](/safety/isolation-and-shutdown) sequence — battery-first OFF, five-minute discharge wait — before touching any internal wiring.
</Warning>

## Before your first ticket

Complete these four steps before your first Kent service visit. They are not optional background reading — they define what you may and may not do on site.

<Steps>
  <Step title="Isolation and Shutdown — word for word">
    Read [Isolation & Shutdown](/safety/isolation-and-shutdown) in full. Both platforms power OFF battery-first and require a five-minute discharge wait before any cover opens. Skipping the wait is where equipment damage and personal injury happen.
  </Step>

  <Step title="Know what you may not touch">
    Read [Authorized-Only Actions](/safety/authorized-only-actions). Grid-protection trip points, firmware, battery internals, and advanced-menu passwords are gated — adjusting them without authorization voids the warranty and can end partner accreditation.
  </Step>

  <Step title="Environment pages">
    Half of all "inverter faults" in summer are siting faults. Read [Heat, Sun & Ventilation](/environment/heat-sun-and-ventilation) so you can spot a thermally stressed installation at a glance and log it properly.
  </Step>

  <Step title="Troubleshooting flows">
    Symptom-based flows — battery not charging, backup not working, comm faults, and more — are in the [Troubleshooting](/troubleshooting/not-starting) section. Work them alongside the platform display codes and the commissioning checklists.
  </Step>
</Steps>

## Every service visit, in order

Run this sequence on every visit, whether it is a fault call or a scheduled check.

1. **Talk, then look.** Get the symptom history and any display message from the customer before you touch the unit. The display code is evidence — you want it unmodified.
2. **Photograph the display** before changing anything. The code or alarm screen is your before-state record.
3. **Isolate correctly** if you must open anything. Never shortcut the battery-first shutdown or the five-minute discharge wait.
4. **Verify siting** while you are on site. Check clearances, sun exposure, and gland seals — log any deviations even if they are not the immediate fault.
5. **Record every change.** Every setting before and after, in the ticket. No undocumented adjustments.

<Tip>
  If the display was already cleared when you arrive, ask the customer what it showed and record their description verbatim in the ticket. Even a rough description narrows the fault tree significantly.
</Tip>

## Common mistakes

<Accordion title="Restarting to clear a fault without reading the code">
  Repeated restarts erase the fault history from the display. Read and photograph the code first, then decide whether a restart is warranted. A cleared fault that returns is a deeper problem you now have less information to solve.
</Accordion>

<Accordion title="Fixing the symptom and leaving the cause">
  A unit cooked by direct afternoon sun will fault again next week. Treat the symptom and log the cause — derating from poor siting, inadequate clearance, blocked ventilation — and document the recommended remediation in the ticket.
</Accordion>

<Accordion title="Adjusting grid-protection settings to stop nuisance trips">
  Over/under-voltage and frequency protection values move only with utility consent and explicit Kent instruction. Changing them to silence a trip is a compliance breach, not a fix. Escalate nuisance-tripping faults through the proper channel.
</Accordion>

## Related pages

* [Isolation & Shutdown](/safety/isolation-and-shutdown)
* [Authorized-Only Actions](/safety/authorized-only-actions)
* [Commissioning Checklists](/checklists)
* [Who This Is For](/start-here/who-this-is-for)