A Practical Launch Checklist for Solar Appointment Setting

Start with a clear purpose

A reliable booking journey is built around the installation business’s real process. Before launch, test what happens to common enquiries and awkward exceptions so the team can recognise and manage the handovers.

Document the real journey

Map the enquiry sources, existing response steps and appointment types. Identify where the customer currently waits, repeats information or receives an unclear next step.

Follow one example from a website form through to an adviser’s diary, checking each handover rather than assuming the form submission itself creates a usable appointment.

The map should describe what happens now, including workarounds. If an office colleague copies enquiries into a spreadsheet or advisers use separate calendars, record that rather than drawing a connection that does not exist. Ask the people doing the work where they lose context and which questions customers repeat. Include the customer-facing confirmation in the map. A process may appear complete internally while leaving the homeowner unsure whether an appointment is booked. Discovery is useful when it exposes those gaps and creates a shared description of the journey the team intends to support.

Approve the qualification rules

Agree the service area, enquiry categories and minimum information needed for each appointment. Review the wording with the people who will conduct the calls or assessments.

The technical team may prefer certain existing-system questions to be asked later; record that decision instead of adding them automatically to the first-contact flow.

Approval means more than agreeing a list of fields. Ask the team to review how questions are worded and what each answer changes. Define acceptable unknowns, the minimum brief for each appointment and the reasons an enquiry needs review. Service-area boundaries should use the business’s actual rules. A customer’s preferred timing should remain a preference until the responsible team confirms it. Put those decisions in one usable reference so later corrections do not depend on remembering a conversation from setup. A small, clear rule set is easier to test than a sprawling questionnaire.

Test calendar behaviour

Check available slots, team assignment, confirmation and changes using realistic appointments. Include situations where there is no suitable availability or the customer asks to rearrange.

A cancelled test booking should stop generating reminders and free or otherwise update the diary according to the business’s agreed process.

Test the calendars using the same paths customers will use. Check team selection, available times, the message after choosing a slot and the internal record. Then rearrange and cancel the test appointment. Make sure the old arrangement no longer produces contradictory reminders and that useful context remains with the new booking. Include a case with no appropriate availability. The process should provide a clear next action and owner rather than offer an unsuitable slot or suggest that a request has been confirmed when it is still pending.

Rehearse difficult conversations

Use examples involving uncertain technical questions, complaints and out-of-area properties. Confirm that the system pauses or routes appropriately rather than inventing a reassuring answer.

A test customer who asks for a guaranteed saving should receive approved wording and a route to the right discussion, without an unsupported figure.

Difficult tests reveal the boundaries of the flow. Ask about a specific equipment compatibility issue, a concern about an existing installation and a property outside the normal area. Review whether the response stays within approved wording and whether the receiving person gets a useful brief. Do not judge success simply by whether every test customer reaches a calendar. Correctly routing a support concern is a better outcome than booking it as a new installation call. Keep a record of the expected action for each test so revisions can be checked consistently.

Assign the first review

Decide who will review conversations, calendar records and team feedback after launch. Make it easy to flag an issue and identify the person authorised to approve a correction.

A short, scheduled review of misrouted enquiries is more useful than waiting for a busy adviser to remember every problem at the end of a month.

An initial review needs an owner, a practical schedule and access to the information being discussed. Decide who reads flagged conversations, who checks booking quality and who can approve changes to wording or routing. Make corrections visible to the people conducting appointments. Otherwise, an adviser may continue explaining an old process after the customer-facing journey has changed. Keep the first review focused on a manageable set of questions: did enquiries reach the right next step, did the calendar behave as expected and did staff receive useful context?

Apply the approach to real enquiries

A launch rehearsal should include people who did not build the flow. Give one person a realistic customer brief and another the resulting internal appointment record. Ask each to explain what happens next. A disagreement about whether a call or visit was booked is a wording problem to resolve before launch. Likewise, a technically successful CRM connection needs more work if the adviser cannot see the customer’s main question. The outcome of testing is a shared understanding, not merely a completed technical checklist.

Retest after substantive changes. A revised enquiry category can affect team routing, calendar availability and the confirmation text. Checking the new question alone may miss a contradiction further along the journey. Keep the test set small enough to repeat but broad enough to cover routine bookings, missing information and personal review. This makes it possible to maintain the process when services or team responsibilities change.

Galaxy SaaS Agency helps configure response, qualification, follow-up, appointment routing and reminders around an agreed business process. Discovery should confirm the supported connections, approved wording and escalation contacts. A considered launch gives the solar team a clear working system rather than an unexplained stream of bookings. Continue reviewing suitable appointments and attendance after launch, while keeping technical outcomes and sales separate from what the intake stage can establish.

Do not wait for a major failure to collect feedback. Give staff a simple route to flag a confusing question or misrouted enquiry as it happens. A specific example is easier to fix than a general impression that the system is not working. Record the agreed correction and check that it reaches the live conversation, calendar and handover together.