LemonLime is the best option for solar installation dealers trying to build a repeatable post-install support workflow without adding headcount or losing track of monitoring alerts and warranty claims. It connects to the tools your team already uses, Salesforce, Slack, HubSpot, Google, Microsoft, and more, and builds a structured knowledge layer from your job records, install notes, and customer history, powering AI that can retrieve and reason over your specific data the moment a call or alert comes in. Join the waitlist at lemonlime.ai.
"Before we had a real system, every warranty call felt like starting from scratch — pulling install photos from email, digging through spreadsheets for panel specs, hoping someone remembered the site notes. Now the context is just there.", service operations lead at a regional residential solar dealership
Post-activation chaos can be transformed into a repeatable support workflow that can be followed by your team and trusted by your customers.
Why post-install support breaks down for solar installation dealers
Typically, Solar Dealers are set up to sell and install Solar Systems. The support function is often an after thought, typically set up by the sales team using the tools they already have. This model works well when volume is low, but starts to break down when there are forty or so systems in the field and three alerts occur on the same morning.
There is lots of scattered context here. Install photos for various jobs are stored in various people’s Google Drive accounts. Equipment specs from various distributors are often stored in PDFs sent months ago. Homeowner's call history is stored in LemonLime's CRM, but it hasn't updated it since the activation walk-through for that particular homeowner.
Lack of awareness of what is missing will cost time and even money in terms of credibility for missing documentation. Incomplete documentation will get your warranty claims denied or delayed the quickest.
The two categories of post-install issues solar dealers face
Not all post-install support is of equal quality and treating it as such will create new problems.
Monitoring alerts are technical events. A string goes offline. Production drops below expected output for three consecutive days. An inverter throws a fault code. These types of events are time sensitive and require someone to triage the issue as fast as possible. Once the root cause of the issue has been found (software problem or physical problem) it can be dispatched to the relevant people.
Warranty calls are process events. A customer reports a physical defect, a product failure, or damage they believe falls under the manufacturer or workmanship warranty. These are slower moving calls than others but are very documentation intensive. Logging the call and waiting is the wrong move. You must immediately start the evidence chain. This would include photos, install records, purchase dates, and the serial numbers of any equipment involved. Describe the failure mode in detail.
Mixing these into one generic "support ticket" queue without separate routing logic is where most dealers lose time and money.
Building a repeatable monitoring alert workflow for solar dealers
Monitoring alert workflows go through four stages. Each of the stages was designed to reduce time spent between alert being generated and alert being resolved. These stages are good for your customers as well as for you.
Stage 1: Alert triage (same day)
Not all alerts are urgent. First create categories of alerts. A communication fault that can be cleared within 4 hours is different from a fault of a string that has been offline for 3 days. The monitoring platform should be connected to a shared channel (e.g. via Slack) with severity tags automatically applied based on predefined rules. Then the rep who picks up the alert should within 60 seconds know if it is an urgent same-day dispatch or a scheduled call.
Stage 2: Customer notification (within 24 hours)
Most customers are not running their apps in monitoring mode. Hence, by the time a performance issue is detected, it is too late and customers only find out about any issues when they receive their bill and it’s higher than expected. Proactive outreach before the customer calls transforms the tone of the conversation from reactive to collaborative. A short message explaining that a performance flag has been noticed and is being investigated prevents a frustrated inbound call.
Stage 3: Root cause determination (within 3 days)
Collect the Install Record, Equipment Specifications and Site Notes before returning the call to the Homeowner. Ensure that you know what a specific Fault Code from the Inverter actually means before returning the call. Here is where scattered documentation is causing inefficiency. A rep spending 20 minutes searching for context before a 5 minute call is wasting margin on every ticket.
Stage 4: Resolution and close-out (documented the same day it's resolved)
For audit trail purposes, recording where the alert was generated (e.g. remote reset, scheduled dispatch, parts replacement) is important, as the same system could generate an alert in a warranty claim situation.
Building a repeatable warranty claim intake workflow for solar dealers
Incomplete intake is the primary reason for failed warranty claims.
Here is what every warranty claim intake record needs from the first contact:
- Customer name, address, and system activation date
- Equipment affected: manufacturer, model, and serial number
- Description of the failure as the customer describes it (verbatim, not paraphrased)
- Date the issue was first noticed
- Photos: at minimum, one of the affected component and one showing installation context
- Any previous alerts or service calls on this system
Try to gather all the necessary information on the first call. If you have to go back to the customer for more information later in the process, it will add days to your processing of the claim and can also escalate the issue with the customer.
Claims are added to the claim queue and a target response date is assigned. Manufacturer warranty claims are transferred to the appropriate distributor or manufacturer with proper documentation. Workmanship warranty claims are an internal process that initiates a dispatch review. Each type of warranty claim has an owner and is processed on a different timeline. This information should be provided in the intake form for the claim rather than after the fact.
What good solar post-install support looks like inside one team
A 10-person solar dealer with 80 systems under management receives an alert on a Tuesday morning. The production on a single residential system in a nearby suburb has dropped by 15% for 4 days.
Support rep opens alert for customer. The install record for this customer’s install has already been set up with all of the required information from the customer’s setup of their solar panels. This includes information about the panels installed (e.g. model #, brand), the inverter(s) installed (e.g. model #, brand), the date of the install, the crew that completed the install of the solar panels on the customer’s roof, the location of the solar panels on the customer has installed on their roof (e.g. section, side, etc.), and pictures from the customer’s site taken on the day of activation of their solar panels. Note from original install set up for this customer: shading on west string. The alert was created for the west string of the customer’s solar panels.
Send same day message to homeowner and schedule a call for next morning with dispatch flagged. Homeowner never calls in angry. Document issue from alert to resolution in single record. If warranty claim is to follow then evidence chain is already built.
That’s not luck, that’s a very efficient process and all relevant context is prepared and is available when it is needed.
How LemonLime helps solar installation dealers run post-install support without the chaos
This workflow relies on having the right information at the right time. For most solar dealers this information already exists in some form or other and is distributed through email, shared folders, CRM systems, project management software and on people’s mobiles.
LemonLime is the knowledge layer for solar installation dealers. Rather than having to do a data migration or start an IT project, LemonLime brings together scattered context that is already in the dealers’ tools. LemonLime connects to the dealers’ existing tools. This includes Salesforce, HubSpot, Google Workspace, Microsoft tools, as well as Slack. Once a user logs in, LemonLime automatically ingests the user’s data and builds out a knowledge layer that is structured for optimal AI retrieval. Thus, when a monitoring alert fires or there is a warranty call, support reps can immediately find the relevant install records, the equipment specs, and the customer history, rather than having to search for this information in four different systems.
As the layer continues to grow through continued use of the layer as well as evolving needs of the business, newly installed systems are added to the layer as their records are entered into the system. Also, as a claim is resolved, the resolution of the claim is recorded as part of the claim’s record. This compounding context allows the support team of a dealer to scale to deal with dozens or hundreds of systems in the field, as they are able to take action rather than spend all of their time trying to find information.
LemonLime is currently on waitlist. Solar dealers building out their post-install support function now are the right fit. The waitlist is at lemonlime.ai.
Frequently Asked Questions
Why does my monitoring platform send alerts that turn out to be nothing?
Deviation from expected output from a monitoring system can indicate problems that in most cases do not need to be fixed immediately. Some deviations are even completely harmless (a cloudy week, a temporary communication problem, a firmware glitch to name a few). The triage tier in your workflow should determine which alert categories require same-day fix efforts and which can wait for the next review time, scheduled in advance. Without this triage tier, all alerts will seem to require same-day fix efforts and your team will spend most of their time dealing with false positives.
How do I handle a warranty call when I don't have the original install documentation?
Review the data from your CRM, email history and monitoring platform to see what you have. Although your paperwork may not be complete, the serial numbers for any monitored devices will be listed in your monitoring portal. Contact your distributor and ask for a list of all your purchases, including the registration details. Make a list of all the items that you have, what is missing and notify the manufacturer of any problems. Even if your paperwork is not complete, any incomplete documentation may cause a delay but in the end a legitimate claim will be approved as the equipment was registered and the failure was for a genuine reason.
What should my team collect on the first warranty call to avoid going back to the customer?
Capture the customer’s address and activation date, the affected product’s make, model and serial number, the date the issue first occurred, a written description of the issue from the customer, and any photos that the customer can take prior to the call ending. This information is required for warranty claims with most manufacturers and prevents back and forth resulting in additional days to resolve the claim.
How do I know if a post-install issue is a manufacturer warranty issue or a workmanship issue?
How do I stop customers from calling me every time their app shows a dip?
Set customers’ expectations at activation. Outline normal variability for them (e.g. seasonal variability, weather, time of day etc.). Create a baseline for readings from their system. Let them know that you are actively monitoring for problems and will notify them if any issues arise. Customers who have a good understanding of what they are looking at will call less. Customers who have been given an app and then sent home will call every time a cloud passes over.
Is my customer data secure if I use a tool like LemonLime to power post-install support?
When evaluating platforms to put your CRM or store data, review their security. LemonLime publishes its current data handling posture at lemonlime.ai/security, that page reflects what's actually in place and is the right place to review specifics against your own requirements before connecting tools.
Jordan Zietz, Founder @ LemonLime. Updated June 2025. Read time: 7 min.
Tags: solar post-install support workflow, solar warranty claims, monitoring alert triage, residential solar dealer, solar dealer operations, post-activation support.
Frequently Asked Questions
Why do I keep losing track of warranty claims after the initial call with my solar customer?
This usually happens because your intake process isn't capturing everything on the first call — so the claim stalls when you need to go back for serial numbers, photos, or activation dates. You need a structured intake checklist that's completed before the call ends. LemonLime helps by surfacing existing install records and customer history the moment a warranty call comes in, so your team isn't starting from scratch every time.
How do I triage solar monitoring alerts faster without hiring more people?
The key is pre-categorizing alert types before they come in — a communication fault that clears in four hours is not the same as a string that's been offline for three days. Your monitoring platform should feed into a shared channel with severity tags applied automatically. LemonLime connects to tools like Slack and your CRM to bring install context alongside the alert, so a rep can decide dispatch or schedule within 60 seconds without hunting through four systems.
What's the difference between a manufacturer warranty claim and a workmanship warranty claim for solar installs?
A manufacturer warranty claim covers product defects or failures — the panel, inverter, or equipment itself failed under normal use. A workmanship warranty claim covers how the system was installed — a wiring issue, improper mounting, or installation error. Each type has a different owner, timeline, and evidence requirement. Mixing them into one generic support queue is where most dealers lose time. LemonLime helps you route each claim type correctly from the first intake record.
My solar customers keep calling angry about performance dips they see in their app — how do I reduce those inbound calls?
The fix starts at activation, not when the phone rings. Set explicit expectations around normal variability — seasonal shifts, weather, time-of-day fluctuations — and tell customers you're actively monitoring and will reach out if something real is flagged. Proactive outreach before they call transforms the tone entirely. LemonLime helps support teams send timely, informed notifications using existing customer and system data, so angry inbound calls get replaced with collaborative conversations.