Sales Follow-Up
How to Reconnect with Old WhatsApp Enquiries Without Sending a Generic Broadcast
An old enquiry is useful context, not automatic permission for a new campaign. Start with the buyer’s previous need and a real reason to reconnect.
Your CRM has hundreds of old enquiries. Someone suggests sending all of them “Hi, are you still interested?” It feels efficient, but the list includes buyers who already purchased, people who asked you to stop and projects that were never a fit.
To re-engage old leads on WhatsApp thoughtfully, first decide who has a relevant reason to hear from you. Then write a message that remembers the previous conversation and makes it easy to continue—or decline.
Clean the audience before writing copy
Remove opt-outs, wrong numbers, unresolved complaints requiring a different owner and contacts whose needs are no longer relevant. Check permission for the proposed communication. A number appearing in an old spreadsheet is not enough to justify a fresh campaign.
Review Meta’s current policy and your own contact records. If you cannot establish an appropriate basis to message someone, do not include them simply to make the audience larger.
Segment by the reason the conversation stopped
| Previous situation | Potentially useful reason to reconnect |
|---|---|
| Buyer asked to revisit later | The agreed month or milestone has arrived. |
| Requested option was unavailable | That specific option is now genuinely available. |
| Buyer needed a missing detail | You can now answer the unresolved question. |
| Project scope was unclear | Ask whether the project has become defined, if contact is appropriate. |
| No fit or explicit refusal | Do not treat this as a routine reactivation audience. |
Use actual CRM history, not an invented personal detail. If the previous requirement is unclear, review the conversation before sending anything.
When the buyer asked you to return later
Hi [name], when we discussed [project], you suggested revisiting it around [month]. Is that still a useful time to look at the options, or has the plan changed?
This works because it refers to an agreement. Do not use it for contacts who never asked for another message. Give the recipient a simple way to say the project is paused.
When something relevant has changed
You previously asked about [specific option], which we couldn’t offer then. It is now available under [brief accurate condition]. Would you like the details, or should we leave this enquiry paused?
Check the update before sending. Avoid manufactured scarcity, invented deadlines and “special offers” that are available to everyone indefinitely. A genuine update does not need pressure to explain its relevance.
Plan for the replies before launching
Who will answer questions? What happens if the buyer has a new requirement? Which sequence stops when they reply? A campaign that produces responses but leaves them unattended can make the old problem worse.
Keep “interested,” “later,” “not relevant” and “stop” distinct. Update the record accordingly. Do not restart a sequence after someone opts out through a different channel.
Use a small reviewable batch
Start with a narrow group sharing one genuine reason for contact. Inspect the wording with realistic fictional examples, confirm the destination links and check how replies reach the team. For WhatsApp Platform sends, use the appropriate approved-template process where required.
Measure useful replies, qualified next steps and sales outcomes alongside opt-outs and negative feedback. A high delivery count does not show that the contact was welcome. Compare the same audience definition over time and avoid attributing every later sale to one message.
Make old enquiry review part of CRM hygiene
A clear pause reason and review date today make future contact more relevant. Our pipeline guide explains how to separate paused opportunities from active work.
Plan an old-enquiry review with SHVYA. Bring your audience categories and examples of why conversations stopped. Start with the segment you can help, then build the message and reply-handling process around it.
