Understanding this example
An interested customer asks to book a consultation. The sample first asks which service they need and what they want to improve. That gives the receiving team useful context before the customer moves to a scheduling link.
The design choice is how much information to collect inside the conversation. A short qualification step can be useful; repeating a long form in chat can make the customer abandon the process. Decide which fields are essential, who receives the conversation and when a person should take over.
Read the complete sample sequence
Use Next step above to explore the preview, or read every stage below. Selecting a stage changes the explanation shown; it does not perform that action.
The inquiry arrives
Customer: Hi! I would like to book a consultation for my business.
Ask the right question
WhatsApp assistant: Happy to help. What service are you interested in, and what would you like to improve?
Connect to booking
Booking handoff: The sample customer receives a booking link and their inquiry is ready for the team.
What to look for
- The opening request is acknowledged before another question is asked.
- The qualification question relates to the service and business problem.
- The handoff gives a booking route without claiming that sending a link reserves a slot.
What happens when the request changes?
Test scenario: I have a complaint and want to speak to someone.
A production flow should stop the qualification loop and route the conversation to an accountable person with its existing context. It should not keep sending booking prompts while the complaint is unresolved.
What this demonstration does and does not do
No WhatsApp account is connected here. Advancing the steps does not send a message, write to a CRM or contact your phone number.
Prepare for a connected version
A production workflow needs agreed access, ownership and recovery behavior. Bring these details to discovery:
- An authorized business messaging account and official integration route.
- Approved conversation questions, opt-out handling and message ownership.
- A team inbox and a recovery process for failed handoffs.
Continue with Plan an n8n lead workflow that stops when it should for a deeper planning checklist.
Published by FindSolution. These examples explain a design choice; they are not client case studies or evidence of a live integration. Read our editorial approach.