
NGO Partnership Delivery Formats: Five Scoped Contributions for Energy Vendors
Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Map normal solar enquiries from receipt to assessment with clear human responsibilities, relevant outputs, realistic scheduling and an agreed next decision.
A solar enquiry follow-up handoff map gives each normal enquiry event a responsible person and a useful response. A useful follow-up flow tells a prospective customer what happens next and gives a team member responsibility for the inquiry. It should reflect what the person asked for rather than automatically placing every contact in a long sales sequence.
Record the service requested, contact details, source, date and relevant permission evidence. Ask only for information needed at this stage. Do not require banking details or extensive property documents simply to request a conversation.
Before sending commercial electronic messages, check the applicable consent basis. CRTC guidance explains consent, identification and unsubscribe requirements. A quote inquiry and an ongoing promotional subscription should not be treated as identical permissions.
Send an appropriate acknowledgement that confirms receipt and a realistic response expectation. Assign a named owner and a task to review the inquiry. A booking link can be useful if the service and appointment type are clear.
For example, a sample acknowledgement might say: “We received your request about rooftop solar. Our team will review the information and contact you about the next step.” It should not declare the roof suitable or promise a rebate.
When a consultation is booked, update the record and stop invitations that no longer apply. Send relevant appointment information and provide a rescheduling route. If a person replies, route the message to a human rather than leaving the automation to continue unchecked.
Use a limited, appropriate follow-up for an unanswered request and define when it ends. Do not keep escalating urgency or imply that an unverified program deadline requires immediate action.
Track time to a human response, completed consultations, unresolved replies and unwanted duplicate messages. Compare similar inquiry sources and periods before claiming improvement.
Keep personalized rebate discovery and address matching within Solenery premium access. General follow-up messages can explain the assessment process without delivering invented eligibility results.
| Trigger | Human responsibility | Output before the next step |
|---|---|---|
| New request received. | Intake owner checks the request and relevant contact basis. | Reference, acknowledgement and assigned reviewer. |
| Initial fit reviewed. | Coordinator clarifies the service, location and next task. | Missing-information request or an appropriate assessment route. |
| Assessment appointment accepted. | Scheduling owner confirms actual availability and preparation. | Current appointment, relevant instructions and contact route. |
| Assessment information reviewed. | Responsible technical person identifies scope and remaining questions. | Documented basis for a proposal or further review. |
| Next decision agreed. | Opportunity owner records the buyer’s requested action. | Current task, owner and agreed update or closure. |
This is an operational map to adapt, not a legal sequence or fixed message schedule. Acknowledgement, service coordination and promotion need review for their actual purpose; one enquiry does not justify every possible later campaign.
In a fictional request, an owner asks what a rooftop-solar assessment involves. The acknowledgement identifies the process, and a coordinator asks for the specific preparation information needed. The next appointment is offered only when the intended service and real availability are clear.
The request should not automatically generate an eligibility result or a system size. Those require their own property review and relevant evidence. Keep the customer’s actual question visible as the enquiry moves between the office and technical team.
Have a staff member follow a sample normal request from entry to the next agreed decision. Can they identify the owner, current record and output at each step? Fix a missing responsibility before adding more messages.
Keep exceptional cases in a separate test matrix so normal-path instructions remain readable. Their handling still needs to be demonstrated before launch and reviewed as the connected tools change.

Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Reconcile partner referrals with an event-to-payment ledger for source history, duplicate...

Use co-marketing templates for clean energy partners to document the brief, landing-page...