A customer calls for an update. Your administrator opens the CRM, searches two inboxes and asks the installer what happened yesterday. The answer may exist, but nobody has turned it into a clear message for the customer.
A communication workflow should make the next useful update easier to send. The goal is to explain the verified position, identify any customer action and set a realistic expectation for the next contact. Sending more messages does not help if they repeat a vague status or contradict the job record.
The following approach is a suggested internal workflow for a solar business. Adapt the wording to the actual project, distributor and applicable program requirements. A Philippines-based solar administrator can own the communication queue while your responsible staff supply technical decisions and resolve exceptions.
Build the message from evidence, not a colour in the CRM
Start by defining what each customer-facing milestone means. “Submitted”, “under assessment”, “offer received” and “accepted” describe different events. Avoid converting all of them into “approved” because a CRM field turned green.
Energex's connection journey illustrates why the distinction matters. Its process separates an application, connection offer and acceptance, although eligible expedited basic applications can establish the contract during submission. Installation must wait until the connection offer is accepted and the contract exists. Use the actual applicable confirmation when preparing an update. Energex: connection process.
Keep a link to the evidence behind the message and the time it was checked. If the current record is unclear, ask the application owner to clarify it before telling the customer the next stage is ready.
A simple message register can help:
| Internal event | Verify before writing | Customer needs to understand |
|---|---|---|
| Application submitted | Submission reference and correct project | What was submitted and what happens next |
| Further information requested | The actual question and who must answer it | Whether they need to provide anything |
| Offer or decision received | Current document and responsible person's review | The specific next action, including acceptance where applicable |
| Installation booking proposed | Scheduling authority and unresolved conditions | Whether the date is proposed or confirmed |
| Installation activity completed | Installer's record and outstanding steps | What is complete and what still needs attention |
| Handover information supplied | Correct documents and delivery record | Where to find instructions and obtain help |
These are internal communication triggers, not official portal labels or a universal installation checklist.
Give each update four jobs to do
A useful update answers four questions: what has happened, what remains outstanding, whether the customer needs to act, and when the team will contact them again.
For a hypothetical submitted application, an administrator might write:
“Your connection application has been submitted under reference EXAMPLE-104. We are waiting for the network's response. You do not need to send us anything further at this stage. I will update you on Thursday, or earlier if a response requires action.”
Use that structure only when those facts are true. Replace the example reference and day with verified information. Do not leave template instructions or fictional values in a live message.
For a request needing customer input, specify the item and approved return channel. Explain which step is waiting for it. “Please send the information we discussed” forces the customer to reconstruct the request; “Please confirm the best daytime contact number using our agreed channel” gives them an answerable task.
Keep the message short enough that its action is easy to find. Detailed technical questions belong with the responsible person, who can provide wording the administrator is authorised to relay.
Promise the next contact you control
A follow-up date is a commitment to communicate. It is not a promise that an external assessment, metering job or approval will be complete by then.
Energex says its connection updates normally go to the person who submitted the application. When that person applied for the customer, they remain the main contact even if the customer receives copies of network emails. Give that contact a clear route for turning correspondence into an explanation. Energex: application updates.
If the promised update date arrives without a decision, send a factual holding message. For example: “We have not received the response yet. We followed up today, and our next update to you is due Monday.” Use the sentence about following up only after the action has happened.
Agree a sensible contact rhythm with the customer and your team. Some situations need a phone call; others suit a short written update. Record the preferred channel, useful contact times and any communication assistance requested, so the next administrator does not start again.
Stop automatic messages when the facts change
Consider a hypothetical installation booked for Friday. On Wednesday, the proposed inverter becomes unavailable and the job enters a change review. An automatic “we will see you on Friday” message would now be misleading, even if it was correct when queued.
Add a check for unresolved changes before scheduled messages leave the queue. Equipment variations, disputed dates, incomplete customer actions and conflicting records should route the message to its owner for review.
Preserve the earlier message and record the correction. Explain what has changed, the effect that is confirmed and when the remaining questions will be answered. Do not invent a replacement date to make the update sound more reassuring.
After installation, keep the wording equally precise. Our installation-to-close-out guide explains why an installation record is separate from metering, documentation and customer handover. An administrator should refer operating instructions to the installer rather than deriving them from an internal status.
Give the VA a queue with a backup owner
For every update, record the job reference, trigger, source checked, next contact date, message owner and any required reviewer. Keep a sent record and the customer's reply with the job. Store only the personal information needed for the task in approved systems.
Build two working views: updates due soon and exceptions needing a decision. A VA can prepare messages and manage follow-up while the relevant owner resolves the exception. Assign a backup so leave or an absence does not turn a promised call into a missed commitment.
If a customer replies with a new request, treat it as work requiring an owner. A sent message does not close the loop when its reply is still unanswered.
Review clarity as well as message volume
Track missed update commitments, unanswered replies and inbound status enquiries per active job over a defined period. Review the reasons for calls; some customers simply prefer speaking to a person, while others are asking because the message failed to explain the next step.
Sample a few conversations with the team. Was the status accurate? Was the customer action clear? Did the next contact happen? Improve the template or ownership rule responsible for the gap rather than rewarding a higher number of messages sent.
Start with one queue and a small set of reviewed templates. A clear sales-to-operations handover gives the communication owner a stronger starting point. Talk to Nexus about solar administration support to organise the follow-up around your team's actual workflow.
