What questions should you ask a new WhatsApp sales lead?

Begin with the customer’s task. “What would you like help with?” or a short choice of services is often more useful than asking for a budget before the person knows what you offer. Use words that match the business rather than internal sales categories.

Explain the purpose of a necessary question. “Which city is the property in? That helps us route you to the local team” gives the customer a reason to answer. Do not make someone repeat details they already supplied in the conversation.

Prepare a question record before building the flow. The exact wording and whether it is required depend on the service. A short menu works when the choices are meaningful; free text or a person may be more useful for an unusual request.

Replace internal labels with a question a customer can answer.

Instead of “Lead category?” ask “Are you looking for a new property or help selling one?” when those are your actual services.

Instead of “Budget mandatory” ask “Do you have a budget range in mind, or would you like the team to explain the options first?”

Instead of “Urgency score?” ask “Is there a date you need this ready by?”

These examples are illustrative. Do not collect every field simply because it appears in a template. Test the wording with the people who answer your enquiries.

Start with whether the person wants to buy, rent or discuss another supported service. Ask the relevant area and property requirements. If timeframe and budget affect the shortlist, explain that and allow uncertainty.

The result should be a usable enquiry for the property team. Do not imply that a requested viewing has been scheduled until availability and booking are confirmed. The real-estate WhatsApp guide connects these fields to follow-up and viewing ownership.

A person who has not decided on a budget may still need advice. Route that request appropriately instead of labelling them a poor lead without evidence.

An agency may need to know the business goal, the service being considered and who will own the work. Ask about timing when it affects capacity. Detailed technical access can wait until the service scope is understood.

Illustrative opening: “Which part of your customer messaging would you like help with?” Follow with “What is happening today?” before collecting implementation details. The agency guide covers the agency’s own enquiry intake and client-service ownership.

For a hotel, the useful fields are different: dates, guests and the type of stay. Use the hotel guide rather than copying an agency intake form into reservations.

Decide which answers are essential and which only improve context. If a missing field blocks the next step, explain the specific reason. If it does not, let the enquiry continue.

Keep a visible human exit. A customer who asks for a person should not be forced through the remaining questionnaire. Preserve the answers already supplied and tell the customer where the request is going. Use the handoff decision guide to write that response.

Treat contradictory answers as something to clarify, not permission to guess the customer’s intent.

No. Collecting details for an enquiry and obtaining permission for later business-initiated messages are separate tasks. The WhatsApp Business Messaging Policy sets opt-in and opt-out requirements. Keep the purpose of a question clear and avoid collecting unnecessary personal information.

Use the opt-in guide when planning follow-ups. Do not turn a request for a quote into blanket consent for unrelated campaigns.

Write the condition that uses each answer and name the receiving owner. The automation-without-AI worksheet helps you map the task before using the Logic Flow editor.

Test complete answers, uncertainty, a changed answer and a requested person. Then review where customers stop or need clarification. Improve the question that causes confusion; adding more mandatory fields is not automatically an improvement.