A lead that arrives through WhatsApp, a website form or email does not automatically become a business opportunity. If every source lands somewhere different, the team may miss the enquiry, reply twice or lose the context of what the customer already said.
The goal of lead automation is not to connect another tool. It is to create a clear path: intake, validation, deduplication, routing, first response and follow-up — with a person responsible for exceptions.
Start with an input map, not a CRM
List every entry point: a business WhatsApp number, contact forms, email addresses, website chat, campaign forms and manually forwarded enquiries. For each source, document:
- what data arrives and in what format;
- what identifies the person — phone, email or both;
- what happens when a required field is missing;
- who receives the alert and what response time you want;
- where the conversation and enquiry history is stored.
On the WhatsApp Business Platform, for example, incoming messages and events can be received through Webhooks, while messages are sent through the API. That makes an integration possible; it does not define the business process for you.
Meta documentation: WhatsApp Business Platform
Normalize the data before routing it
Before creating a new record, check whether the person already exists. Email and phone are useful identifiers, but they may be missing or formatted differently. Define:
- required and optional fields;
- phone and email normalization;
- a duplicate-detection rule;
- what happens when two records are possible matches;
- which source and first message are retained for context.
Do not let an AI model decide on its own to merge or delete records. It can summarize, classify and suggest an action, but irreversible changes need permissions and review.
Make routing rules easy to explain
Once the information is normalized, define rules that a new team member could understand: service area, language, enquiry type, location or urgency. Each rule also needs a fallback path:
- Clear match: create a task and assign an owner;
- Missing information: request it or mark the lead for review;
- Exception or high-risk case: hand it to a person;
- Duplicate: add activity to the existing record instead of creating another lead.
Rather than alerting everyone, define an owner, a backup and an escalation point for an enquiry that remains untouched. Good automation shows what did not happen as well as what did.
A first response is not the same as follow-up
You can send an acknowledgement or a short question automatically, but separate an automated message from a business promise. Do not promise a price, availability or suitability before the relevant information has been checked.
Email automation tools can trigger a flow when a message arrives and filter by folder, sender, subject or attachment. Where possible, apply the filter in the trigger instead of running a flow for every message and filtering later.
Microsoft Learn: trigger a flow from email properties
Test the workflow before switching it on
- Send an enquiry from each source and confirm it is recorded once.
- Test a person who contacts you through two different channels.
- Try a missing field, a differently formatted phone number and another language.
- Check that the alert reaches the right owner and that a backup exists.
- Confirm that the team member can see the source, context and history.
- Test an API failure, duplicate event and retry without creating two activities.
- Define who may access personal data and how long it is retained.
Start with a narrow process and measure response time, the share of enquiries with an owner, duplicates and exceptions. There is no universal success metric; the right measure depends on the process you defined.
The bottom line
Connecting WhatsApp, forms and email is only the intake layer. The business result depends on what happens next: is the data unified, is there an owner, is the context preserved, and can a person stop or correct the workflow?
If you cannot draw the path from an incoming enquiry to the next action, it is too early to choose a tool. Map the process, define exceptions and run a pilot where automation suggests — and a person approves.
For the next step, read How to choose the first business process to automate and Business website brief: 15 questions.