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

Test solar follow-up exceptions with expected behaviour, observed evidence and retest records for duplicates, replies, opt-outs, bookings and failed transfers.
A solar follow-up exception test matrix helps the team prove how duplicate requests, replies, opt-outs and booking changes behave before launch. An automated follow-up should stop or change when a customer's situation changes. Before expanding a solar inquiry sequence, test the exceptions that can create confusing or unwanted messages.
Identify whether a person is a new inquiry, booked consultation, active quotation, customer, deferred prospect or closed inquiry. Give each state a clear owner and exit rule. Do not assume that everyone who downloads information wants a sales appointment.
For commercial electronic messages, verify the applicable consent basis and preserve evidence. CRTC guidance explains the distinction between express and implied consent and the need to respect unsubscribe requests. A CRM tag alone is not proof of permission.
These are test cases, not a prescribed email schedule. Decide what messages are appropriate for your service and circumstances.
Use safe defaults when names or locations are missing. Do not insert a rebate eligibility claim based only on a postal code. Personal property matching remains within Solenery premium access, and any incentive statement needs current verification.
Assign someone to monitor failed integrations, bounced messages and replies. Measure duplicate sends, missed handoffs and completed appointments using actual records. Automation supports follow-through only when exceptions reach a person who can resolve them.
| Test setup | Expected behaviour to define | Evidence to inspect |
|---|---|---|
| Same test contact submits twice. | One coherent owner and communication path, preserving both entry events. | Linked records, assignment and queued messages. |
| Reply arrives before a queued reminder. | Human receives the reply and irrelevant automation stops. | Inbox routing, queue state and response task. |
| Opt-out is recorded in one connected tool. | Relevant marketing suppression reaches all intended systems. | Preference history and attempted-send outcome. |
| Appointment is rescheduled or cancelled. | Old reminders no longer describe an active booking. | Calendar, confirmation and reminder versions. |
| Transfer fails while the owner is absent. | An alert reaches accountable cover without silent duplication. | Error, retry and reconciliation records. |
Use fictional contacts and controlled test destinations. Set the expected behaviour first, then mark pass, fail or not tested from observation. A vendor assurance alone is not a passed test.
For a fictional test, queue a booking invitation, then record a booking before the send time. Inspect whether the queued invitation is cancelled or re-evaluated. Next, change the booking and inspect the replacement reminders. The actual implementation may need a different safeguard at each boundary.
When a test fails, record the affected systems, correction owner and retest evidence. Do not erase the failure by changing the expected result after observing it.
Retain the test date, workflow version and configuration with the release decision. Repeat affected tests when an integration or rule changes; the record should show which exception paths were actually covered.

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...