The first job creates a new customer state
The work is complete, the customer has paid and the record goes quiet. Later, someone sends a generic offer without checking whether the first job went well.
Post-job follow-up should begin with the service that was delivered. Confirm completion, give necessary aftercare, make support easy and then consider whether another conversation would be useful.
This workflow is a practical design to test. It does not prove a repeat-purchase lift. Some services naturally repeat; others do not. A customer who never needs the same service again may still have received excellent work.
Keep four purposes separate
A completion check asks whether the agreed job is finished. Support handles an unresolved issue. Feedback helps you understand the experience. A future-service invitation proposes another commercial action.
Do not hide an offer inside a message that appears to be only a service update. Keep the purpose understandable and check permission for the channel and type of contact. Resolving a complaint should not trigger a sales pitch.
| Stage | Question to answer | Example next action |
|---|---|---|
| Completion | Was the agreed work delivered? | Confirm scope and provide the relevant document or instructions |
| Support | Is anything unresolved? | Assign an issue to the person who can resolve it |
| Feedback | What worked or caused friction? | Ask one neutral question about the experience |
| Future service | Is another action relevant and welcome? | Offer an appropriate next step with a clear purpose |
Choose timing from the service. A result that becomes visible after several weeks needs a different check from a job the customer can inspect immediately. Set a starting schedule, then review whether it reaches people at a useful moment.
Write a completion message with an easy support route
Example: “Hi [name], we've completed [agreed work]. Here's [handover item/instructions]. If something in that scope still needs attention, reply here and [responsible team] will review it.”
Check the facts before sending. Completion should come from the delivery record, not a timer that assumes every job finishes on schedule. Include the actual scope rather than a vague claim that everything is done.
Assign replies to an owner. The customer should not need to explain the issue again to three people. Keep a support state that pauses any unrelated sales follow-up until the issue has been handled appropriately.
Ask for feedback without steering the answer
Example: “Now that you've had a chance to use [delivered service], what worked well and what could have been clearer?”
Use the answer to improve the process. Record themes without copying private customer details into public reports. A positive comment does not automatically grant permission to publish a testimonial.
Avoid asking only satisfied customers for information you then present as a representative result. Keep the invitation rule consistent so your own feedback records are easier to interpret.
If someone reports a problem, acknowledge it and route it. Do not ask for a public review while their issue remains unresolved.
Offer the next service only when it makes sense
Example: “If [specific next need] is coming up, we can help with [relevant service]. Would you like the details, or would you prefer to contact us if you need it?”
The link between the first job and the next service should be real. A maintenance plan may be relevant after installation; a completely unrelated offer may not be. Do not use a fictional “recommended” label to disguise a generic campaign.
Stop if the customer declines or withdraws permission. A past purchase should not be treated as indefinite permission for every channel and message type. For WhatsApp, follow the current Business Messaging Policy and the requirements of your delivery setup.
Run a small pilot with a stop rule
Choose a defined group of completed jobs, one service and a clear observation period. Record how many customers are eligible for each message, how many are contacted, replies, support issues, opt-outs and confirmed future bookings.
Write the stop rule before starting. Pause if messages go to unfinished jobs, opt-outs fail to stop contact, unresolved issues receive offers, or the team cannot respond to the replies. Those failures call for a process repair.
Compare like-for-like groups where possible. Repeat bookings can change because of season, price or customer mix. A before-and-after increase is useful to investigate, but it does not isolate the follow-up's effect.
Keep the first report modest: what was sent, to how many eligible customers, what happened and what needs changing. Rainlight's follow-up blueprint helps map the decisions. Its service-business briefing is relevant when delivery records, customer messages and bookings need to stay connected.