WhatsApp lead management: from message to owned enquiry

Choose the level of connection you actually need

A direct WhatsApp link can be a sensible starting point when one person handles enquiries. The visitor opens an editable message and chooses whether to send it. Measure that click as contact intent, not as a submitted enquiry or booked appointment. Give the responsible person a simple way to record the resulting conversation.

If several people need assignment, shared visibility and reliable CRM context, evaluate a supported integration. Ask which product and account configuration it uses, how ownership is represented and how a failed transfer appears. Do not assume that a website button or a messaging subscription includes those capabilities.

Keep the record small and useful

For an illustrative property-maintenance enquiry, useful context might be the service requested, the site area, the preferred reply language and whether a visit needs arranging. Preserve the customer's message or a faithful summary, its source and the person who reviewed it. A field labelled 'new WhatsApp lead' tells the next person very little.

A repeat message can be a continuation or a different request. Keep a conversation reference where the integration supports it, and let the owner distinguish a new opportunity from an update. Never merge records solely because two names look similar.

• Source and time received
• Request summary and any agreed next step
• Assigned owner and backup
• Reply preference and relevant permission record
• Delivery or sync exception that needs review

Design follow-up around the channel's current rules

WhatsApp's Business Messaging Policy requires recipient permission for subsequent messages and respect for opt-out requests. For the Business Platform, free-form replies are permitted within the 24-hour customer-service window after a user message; outside that window, approved templates are required. The policy also requires a clear escalation route when automation responds. Review the linked policy before implementation because platform rules can change.

Build a useful follow-up around what the customer asked. A requested quotation update and an unrelated promotional campaign are different jobs. Record why the message should be sent, who approves its wording and how a stop request suppresses further contact. An automation should not keep pursuing someone simply because the opportunity remains open.

Work through an exception before launch

Example: a customer asks for a site visit after the sales coordinator's working hours. Capture the request if the supported integration permits it, assign the next staffed review and avoid promising a confirmed appointment. If the integration is unavailable, the exception should reach the person who can use the agreed manual route.

Test a duplicate inbound event, an unassigned message, an opted-out recipient and a rejected outbound template. Review the customer's view as well as the CRM. A green automation run does not establish that the right person received a useful answer.

Measure conversations that move forward

Track opened contact links separately from received conversations. Then review ownership, first useful response, qualified enquiries and unresolved exceptions. Keep the same definitions over time so a change in reporting does not look like an improvement in sales.

For a small team, the first improvement may be a named owner and a daily review of unanswered requests. Add automated messaging after the human process is clear enough to encode.