WhatsApp automation helps most with the first reply and the follow-ups that come after. A new lead gets an answer straight away, lands in your CRM with the conversation attached, and receives timed nudges until a person takes over.
Speed matters because people message several businesses at once. The one that answers first is often the one that gets the conversation.
The instant reply
When someone fills in a form or messages you, an automatic first message can confirm you received it, ask one or two useful questions and say when a person will respond. It does not need to be clever. It needs to be quick and honest.
Keep it short. Say who you are, thank them, and ask what they need. Do not pretend a person is typing if it is an automated message.
Capture the lead into your CRM
A reply on its own is not enough. If the conversation lives only on a phone, leads get lost when someone is away or leaves.
With WhatsApp connected to your CRM, people who message you become leads, with the conversation attached to the record. Your team sees the full picture and knows who owns the lead. If you do not yet have a pipeline, see moving from a spreadsheet to a CRM first, because automation on top of a messy process just makes the mess faster.
Timed follow-ups
Most leads do not answer the first time. A good follow-up sequence is modest:
- A prompt reply to the first enquiry.
- A gentle check-in if there is no response after a sensible wait.
- A reminder before a booked call or visit.
- A final polite message, then stop.
Stop the sequence when the person replies or the deal moves on. Nothing annoys a customer more than an automated message that ignores what they just said. Also give people an easy way to opt out.
Templates and approval
WhatsApp has rules for messages you start yourself. Those messages use templates, and templates need approval by Meta before you can send them. Approval can take time and a template can be refused, so plan for it.
Practical points:
- Write templates for the messages you send most, in plain words.
- Expect to adjust wording if one is rejected.
- Get consent before you message someone first.
- Do not build a flow that depends on a template you have not yet got approved.
WhatsApp charges for some kinds of messages, so ask what applies to you before you scale a flow.
A person must be able to step in
Automation should handle the repeat parts and hand over the rest. Decide in advance when a person takes over: a question outside the script, a price negotiation, a complaint, or any sign that the customer is frustrated.
Make the handover obvious to the customer, and make sure whoever picks up can see what has already been said. A flow that traps people in a loop is worse than no flow.
Test before customers see it
Have your own team try every flow as if they were customers. Try the odd answers too: a message in another language, a voice note, a one-word reply, silence. Fix what breaks. Then launch, watch real conversations for a while and refine.
What can go wrong
- Too many messages, so people block you.
- Templates that were never approved.
- No owner for leads that arrive out of hours.
- Messages that do not match what the CRM knows about the customer.
- Nobody reading the conversations after launch.
Where Teapot Techies fits
We connect WhatsApp to your CRM or Odoo, using the official WhatsApp Business platform, so messages follow its rules for consent and templates. We agree the few conversations that cost you most time, write the flows with you, decide when a person takes over, test with your team and review real conversations after launch. See WhatsApp automation and CRM for the detail.