Silent Solar Prospects: 7 Follow-Up Sequences

Last updated: November 2026.

SurgePV publishes this post and sells solar design software.

The proposal went out Friday afternoon. On Monday, the salesperson sees a document-view event and an empty inbox. That blank space is surprisingly easy to fill with a story: price objection, competing installer, distracted buyer, hesitant spouse, bad timing. None of those explanations came from the prospect.

Silence is an unknown state. A useful follow-up sequence begins with the last thing the prospect actually said, the proposal revision they received, the unresolved decision, and the communication direction on record. The sequence should reduce one decision cost or close the loop. It should never manufacture urgency merely because the pipeline feels uncomfortable.

Use this guide to choose and close a workflow after unexplained post-proposal silence. For wording, use the six value-adding follow-up messages. For a planning window, use the 14-day proposal-review checklist. If the buyer has explicitly asked to wait, follow the delayed homeowner decision workflow instead of enrolling them in a chase.

The seven sequences below are operating patterns, not universal contact rules. Timing, channel, consent, suppression, privacy, and marketing requirements depend on the recipient, message, jurisdiction, company policy, and prior direction. Qualified reviewers must approve the actual communication program.

What should happen before a silent prospect enters a sequence?

Before enrolling a silent prospect, verify the customer and project identity, correct proposal revision, delivery state, last customer statement, unresolved decision, promised action, permitted channel and purpose, open technical or commercial changes, sequence owner, and exit condition. Do not infer an objection from silence or use an engagement event as permission for more contact.

Start with the released artifact. Confirm the proposal link or attachment still points to the intended project, design, equipment, scope, price, finance scenario, assumptions, and review state. A later design revision or corrected utility record can make an earlier follow-up message factually stale even when its wording has not changed.

NASA describes configuration management through identification, change control, status reporting, and verification. A sales sequence is not a NASA program. The useful analogy is version traceability: a message about production, price, equipment, or a customer choice should still point to the current project state.

Next, reconstruct the final conversation without adding motive. “Customer asked for the roof-only option and said a co-owner would review it” is an observed state. “Customer is price shopping” is an interpretation unless the customer said so. Keep a faithful note beside any reporting code so another representative can see the difference.

DOE says in its homeowner solar guide that there is no universal solar solution and discusses site, energy use, provider, cost, financing, utility, and decision context. That broad decision frame is why a generic “checking in” message usually carries too little project information to help.

If the company owes the customer a correction, answer, or revised option, complete that work before starting a persuasion sequence. Label the output and explain what changed. A missing internal deliverable is not customer silence.

Which seven solar proposal follow-up sequences fit verified states?

Seven useful sequences fit seven verified states: uncertain delivery, an unanswered project question, a corrected proposal, a missing decision participant, a requested option comparison, customer-controlled timing, and respectful closure. Choose only the state supported by the record. Each sequence needs a permitted purpose, current evidence, one response path, and an explicit exit or handoff.

1. The delivery and decision-map sequence

Use this sequence when the team can prove the proposal was released but cannot confirm that the intended person received the correct revision or knows what decision comes next. Do not cite tracking activity as evidence of comprehension.

The opening message names the project and revision, offers a stable link or attachment, and states the proposal’s intended decision in one sentence. Give the recipient a low-burden correction path: wrong person, wrong version, cannot access, received and reviewing, or prefers another channel under approved policy.

If delivery is confirmed, a second message may identify the one decision that remained open during the meeting. Avoid listing every proposal feature. The sequence exits when delivery and ownership are confirmed, another recipient is authorized, a technical access issue is handed off, or the approved closure condition is reached.

This sequence solves document access and decision orientation. It does not presume buying interest. Keep event interpretation and measurement in a separate tracking record, with the event source and its limitations.

2. The named-question sequence

Use this when the prospect asked a specific question and the company now has a source-bound answer. Common subjects include roof use, equipment, modeled production, scope, service, finance documentation, agreement language, or the person responsible for a later review.

The first message restates the question faithfully and provides the current answer, source, assumption, proposal revision, and limit. Ask whether the answer resolves that question or exposes another named gap. The prospect should be able to reply with a fact, correction, or decision rather than reconstruct the whole proposal.

If qualified review remains open, say so. Do not soften “pending technical review” into “looks good” merely to keep the conversation moving. The sequence exits when the question is answered, the prospect corrects the record, a specialist takes ownership, or the prospect declines further discussion.

Digital.gov’s plain-language guidance describes clear content that helps the intended audience understand information and use it. Clear wording cannot prove understanding, but it can make the response path visible and reduce unnecessary interpretation.

3. The corrected-proposal sequence

Use this after a bill, tariff, roof fact, layout, equipment choice, scope line, price, finance document, savings input, or proposal statement has been corrected. The correction itself is the reason for contact, so it must be complete before the message is released.

The first message names the old item, the new source, the current revision, and which customer-facing outputs changed. It also says what stayed the same when that distinction matters. Never turn a correction into unsupported good news. A lower or higher modeled value is still an estimate tied to stated inputs.

A later message asks whether the revised record now matches the customer’s information and whether the original decision remains current. The sequence exits on confirmation, a new correction, a required specialist review, withdrawal, or archive. Preserve the superseded artifact so reviewers can reconstruct the change.

FTC advertising guidance for small businesses says advertising must be truthful and non-deceptive and advertisers need evidence for objective claims. That United States guidance does not decide a private message’s legal status. It supports the operating rule that a correction should not leave an earlier unsupported impression in the follow-up.

4. The decision-participant sequence

Use this when the prospect identified another legitimate participant, such as a co-owner, facilities lead, finance reviewer, procurement contact, property manager, adviser, or other decision owner. Confirm permission before adding anyone or sharing project information.

The first message offers a short, current decision record that states the project option, unresolved choice, principal assumptions, material differences, and questions for the participant. It should work when forwarded without revealing unrelated personal or commercial data. The prospect may prefer to forward it personally rather than authorize direct contact.

If a shared conversation is requested, ask what each participant needs to decide and which documents they should receive. The sequence exits when the authorized handoff is completed, a joint discussion occurs, the decision returns to the original owner, or no further contact is requested. Record transmission or access status separately from the participant’s actual acknowledgment; a delivery event does not prove that they reviewed the case.

Do not label another participant as an objection. Their role, authority, questions, and preferred process are project facts. The salesperson’s forecast interpretation belongs in a separate field.

5. The requested-option sequence

Use this when the prospect asked to compare named options and the company can present them on a controlled basis. Examples may include roof areas, equipment families, storage scope, cash and financing structures, or another documented choice. Do not create an option simply to trigger a reply.

The first message names the common project basis and shows only the fields needed for the requested decision. Separate design, energy, price, finance, customer responsibilities, assumptions, and review state. Unknown fields stay unknown. If options use different project bases, say that comparison is not ready.

The next message asks which tradeoff the prospect wants clarified, not which option they want to buy immediately. Route technical, financing, tax, contract, or utility questions to qualified owners. The sequence exits on a selected next review, an evidence hold, a request for another authorized option, explicit delay, or closure.

The CFPB’s August 2024 solar-financing issue spotlight discusses risks involving markups, fees, tax-credit assumptions, and confusing terms in solar-specific loans. It does not evaluate a current offer. Financing messages should use current provider documents and qualified review rather than a salesperson’s reconstruction.

6. The timing and permission sequence

Use this when the prospect previously named a date, project event, decision window, or contact preference, but then stopped replying. The trigger must come from the prospect or an approved policy, not from a rep’s desired forecast date.

The first message refers to the agreed trigger and asks whether it still controls. A roof project may have moved. Another decision participant may need more time. A financing offer may have changed. The prospect may prefer no current action. Offer a small set of accurate states and an easy way to change communication direction.

If the trigger is no longer valid, ask whether to record another customer-selected event or close current follow-up. Never promise that the proposal, price, equipment, finance terms, incentive assumption, or modeled result remains current without revalidation. The sequence exits on a new agreed trigger, a requested deliverable, closure, opt-out, or suppression.

An explicit delayed decision belongs in the separate delayed-decision workflow, not in an automated chase. This guide covers silence only when an earlier permitted trigger still exists.

7. The respectful close-the-loop sequence

Use this when earlier value-bearing contact did not produce a reply and no unresolved company obligation remains. The purpose is to end current activity accurately, not to create a dramatic “last chance.”

The message states that the active sequence will close, identifies the project and proposal status, and explains how the prospect may restart if appropriate. It does not invent scarcity, imply approval, threaten lost savings, or announce that the person’s file will be destroyed unless a verified retention policy says so.

Internally, archive active tasks, update the opportunity state, apply required suppression or channel changes, identify stale proposal links, and preserve the minimum approved record. The sequence exits when the archive and communication controls are confirmed. A later inbound message or agreed event may reopen the opportunity through a fresh project and permission check.

Closure is useful data. It stops silent opportunities from consuming forecasts and prevents another system or representative from reviving generic outreach without context.

How should a sales rep choose one follow-up sequence?

Choose a follow-up sequence from the last verified customer state and the smallest unresolved decision. Confirm that the company has completed its promised work, the proposal remains current for the stated purpose, and contact is permitted. Run one sequence at a time. If evidence, permission, or authority is missing, hold outreach and assign the responsible owner.

Do not stack the corrected-proposal, option, and timing sequences because several labels appear plausible. Sequence selection is a decision about the next useful job. A corrected option comparison may resolve all three conditions in one controlled message, but its record should still state which job governs.

Sources: the FTC CAN-SPAM guide and NIST Privacy Framework linked below, checked November 2026. These facts concern U.S. email guidance and voluntary privacy-risk management; the seven sequence choices are editorial workflow suggestions, not legal permission to contact someone.

Use this seven-step control before enrollment:

1. Reconstruct the last verified state. Read the meeting note, customer message, promised action, proposal release, and permission record. Separate customer words from the rep’s interpretation.

2. Check company-owned work. Finish any promised answer, correction, review, or option before contacting the prospect. A pending internal task is not a follow-up trigger.

3. Revalidate the proposal basis. Confirm design, scope, price, finance document, model, assumption, and claim states needed for the next message. Restrict anything stale or unresolved.

4. Confirm contact controls. Check recipient, purpose, channel, sender, timing basis, suppression state, and applicable approved policy. Send nothing when authority is unclear.

5. Select one sequence and owner. State the observed trigger, current job, message progression, responsible owner, reviewer, and exit. Keep other possible sequences inactive.

6. Review the customer-facing claim. Verify the source, revision, qualification, implied meaning, and link. Remove pressure, unsupported scarcity, prediction, and interpretation of engagement data.

7. Record the disposition. Capture reply, correction, handoff, hold, new trigger, opt-out, archive, or reopening rule. Update every connected task or system that could keep contacting the prospect.

What should the follow-up sequence record contain?

A follow-up sequence record should contain the prospect and project identifiers, current proposal revision, last verified customer statement, open decision, company-owned deliverables, permitted purpose and channel, selected sequence, source-bound message claim, owner, reviewer, next event, exit condition, suppression action, archive state, and valid reopening trigger. Another representative should understand the record without guessing motive.

Use a copy-ready record before the first message. Replace every bracketed planning field with approved information in the responsible system. Do not paste personal, financial, or project data into an uncontrolled document.

Post-proposal silence sequence record

Prospect, authorized recipients, and controlled project ID: [record]

Current proposal link or file, revision, release state, and owner: [record]

Last verified customer statement and observation date: [faithful note]

Rep interpretation or reporting code, kept separate: [optional controlled field]

Open decision or promised company action: [one bounded job]

Material changes since release: [design, equipment, scope, model, price, finance, claim, or none confirmed]

Contact purpose, channel, sender, permission basis, and limits: [approved record]

Selected sequence and observed trigger: [one of seven]

Message one purpose, source, proposal revision, and response path: [record]

Later message condition, if any: [event, not automatic assumption]

Technical, finance, contract, tax, legal, privacy, or compliance reviewer: [owner or not applicable with reason]

Exit condition: [reply, correction, handoff, hold, trigger, opt-out, archive]

Suppression and downstream systems to update: [CRM, email, text, dialer, tasks, marketing, partner]

Archive status and valid reopening trigger: [record]

NIST describes its Privacy Framework as a voluntary tool intended to help organizations identify and manage privacy risk. Using that framework does not prove consent or legal compliance. Apply approved controls to access, collection, sharing, retention, deletion, and suppression for the actual system and jurisdiction.

The record should keep opportunity status and communication direction separate. “Proposal under finance review” describes a commercial state. “Email allowed for the requested document only” describes a contact boundary. Combining them into “active follow-up” invites another system to send the wrong message.

Illustrative workflow, not a customer case

An illustrative prospect receives a roof-only proposal after asking whether a second household decision-maker can review it. The representative sends the authorized participant record. No reply follows, and a tracking system later records a proposal view.

The team does not interpret the view as buying intent. The last verified state is another decision participant, so the representative selects the decision-participant sequence. Before contact, the proposal owner confirms that the current link still points to the reviewed roof-only revision and that no price, equipment, or model change has occurred.

The message offers a concise decision record and asks whether the original recipient prefers to forward it or authorize a shared conversation. The sequence exits when the authorized handoff is completed, permission changes, another question appears, or the closure condition is reached. A delivery event alone does not show that the participant reviewed the record. This example contains no real prospect, schedule, conversion result, proposal value, financing term, or performance claim.

When must solar proposal follow-up stop or move to another owner?

Solar proposal follow-up must stop when the recipient opts out, requests no contact, the approved permission or sequence basis ends, or the closure state is reached. It must move to another owner when the next decision requires technical, finance, tax, contract, legal, privacy, utility, warranty, or compliance authority the sales representative does not hold.

For United States commercial email, the FTC’s CAN-SPAM compliance guide describes requirements involving sender and routing information, subject lines, advertising identification, location information, opt-out handling, and responsibility when another company sends email on a business’s behalf. That guide does not determine whether a specific message is commercial, permitted, or compliant.

The FTC guide covers commercial email beyond bulk sends, including business-to-business messages. It distinguishes commercial content from narrowly defined transactional or relationship content by the message’s primary purpose. A requested proposal or correction is not automatically exempt. Qualified policy owners should classify the actual message, including any promotional material, before applying the relevant controls.

Multi-jurisdiction teams need local review. Do not copy one market’s email, text, calling, consent, retention, or suppression rule into another market. The operating record should name the jurisdiction, responsible policy owner, rule version, and system control without turning this article into legal advice.

The FTC’s solar consumer guidance tells shoppers to examine fit, ownership or lease terms, costs, savings representations, contracts, company information, and sales pressure. Do not respond to silence with unsupported countdowns, guaranteed savings, “nothing has changed,” or a claim that immediate signature protects an unverified benefit.

Sales should hand off a production question to the design or energy-modeling owner, a financing question to the qualified finance or lender route, agreement interpretation to contract or legal review, eligibility and tax questions to qualified advisers, and contact-rule questions to compliance. The sales representative can coordinate the record without pretending to become each authority.

SurgePV’s solar design workflow supports 3D roof modeling, solar array layout, shading analysis, energy-yield and financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Use those outputs to prepare the customer-facing proposal, then check that its stated scenario matches the reviewed project inputs.

No verified product claim says SurgePV is a CRM, email, text, telephony, consent, suppression, sequence-delivery, engagement-tracking, or sales-management platform. SurgePV cannot infer why a prospect is silent, authorize contact, apply a jurisdiction’s rule, or guarantee a response. Teams need responsible communication systems and qualified reviewers for those jobs.

Keep the workflow record separate from the message draft. A well-written email does not show why contact is permitted, which project version supports it, who owns an unresolved answer or what stops future tasks. Store those operational decisions with the opportunity, then draft only the communication they authorize.

Frequently Asked Questions

How many times should a solar rep follow up after a proposal?

No universal message count fits every prospect, channel, permission state, project, or jurisdiction. Use the company’s approved communication policy and the customer’s stated preferences, with a permitted purpose, current proposal and exit condition for each contact. Stop when the customer opts out, requests no contact, or the approved sequence reaches its closure state.

What should the first follow-up after a solar proposal say?

Match the first follow-up to the documented state. If receipt is uncertain, confirm access to the correct revision; if a question or correction is already owed, provide that reviewed answer first. Name the project, revision, one open item and response path without treating delivery, opens or views as understanding or acceptance.

Should a solar rep mention proposal-view activity?

Treat proposal-view activity as a system event, not buyer intent. The event alone may not identify the reader or show whether they understood the document. Use the event for internal troubleshooting if appropriate, but do not tell the prospect what they think, infer readiness, or create urgency from an open, click, or view alone.

When should a silent solar opportunity be archived?

Archive the active sequence when its approved exit condition is met and no permitted next action remains. Record the last verified decision state, proposal revision, open conditions, communication direction, suppression updates, and valid reopening trigger. Archiving ends the current outreach and forecast activity without assigning a motive to the person.

Can SurgePV send and manage these follow-up sequences?

No verified product claim says SurgePV is a CRM, email, text, telephony, consent, suppression, sequence-delivery, or engagement-tracking system. SurgePV supports solar design, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Teams must manage outreach permission, message delivery, sales stages, and suppression in their responsible systems.

A clean archive is part of a useful sequence

The quality of a follow-up sequence is visible at its end. A strong record tells the next representative why contact began, which project state supported it, what the prospect did or did not say, and why the sequence stopped. It does not leave a forever-open task with the instruction “try again.”

Archive current activity without writing a story about the person. Preserve the last verified state, retire stale material, apply approved communication controls, and name the only event that can reopen work. If the prospect returns, begin with what changed rather than pretending the old proposal and permission record remained frozen.

Silence does not need a cleverer nudge. It needs a smaller claim, a clearer decision job, and an exit the operating system will actually honor.

Bring a proposal that needs a clearer explanation to a guided proposal demo. Assess the design outputs there, and keep message delivery and contact controls in your outreach system.