Routing Solar Appointments Across Multiple Teams

Start with a clear purpose

A growing solar business may have several advisers, service areas or specialist teams. Clear routing helps customers reach the appropriate conversation and prevents the diary from being filled with appointments that someone else must handle.

Map who handles what

Write down which people or teams handle new installations, storage, commercial projects and support. Include any differences in geography or availability that affect booking.

A commercial project may belong with a specific adviser even when the property sits inside an area normally managed by a domestic team.

Responsibility maps should use the work the teams actually perform. Include service categories, location coverage and any specialist review route. A team may handle domestic installations in one area and support enquiries across another, so one broad territory field may be insufficient. Ask staff where informal forwarding currently happens and why. Those repeated transfers reveal decisions that need to be written into the routing process. Keep the map understandable enough for an office colleague to use without relying on a particular adviser’s memory or availability.

Choose reliable routing questions

Use questions customers can answer accurately, such as postcode and enquiry type. Avoid requiring them to choose an internal department or technical category they do not understand.

Ask whether the enquiry concerns a home or business property rather than presenting unexplained internal team names in the booking journey.

Customer-facing questions should translate the internal map into ordinary language. Postcode and a description of the enquiry often give a better starting point than a list of team names. If a customer is unsure whether their request fits a category, preserve the explanation and route for review. Avoid requiring them to diagnose the service they need before they can ask about it. The aim is a suitable next conversation, not a perfect classification supplied by a person who may be exploring solar for the first time.

Define exceptions and overlaps

Agree what happens when more than one team could handle an enquiry or none clearly fits. Give a person ownership of deciding the route where the standard rules are insufficient.

A customer with both domestic and business sites may need a coordinated conversation instead of receiving separate, conflicting appointment invitations.

Overlaps need an explicit decision rule or reviewer. Two teams may cover the same area but handle different kinds of project, or the customer may have several related sites. Agree whether one person coordinates the enquiry and how specialist input is arranged. Do not solve ambiguity by sending several invitations and asking the customer to work out which one to attend. A clear owner can select the useful first meeting and ensure other teams receive the relevant context without making the experience feel fragmented.

Keep calendars understandable

Make the appointment type and assigned team visible in the confirmation and handover. Check that a later change does not lose the original routing context.

If a specialist rearranges a call, the new appointment should retain the note explaining why the enquiry was routed to that specialist.

A calendar entry should show enough information to explain the assignment. Include the appointment type and relevant enquiry summary, not just the customer’s name. If a booking moves between advisers, confirm the new arrangement and retain the reason for specialist routing. Check that the customer-facing confirmation does not name a person or location that is no longer correct. Diary changes are part of the routing process; they should not silently remove the context that made the original assignment appropriate. Test a transferred appointment as well as a new one.

Review misplaced bookings

Ask teams to flag appointments that should have gone elsewhere and identify the question or rule behind the error. Correct the process rather than relying on informal forwarding forever.

Repeated storage enquiries in the new-installation diary may point to unclear enquiry categories, not simply to an adviser choosing the wrong slot.

Misrouted bookings are useful diagnostic examples. Ask the receiving team why the meeting belonged elsewhere and trace that back to the questions and rules used. The cause may be a confusing category, an unrecorded change in service scope or an exception the standard flow cannot decide. Correct the relevant part rather than adding a catch-all instruction to forward mistakes manually. Some review will remain necessary, but repeated identical transfers indicate that the normal route needs improvement. Keep the feedback focused on the rule, not on blaming the customer for selecting a label.

Apply the approach to real enquiries

Test a straightforward domestic enquiry, a battery addition, a business site and a request involving more than one property. For each, write the expected owner and appointment purpose before running the conversation. Compare the result with that expectation and inspect the calendar description. If team members disagree about the expected owner, resolve the underlying responsibility before changing the automated flow. A system cannot consistently apply a rule the business has not agreed.

Include a test where the assigned person has no availability. The fallback should preserve expertise and context rather than simply choose an unrelated free diary. A review or an honest explanation of the next step may be more appropriate than an immediate slot. The customer should understand what is available and whether the booking is confirmed or awaiting coordination.

Galaxy SaaS Agency supports agreed qualification, team routing, follow-up, calendar booking and reminders, with supported CRM handover. The setup should confirm the teams, service areas and exceptions that matter to the actual business. Review correct assignment alongside suitable bookings and attendance. The purpose is a connected route into the right conversation, not a claim that every enquiry can be allocated without judgement or that calendar automation creates extra specialist capacity.

Keep the responsibility map current when staff roles or service areas change. Identify the approver and retest the affected enquiry types. A routing system can continue operating smoothly while using an outdated team boundary, so operational accuracy needs review as well as technical function.

A transferred appointment should have one clear owner. Identify who tells the customer about the change and who verifies the updated diary. Without that responsibility, two teams can each assume the other has confirmed the arrangement, leaving the person who booked with no reliable explanation of what happens next.