Technical support
How a case is investigated, what evidence is needed, and when it belongs with HQ.
Support intelligence built for Solis.
Qlint brings together Solis technical knowledge, support experience, resolved cases and company procedures, so every support employee can understand more, troubleshoot faster and keep learning.
- Solis documentation
- Resolved support cases
- Product & firmware knowledge
- Company procedures
- Engineer experience
Qlint intelligence
Six kinds of Solis knowledge, held together.
Qlint is not a chat window on top of a document folder. Each domain below is read, structured and used when a case needs it.
Solis products
The hardware behind the cases, from residential hybrids to three-phase commercial sites.
SolisCloud
Monitoring, plant configuration and the data an engineer needs before drawing conclusions.
Company knowledge
The way Solis support actually works — regionally and at HQ.
Communication
Who is on the other side of the thread, and how Solis writes to them.
Continuous learning
Knowledge that moves forward as products, firmware and procedures change.
Start with a technical area.
Whether it is your first week or your fifth year, the same knowledge base is behind every area.
One method, from first message to what the team learns.
Qlint follows the same method a good engineer follows — and shows its reasoning at each step instead of jumping to an answer.
Understand
Read the thread and establish what is actually being reported.
Collect evidence
Model, firmware, plant data, measurements, timestamps, photos.
Troubleshoot
Work through the checks in an order that eliminates causes.
Identify root cause
Separate a confirmed fault from a plausible assumption.
Resolve or escalate
Close it locally, or hand HQ a case they can act on immediately.
Validate
Confirm with the installer or the plant data that it holds.
Learn
The pattern becomes knowledge the next engineer inherits.
Qlint supports the whole method — not only the reply at the end of it.
Jump straight into a technical topic.
The areas Nordic support meets most often. Each one opens the knowledge behind it.
It reads the case, not just the last message.
A static knowledge base waits to be searched. Qlint works out what this case is about, what has already been checked and what is still missing.
- The full support thread, in order
- What the engineer has already checked
- Product model and firmware version
- Plant information and measurements
- Previous cases with the same pattern
- Current Solis knowledge on the subject
- Who the recipient is
- What the next troubleshooting step should be
Example — how Qlint reads a case
- Inverter shuts down intermittently
- Solis-110K-5G-PRO
- Electrician has been on site
- Exact shutdown timestamps
- Firmware, grid alarms, historical telemetry
- Analyse logs and request timestamps
A draft reply is prepared from that investigation — with the sources it used — and a person reviews it before anything is sent.
Every resolved case can improve the next one.
Knowledge in a support organisation usually lives in people. Qlint keeps it where the whole team can reach it.
Support work
Knowledge
Qlint learns
The next engineer
How Qlint weighs what it knows
Qlint does not treat every source as equally true. When two sources disagree, the higher one wins and the difference is visible.
A reply that sounds like the colleague who is sending it.
Qlint learns the difference between writing to an installer, an electrician, an end customer, a distributor, HQ or a colleague — and it follows the thread it is already in.
“Hi Peter, thank you for your email. Could you send the inverter serial number and the time of the shutdown?”
“Hi Peter, I checked the values you sent. The grid voltage peaks at 253 V just before each shutdown, which matches the alarm in the log.”
No restarting the conversation in every reply, no repeated thanks, no template voice.
What Qlint currently understands
Sign in with your Solis account to see the live state of the knowledge Qlint holds for your organisation.
Sign inHelp Qlint understand Solis better.
The more verified Solis knowledge Qlint has, the more accurate its support assistance becomes. Anyone in support can add it.
Adding knowledge is not an administrator task. If you resolved something the team should not have to work out again, put it here.
Add knowledgeWhat Qlint does for each part of the team.
Technical Support Engineer
Case context assembled before you open it: model, firmware, what was checked, what is missing, and a draft to review.
New support employee
A structured way into the Solis ecosystem — products, SolisCloud, alarms and the support method used here.
Product Specialist
Recurring symptoms across cases, and a direct route to correct or extend the technical knowledge behind them.
Support Manager
Where the organisation repeats itself, where knowledge is thin, and what the team has learned recently.
HQ support
Escalations that arrive complete: what Nordic support already checked, with evidence attached.
Start where your work is.
Open the workspace