What Fork Blocks actually do   

1. If the customer says X, respond with Y
   
2. If that does not match, check the next thing
   
3. If nothing fits, take them to a helpful fallback
   

Example

1. Order related help
   
2. Account help
   
3. Something else
   

Why this matters for your customers     

1. Personalise every step
   
2. Reduce back and forth
   
3. Send users to the right answer faster
   
4. Prevent unnecessary agent escalations
   

Advanced techniques

Fork with IM Variables

Fork Block with Operation Block      

Example  

1. A customer shares quantity and price.
   
2. Operation Block calculates total value.
   
3. Fork Block decides how to assist the customer based on that value.
   

Learn more about Operation Block

Fork Block with Webhook Block

How it works

1. The user enters a detail (for example: order ID)
   
2. A webhook sends this to your backend system for a status check
   
3. Your system returns a simple response such as:
   
1. SHIPPED
   
2. OUT_FOR_DELIVERY
   
3. YET_TO_SHIP
   
4. The Fork Block reads this result and decides the next step.
   

1. Webhook checks your system.
   
2. Response = OUT_FOR_DELIVERY
   
3. Fork Block routes to “Your order is on the way. Here’s your tracking link.”
   
4. If response = YET_TO_SHIP,  the Fork Block routes to “Your order is being prepared. We’ll notify you once it ships.”
   

 

How the three come together to create a smooth, intelligent WhatsApp bot   

1. IM variables help trigger the backend and retrieve user details
   
2. Webhook verifies backend information
   
3. Operation Block calculates values

Best Practices  

1. Map your branches before building: Sketch your decision paths on paper first
   
1. This prevents confusion when your flow grows; it will be easy to see where each condition leads
   
2. Use specific conditions first and general ones later
   
3. Always include an Else path
   

Final Thought