Build conversations, one clear step at a time.

Before you start: A contact email field, a sales agent and an optional lead journey.

1. On Keyword Match: DEMO
2. Ask Question: name
3. Ask Question: email
4. Update Contact Profile
5. Add / Remove Tag
6. Assign to Agent
7. Send Text Message
8. End Flow

1. Use an Exact DEMO keyword so the customer starts this flow intentionally.
2. Save answers as lead_name and lead_email. Enable email validation and connect Invalid to a friendly retry question.
3. Map lead_name to the contact name and lead_email to email in Update Contact Profile. Add demo_requested and optionally move the lead to your qualification stage.
4. Assign a sales agent, acknowledge the request and finish. Agree on bot pause behavior for the human conversation.

Before you start: A WhatsApp connection, support agent and configured opening hours.

1. On Keyword Match: MENU
2. Quick Reply Buttons
3. Opening Hours
4. Assign to Agent
5. Send Text Message
6. End Flow

1. Create Shop, My orders and Talk to team buttons; connect each output to its own action.
2. On Talk to team, add Opening Hours. Route Open to Assign to Agent and a handoff message.
3. Route Closed to a message stating your opening hours and an Ask Question for the enquiry. Save the answer to a custom contact field or notify staff before ending.
4. Connect the menu’s fallback, where available, to “Please choose an option” rather than leaving an unanswered path.

Before you start: A configured company OpenRouter key/model, trained knowledge sources and a support agent.

1. On Incoming Message
2. AI Agent / LLM
3. Send Text Message
4. End Flow

1. Open AI Knowledge Training from the tools panel. Add current FAQs, documents or website content and wait for training to complete.
2. In AI Agent / LLM, enable knowledge search and write a system instruction to use your business information and say when an answer is unknown. Use contact_last_message as the customer question.
3. Keep the output variable ai_response. Connect the normal path to Send Text Message containing {{ai_response_message}}.
4. Add a human_support intention for requests to speak to a person. Connect its output to Assign to Agent, a handoff message and End Flow; connect the fallback too.

Before you start: Connected store data and a test customer with past orders.

1. On Keyword Match: ORDERS
2. Send Orders List
3. Send Order Receipt
4. End Flow

1. Start with an Exact ORDERS keyword and send an Orders List using the selected_order prefix.
2. Connect the Selected output to Send Order Receipt and review its selected_order variables.
3. If you need an explicit lookup instead, use Fetch Order Details before Send Order Receipt.
4. Connect the fallback to “We could not find an order. Our team can help” and offer an agent.

Before you start: An abandonment integration, customer opt-in and an approved cart-recovery template.

1. Abandoned Cart
2. Execution Counter
3. WhatsApp Template
4. End Flow

1. Enable abandonment detection in your store integration and confirm that its event includes an identifiable customer and the checkout data you need.
2. Set an Execution Counter limit suitable for your campaign. Route True to an approved recovery template and False to End Flow.
3. Map the template’s parameters and checkout URL from the actual event variables. Keep the invitation helpful and respect opt-outs.
4. If offering assistance after a reply, use On Template Button Click with a quick reply such as “Help me” and route it to an agent.

Before you start: The Reminders module, a reservation and approved confirmation/reminder templates.

1. Reservation Created
2. WhatsApp Template
3. End Flow

1. Create a reservation through your existing booking process. Reservation Created receives that event and sends the confirmation template.
2. Create a separate Reminder Due flow to send the reminder template at the scheduled time. The reminder record controls the appointment timing.
3. Create a Reservation Cancelled flow for cancellation messages or staff alerts.
4. Map date, time and location from the actual reservation/reminder variables and test the configured timezone.

Before you start: Configured verification channel and the node’s recipient/reference settings.

1. On Keyword Match: VERIFY
2. Request Verification
3. Ask Question: code
4. Verify Code
5. Send Text Message
6. End Flow

1. Configure Request Verification for the supported channel and recipient. Store/use the verification reference exposed by the node.
2. Ask for the code and save it to verification_code. Map that answer and the request reference into Verify Code.
3. Connect Verified to a success message and your next permitted action.
4. Connect Failed to a clear retry or fresh-code path; use a counter if you need to limit repeated attempts.

Before you start: Configured Commerce events and approved payment/subscription templates.

1. Payment Received
2. WhatsApp Template
3. End Flow

1. Use Send Payment Link for a specific amount, or Send Checkout Link for cart items, in your purchase flow.
2. Create a separate Payment Received flow for confirmation after the integration reports success.
3. Create a Payment Failed flow with a helpful retry/support option. Use separate subscription event flows for activation, renewal, cancellation and expiry.
4. Map amounts, currency and subscription dates from the event’s real data.