Answer: A useful solar follow-up should change the customer’s ability to decide. Send one corrected assumption, a normalized option comparison, an answer with its source, a request for one missing input, a clear revision note, or an honest close-the-loop message. Name the project and next action, respect consent, and avoid invented urgency or repeated generic nudges.
“Any thoughts?” transfers all the work back to the customer. They must reopen the proposal, remember the unresolved issue, decide which person should answer, and invent a next step. The salesperson learns nothing when the message goes unanswered.
A valuable follow-up carries one piece of the decision forward. It corrects a model input, answers a named question, compares two options on the same basis, requests a missing document, explains a revision, or closes the loop respectfully. The customer can respond with a fact or choice instead of writing a project review from scratch.
The six templates below are starting structures. Replace every bracketed planning instruction before use, verify every claim, and follow the consent, marketing, privacy, and record rules that apply to the recipient and jurisdiction. Do not paste a customer, figure, date, or urgency claim from another project.
Set the follow-up contract during the meeting
Agree the next useful follow-up before the call ends. Summarize the open decision, name the person who owns the next item, and agree on a useful timing cue. “I will send the revised shade comparison after our designer checks the southern tree line” creates a reason for contact. “I will check in next week” creates a calendar event without value.
Record the customer’s preferred channel and who else should receive project information. A homeowner may want a partner included. A commercial buyer may need facilities, finance, procurement, or an adviser. Confirm permission before forwarding bills, pricing, design imagery, or other personal and project material.
Keep project states distinct. A customer who is gathering information needs different contact from one who requested a revised option. An accepted proposal under technical review is not a sales chase. A closed or opted-out record should not re-enter an automated sequence because someone changed a pipeline stage.
The DOE homeowner solar guide frames a decision across site fit, bids, agreements, financing, and installer evaluation. Use the unresolved part of that real decision as the subject of the next message.
Message 1: the corrected assumption
Use this after the customer or reviewer corrects a bill, tariff, roof fact, equipment choice, shading input, or operating assumption.
Subject: Updated [project item] for [site or project name]
Hello [name],
You flagged that [specific prior input] did not match [current document or condition]. We updated [design/model/proposal revision] using [identified source and date]. The change affects [specific customer-facing result or scope] and leaves [important unchanged item] the same.
Please review [linked or attached artifact] and confirm whether [one factual question] now matches your record. If it does, [named next stage] can proceed. If it does not, reply with the document or detail we should use.
Do not frame every correction as a minor improvement. If price, scope, equipment, expected output, savings, financing, or obligations changed materially, say so in the opening. Preserve the previous released version and a reason for change.
Carry the model boundary with a revised number. “The annual modeled energy changed because the confirmed azimuth replaced the imagery assumption” is meaningful. “Great news, your production improved” treats a correction as a sales event.
This message earns contact because it closes a known evidence gap. It also tests whether the company’s change record is understandable outside the design team.
Message 2: the normalized option comparison
Use this when the customer is comparing two solar or storage options and the first proposal made differences hard to see.
Subject: [Option name] and [option name] on the same basis
Hello [name],
We rebuilt the comparison so both options use the same [load period, tariff source, design status, analysis period, or other shared basis]. The attached table shows only the fields that differ: [two to five decision dimensions].
The main tradeoff is [plain, qualified description]. Neither option resolves [open site, technical, finance, or contract condition]. Which objective should control the next review: [choice A] or [choice B]?
Normalize before claiming one option is cheaper, larger, or better. Confirm price boundary, system capacity, design, equipment, production method, tariff, financing, incentives, operating costs, and warranty or scope terms as applicable. Different definitions can manufacture a winner.
Avoid presenting three weak options merely to steer the customer toward a middle choice. Each option should be technically and commercially plausible under the company’s process. Explain who should choose differently and why.
Link to the active proposal revision rather than attaching another unlabelled file. The customer should be able to identify what the company is currently offering.
Message 3: the sourced answer
Use this after a customer asks a factual question about a tariff, incentive, equipment specification, warranty, approval process, finance term, or other source-controlled topic.
Subject: Source for your question about [specific topic]
Hello [name],
You asked [repeat the question accurately]. The current [utility, regulator, manufacturer, lender, contract, or other controlling source] states [narrow answer supported by that source]. You can review it at [descriptive link or identified document], accessed [date].
For this project, [explain the qualified implication]. [Named condition or responsible reviewer] still determines [unresolved part]. Would you like us to update [specific proposal field] using this information?
Use the source that controls the claim. A vendor blog is weak evidence for a regulation. An old proposal is not the source of a current utility rule. A manufacturer specification can describe that product but cannot prove a comparative claim without additional evidence.
Do not copy a long source passage into the email. Give the narrow answer, identify the controlling document, and state the project boundary. If the source is ambiguous or the team lacks authority to interpret it, say that a responsible adviser or reviewer is needed.
The FTC consumer solar guidance encourages buyers to inspect solar claims, agreements, and finance. A sourced response lets the customer do that inspection instead of accepting “our team says so.”
Keep customer updates tied to the active proposal
Explore how SurgePV supports proposal generation connected to design and modeled project inputs while your team controls review and customer communication.
Explore solar proposalsA connected solar proposal workflow can keep the active customer document near the design and modeled inputs behind it. The team still needs a named owner for each change, a review boundary, and a record of what was actually sent.
Message 4: the one-input request
Use this when one missing item prevents a meaningful design, production, price, savings, or storage review.
Subject: One item needed for [named project decision]
Hello [name],
We can complete [specific review or option] once we confirm [one input]. Please send [precise document, photograph, measurement, or answer], covering [period, meter, equipment, location, or other identity].
We use it to determine [plain mechanism]. Without it, [specific result] would remain an assumption. If the item is unavailable, tell us and we can discuss whether a preliminary scenario is still useful or whether the project should pause.
Ask for one coherent package, not an unexplained list. “Send bills” is vague. State the meter, billing periods, file format if material, and why the information changes the decision. Do not request personal information the project does not need.
Give a safe transfer route under company policy. Email may be inappropriate for certain financial, identity, or sensitive project documents. Do not ask customers to upload data to a personal drive or reply with credentials.
When the item arrives, acknowledge it and identify the next owner. Do not send another generic follow-up while the customer’s document waits in an internal queue.
Message 5: the revision note
Use this after survey, engineering, procurement, utility, customer, or equipment information changes the offered project.
Subject: What changed in [proposal revision]
Hello [name],
New [site/customer/manufacturer/utility/reviewer] information changed [specific project input]. Proposal [revision] now shows [specific changed scope or result]. It supersedes [prior revision] for [named decision].
The change does not alter [important stable part]. It still requires [open verification or approval]. Please review [two affected sections] and choose whether to [proportionate next action].
Do not bury an adverse change below a friendly introduction. A reduced layout, increased price, different equipment, altered production, or new exclusion belongs near the top. Use neutral language and preserve the reason.
Separate a design correction from a commercial upsell. If new evidence creates an optional opportunity, show the base correction first and the optional alternative separately. The customer should not have to buy something else to understand what happened.
The solar sales and design handoff guide provides a wider revision-control framework. The follow-up’s job is narrower: help the customer see what moved and what decision follows.
Message 6: the respectful close-the-loop note
Use this when the agreed decision date passed, the customer stopped responding, or the company cannot proceed without new evidence. Check consent, policy, and applicable communication rules first.
Subject: Closing the current review for [project name]
Hello [name],
We have not received [specific decision or item], so we will close the active proposal review on [supported operational date]. The current price, equipment, tariff, incentive, finance, production, or schedule assumptions may need to be refreshed before the project restarts.
We will retain or remove project information according to [company policy or agreement]. If you want to restart later, contact [channel] and reference [project identifier]. No reply is required.
Do not invent an expiry. The date can describe an internal queue action without claiming that the customer loses a benefit. If a price, financing term, incentive, or product reservation truly expires, cite the current controlling source and state the condition precisely.
Suppress further incompatible outreach when an opt-out arrives, following the applicable process and deadlines. A close-the-loop email is not permission to begin another campaign. Archive the project state so a new automation does not restart generic messages.
The final note should reduce pressure. It gives the customer a clean path back while protecting the company from presenting stale assumptions months later.
Apply consent and marketing rules by jurisdiction
Email and messaging rules vary. The U.S. Federal Trade Commission’s CAN-SPAM compliance guide describes requirements for commercial email, including truthful header and subject information and an opt-out mechanism. The United Kingdom Information Commissioner’s Office publishes direct-marketing and electronic-communications guidance covering privacy and electronic marketing.
These sources are jurisdiction-specific and not legal advice for every campaign. The company should maintain an approved communication policy that covers consent basis, existing-customer rules where applicable, sender identity, required address information, opt-outs, recordkeeping, channel, and suppression lists.
Separate service communication from promotion. A requested design correction or appointment detail may have a different purpose from a campaign offering storage or financing. Do not hide promotional content inside an operational update to avoid consent controls.
Respect frequency and channel preferences. A customer who asked for email should not receive unsolicited texts because email was unanswered. A customer who opted out should not remain in a salesperson’s personal reminder list.
Protect customer and project data
Follow-ups often expose the project through subject lines, links, attachments, and copied recipients. Use the minimum information needed. Confirm recipients before sending bills, site imagery, pricing, finance documents, signatures, or personal details.
The NIST Privacy Framework offers a general structure for managing privacy risk. Apply the company’s approved controls to collection, access, sharing, retention, and deletion. Do not claim certification or compliance merely because the team used a framework.
Use descriptive, controlled links. A recipient should know whether a link opens the active proposal, a source, an upload portal, or scheduling. Avoid public URLs containing sensitive values. Revoke access when authorization changes.
Attachments need revision identity. “Proposal-final-2.pdf” invites confusion. Include project, revision, release status, and date in the document itself, not only the filename. The message should identify which previous artifact it supersedes.
Make every message accessible and forwardable
Use real text for the essential message. Do not place the update only inside an image. Give links descriptive labels, preserve readable contrast, use headings when the email is long, and provide text alternatives for meaningful visuals. The W3C WCAG 2.2 reference supplies useful web-accessibility checks; the company’s email implementation still needs practical testing.
Write for the second reader. A customer may forward the message to a partner, facilities manager, accountant, engineer, lender, or adviser. Name the project, decision, source, revision, and open condition so the email survives outside the original conversation.
Avoid jargon in subject lines. “Updated DER scenario” may mean nothing to the customer. “Updated battery option after the load review” is identifiable. Keep urgency claims factual and readable.
Test mobile rendering, keyboard navigation where applicable, zoom, dark mode, and blocked images. The one required action should remain clear without decorative formatting.
What should a solar follow-up decision record contain?
A solar follow-up decision record should contain the customer decision, last commitment, current project and proposal revision, open question, evidence available, message purpose, permitted channel, consent or lawful-contact basis, data sensitivity, sender, next action, stop condition, and CRM update. The message must change the project state or make the next choice easier. The record lets another team member verify why the message was sent and what should happen next.
The record prevents follow-up from becoming a calendar habit. A message sent because “three days passed” may ignore a promised customer event, a pending design correction, a withdrawn consent, or a proposal revision that is no longer current. State comes before cadence.
| Decision field | Question before sending | Stop or reroute when |
|---|---|---|
| Customer decision | What choice is the customer still considering? | No active decision or reason to continue is known |
| Last commitment | Who promised what, and by when? | Sender would duplicate or contradict another owner |
| Project state | Which design, scenario, and proposal are current? | Attachment or link is stale |
| Message purpose | Correct, compare, answer, request, revise, or close | Message adds no new value or action |
| Evidence | Which source supports the statement? | Claim cannot be verified or appropriately qualified |
| Contact permission | Which channel and basis are approved for this recipient and jurisdiction? | Consent, preference, suppression, or legal question is unresolved |
| Data boundary | Which customer or project information may be included? | Message or forwarded content exposes unnecessary data |
| Stop condition | Which reply, event, or silence rule ends the sequence? | Sender keeps following up without a legitimate next state |
Contact, privacy, marketing, and recordkeeping requirements vary by jurisdiction and channel. Use approved company policy and qualified legal review. This article offers an operating record, not permission to contact a person or a universal cadence.
How should the project state choose the message?
Choose a solar follow-up message from the current project state: send a correction when evidence changed, a normalized comparison when options differ, a sourced answer when a question was resolved, a one-input request when progress needs evidence, a revision note when outputs changed, or a respectful close when no active next decision remains. Timing follows the customer’s actual decision path.
Start with the customer’s last decision, not the sender’s desired outcome. A comparison is useful only when scenarios are current and equivalent enough to compare. A document request is useful only when the recipient knows why the input matters, how it will be handled, and what happens after it arrives.
- Read the last customer commitment and current opportunity state.
- Confirm the project, design, model, and proposal revision.
- Select one purpose the evidence can support.
- Check channel, consent, preference, and data boundaries.
- Write the customer choice or requested input in ordinary language.
- Name the next owner and expected update.
- Record the message and stop trigger in the shared project.
Use this copy-ready message brief:
Customer decision:
Current project and proposal revision:
Last commitment:
Message type:
New evidence or value:
One customer action:
Permitted channel and contact basis:
Sensitive data excluded or protected:
Sender and next owner:
Stop or re-entry trigger:
CRM or project update:
Do not put several next steps into one “helpful” message. The customer should be able to answer, supply one input, choose an option, request clarification, defer, or close the loop. If multiple internal questions remain, resolve them before asking the customer to coordinate the company.
How does a state-driven sequence work in practice?
A state-driven solar follow-up sequence changes only when the customer decision, project evidence, or permitted next action changes. It avoids fixed-message automation after a reply, design revision, missing-evidence request, deferral, opt-out, or closure. Every send inherits the current proposal revision and contact boundary from the shared record. Configure automation to stop and request review when the customer or project state invalidates the scheduled message; test that behavior before enabling the sequence.
Illustrative example, not a campaign result: A customer receives two solar options and asks whether the projected production difference comes from system size or shading. The rep records the question and pauses the generic sequence while design reviews the current scenarios.
The next message is a sourced answer with a normalized option table, current identifiers, and the remaining limitation. It asks whether the customer wants to compare the ownership scenarios next. When the customer requests time until a facilities meeting, the rep records the event and stops automatic reminders.
After the meeting date, the permitted re-entry message refers to the customer’s event and current proposal. If the design changed in the meantime, the sender issues a revision note before any “checking in” message. If the customer opts out or closes the project, the sequence ends according to policy.
The record can prove that the workflow honored the state changes. It cannot prove the message caused a sale. Measure delivery, reply, correction, opt-out, and next-state events according to defined rules without converting every open or click into intent.
Use the proposal follow-up checklist for a broader sequence framework. This article owns the six value-adding message types and the decision logic that selects among them.
Match message content to the channel boundary
The approved contact basis does not make every project detail appropriate for every channel. Keep the message proportionate and route sensitive records through approved systems.
| Channel situation | Safe operating approach | Avoid |
|---|---|---|
| Short text or messaging app | Name the decision and link to an approved secure next step | Detailed bills, contracts, site files, or sensitive project data in the thread |
| Email to one stakeholder | Identify the project and current revision with necessary context | Assuming the recipient may forward every attachment safely |
| Multi-stakeholder thread | State roles, current decision, and source of truth | Exposing another person’s contact, pricing, finance, or private information unnecessarily |
| Portal notification | Explain what changed and where the customer can review it | Treating a notification as proof the content was read |
| Automated reminder | Recheck current state, permission, ownership, and stop rules before send | Continuing after reply, deferral, revision, closure, or opt-out |
Use the savings-language consistency guide when a follow-up repeats modeled production or financial value. The message should inherit the current approved assumption and limitation, not create a shorter, stronger promise because the channel feels informal.
Keep links durable and identifiable. The customer should see the destination purpose and current project state before opening it. Avoid URL shorteners or attachments that obscure which revision they contain unless company policy and security review approve them.
When a recipient forwards the message to a decision committee, the content should still make sense. Name the customer decision, evidence source, limitation, and next action without referring to an unexplained “it” or private conversation. Forwardability improves usefulness and reduces the chance that a detached number becomes the whole proposal story.
Test the sequence with replies out of order. A customer may answer an earlier message after a later revision. The receiving owner should reconcile the reply with the current project instead of letting automation reopen a stale state. Record the resolution and stop any scheduled message built on the old branch.
Keep the project record clean between messages
A valuable message still fails if the underlying contact and proposal records disagree. Before sending, confirm recipient identity, role, permission, project status, active proposal revision, last customer request, assigned owner, and suppression status. A stale customer-relationship record can send an excellent template to the wrong person at the wrong stage.
Record the communication as a project event. Keep purpose, channel, recipients, related artifact, claim-sensitive fields used, and next state. Do not paste sensitive documents or unnecessary personal detail into a general activity note. Link to the controlled record under the company’s access policy.
Separate facts from salesperson interpretation. “Customer asked for a cash option after reviewing financing” is a recorded event. “Customer is price shopping and unlikely to buy” is a judgment that may bias the next person. If an interpretation matters, label it and retain the customer statement that supports it.
Close duplicate tasks. Two team members following up on the same missing bill makes the company look inattentive and can expose data to unnecessary recipients. One named owner should control each customer request, with a visible backup when that person is unavailable.
Use expiration logic. A message draft containing a price, tariff, finance term, incentive, production run, or schedule claim should stop for review when the underlying field expires or the proposal changes. Automation must not treat merge success as factual validation.
Edit each template into a human message
Remove every bracket and generic adjective. Name the roof, meter, option, document, tariff, panel, tree, proposal section, or decision. One project fact does more work than three sentences about commitment to customer service.
Read the message aloud. If the first paragraph repeats the subject and the second merely says the issue is important, cut them. Put the update or request in the first two sentences. Keep the reason close to the action.
Use a calm tone when the company made an error. “We used the wrong billing period and corrected the scenario” is better than a long apology that hides the consequence. State what changed, whether anything else was affected, and what review followed.
Avoid false personalization. A merge field with the customer’s name does not make a bulk sequence relevant. Project context, a real answer, and a proportionate next step do. Never invent familiarity, a prior conversation, or a customer preference.
End once. A message does not need “What do you think?”, “Can we hop on a call?”, “Does Tuesday work?”, and “Should I close your file?” together. Choose the action that follows from the project state and let the customer answer it.
Create approved structures, not frozen scripts. Legal or compliance owners can set required sender, consent, disclosure, opt-out, privacy, and record elements. Product and technical owners can approve common boundaries. Sales still writes the project-specific fact and next action.
Review messages that contain prices, incentives, finance, production, savings, deadlines, equipment claims, warranties, or approvals. Automation should pull only current, governed fields and stop when an input expires or a proposal is superseded.
Measure task outcomes: requested document supplied, question resolved, corrected option reviewed, decision recorded, or project closed. Open and click metrics may be incomplete and do not prove understanding. Do not infer intent from one interaction.
Audit a sample of sent messages for unsupported claims, stale versions, missing consent status, broken links, copied recipients, and vague next actions. Feed the findings into templates and workflow rules.
Frequently Asked Questions
What should a solar proposal follow-up include?
Include the customer and project context, one decision-relevant update or question, the source or proposal revision affected, and one proportionate next action. Keep claims qualified and links identifiable. The message should still make sense if forwarded to another decision-maker, and it should respect the recipient’s communication preferences and applicable marketing rules.
How often should a solar salesperson follow up?
There is no universal interval that fits every project or jurisdiction. Agree on a next step during the meeting when possible, use the customer’s stated timeline, and let material project events control additional contact. Repeated messages without new value create pressure and noise. Respect opt-outs, consent limits, and company communication policy.
Should a follow-up repeat the projected solar savings?
Repeat a financial figure only when it is necessary for the decision and still matches the current design, load, tariff, price, finance, incentive, and model revision. Carry the scenario label and material assumptions with it. A follow-up should not strip qualifications or turn a modeled result into a guaranteed customer outcome.
Can a salesperson create urgency in a follow-up email?
Only state a deadline, price expiry, equipment constraint, financing term, or policy date when a current controlling source supports that exact claim and the condition applies to the offer. Link or identify the source. Do not invent scarcity, countdowns, or consequences merely to force a reply from a customer.
When should a salesperson stop following up?
Stop when the customer opts out, asks for no further contact, chooses another path, or reaches the limit set by applicable rules and company policy. A final close-the-loop note can state what will be archived and how the customer may restart later. Preserve required records without continuing unwanted promotional messages.
Keep proposal updates connected to project evidence
Request a guided SurgePV demo with a real proposal workflow. Current access, implementation scope, pricing, and contract terms require confirmation in a written quote.
Request a guided demoSources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.
