Follow up on the unfinished decision
Someone asks about a service, receives a reply and goes quiet. “Just checking in” adds another notification without making the decision easier. A useful follow-up answers something, removes friction or offers a clear way to close the conversation.
Choose the message from the last unresolved step. Did the person need a price, a date, a description of the service or time to decide? Do not send a booking reminder to someone who never agreed the service was a fit.
The examples below are original drafts for adaptation. They are not client messages or tested conversion winners. Replace every bracket, verify every promise and use the customer's chosen channel.
First check whether the message may be sent
WhatsApp's current policy requires permission for subsequent contact and respect for opt-outs. For the Business Platform, free-form replies are limited to the 24-hour service window; outside it, approved templates are required. These samples are writing aids, not approved platform templates. Check the policy and your actual delivery setup before sending.
1. The enquiry needs one more detail
“Hi [name], you asked about [service]. To give you the right answer, is this for [option A] or [option B]? If neither fits, tell me what you need and I'll pass it to [team/person].”
Use this when the missing answer changes the route. Keep the options meaningful: one-off help versus ongoing support, for example. Avoid asking the customer to complete a whole sales questionnaire in chat.
If they already gave the answer, acknowledge it instead of repeating the question. A workflow that loses context can look busy while making the experience worse.
2. A quoted price needs context
“Hi [name], one detail that may help with the [service] quote: it includes [verified inclusion]. [Optional work] is separate. Would you like me to clarify the scope, or is the timing the main question?”
Use this when a genuine scope question may be blocking the decision. State the actual inclusion and exclusion. Do not invent a discount, deadline or limited availability to force a reply.
For a complex quote, have the person responsible for pricing review the message. An assistant can draft a summary; it should not quietly change the commercial terms.
3. The customer is interested but has not chosen a time
“Hi [name], if you'd like to discuss [specific need], you can choose a time here: [booking link]. The [duration] conversation covers [purpose]. If none of the times work, reply with your preferred day and we'll check.”
Explain what the meeting is for. A link without context can feel like another task. Check that the page offers the intended service and timezone, and that the team can handle requests for another time.
Before sending, look for an existing booking. If one exists, the next useful message is appointment information, not another invitation to book.
4. The timing is wrong
“Thanks for letting me know, [name]. Would you prefer to contact us when you're ready, or would a message around [agreed date] be useful?”
Use this after the person says the timing is wrong. Give them control over whether there is another message. Record the agreed date only if they choose one. “Not now” should not silently become a daily nurture sequence.
If the answer is no, close the follow-up task. A clean closed record is useful operational information, even when no sale occurs.
5. Close an unanswered conversation
“Hi [name], I'll close this enquiry for now so we don't keep sending reminders. If you still need help with [service], you can reply here and we'll pick it up.”
Use this at the end of a limited follow-up attempt when contact is permitted. Closing means stopping the sequence. It does not mean deleting the conversation or pretending that silence is rejection.
Avoid guilt, false urgency and repeated “last chance” messages. The purpose is to make the state clear for the customer and the team.
Choose timing from your own evidence
There is no universal schedule that these templates prove. Start with the service's decision cycle, any promised response time and the customer's stated preference. A time-sensitive booking question differs from a large project quote that needs internal approval.
Review a bounded batch of enquiries. Record the unfinished step, message sent, reply, booking, opt-out and human handoff. Compare like-for-like enquiry types. Ten replies from a hundred messages mean something different from ten replies from twenty.
A reply is not necessarily a positive result. “Please stop” is a reply too. Review message quality and downstream fit before adopting a template as the default.
Use Rainlight's value-led follow-up blueprint to map the next useful move for each stage. If the problem is that messages, qualifications and bookings are stored in separate places, review the service-business workflow before adding more messages.