Skip to content
English
  • There are no suggestions because the search field is empty.

Onboarding KPI - failed sessions

We monitor onboarding KPI. For Slow and Failed onboardings email is sent to support at the beginning of the hour. Upon arrival of this email next steps needs to be taken:

  1. Create a ticket in Hubspot mentioning that this site has been flagged by onboarding KPI.
  2. Check the status of the site and look into metabase sequence ( go to Metabase --> Onboarding KPI --> fill in the year and the week number " 2025-37" --> for new Installation put filter "N" (for re-occuring "R") --> Play , Press on the ID.

    Analyse the events.
  3. If the findings cannot be explained, we try to reach the installer. Explanable scenarios.
    1. Onboarding was started before the Gateway was powered on, e.g. during site creation
    2. Gateway appeared online but after start of onboarding there were no communication with it (presumably just turned off)
  4. Possible issues during onboarding
    1. If it turns out that installer had an issue with scanning panels, brute force scan can be offered, it must be shared that it takes time and in meanwhile dashboard will be showing zeros (whie production will be still occurring)
    2. In case if inverter was not found, auto detect can be applied.
    3. In case of not Taylor inverter, it can be that communication cable is not present or is faulty.
    4. Tango sites have problems as they have own network connected to the ethernet port of the gateway, Tango must do first some modifications on their side.
  5. Process all findings in hubspot
  6. Weekly during support meeting this topic is discussed. Summary of the findings must be shared in  this excel:
    1. Use tab for corresponding week (create new one if does not exist yet)
    2. There are two categories New sites (marked as "N" in metabase) and Old sites ("R")
    3. Update all fields: number of sites, What % within 15/5 min. etc.