Skip to content
Back to Business Operations
Business Operations

Solar Follow-Up Exception Test Matrix: Duplicates, Replies and Booking Changes

Test solar follow-up exceptions with expected behaviour, observed evidence and retest records for duplicates, replies, opt-outs, bookings and failed transfers.

Arshia Jahangiri
3 min

Table of contents

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.

Map the states first

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.

Run these scenarios with test contacts

  • A person books after a reminder has already been queued: the booking invitation should not continue as though nothing happened.
  • The same person submits two forms: prevent duplicate sequences and conflicting owners.
  • A consultation is cancelled or rescheduled: update all connected reminders and calendar records.
  • A prospect replies with a technical question: pause generic nudges and assign a person to respond.
  • A person opts out: suppress further marketing across connected tools and retain the necessary suppression record.
  • A supplier or utility delay changes the timeline: require a human review before sending a promised installation date.

These are test cases, not a prescribed email schedule. Decide what messages are appropriate for your service and circumstances.

Review content and failure alerts

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.

Record the expected result and observed evidence

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.

Handle the timing race deliberately

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.

Share this article