# How to Trigger a Sequence from a ZazzyAgent Flow A sequence is designed to continue communication after a customer enters an automation. But before the sequence can send anything, the customer needs to be enrolled. [ZazzyAgent](http://zazzyagent.com) supports several ways to start a sequence from an automation, including triggering it from a flow or allowing the customer to subscribe through an interactive action. This guide explains how to build that connection. ## When should a flow start a sequence? Use a sequence when the immediate conversation is finished but the customer still needs follow-up. Examples: ```text Lead submits enquiry ↓ Flow captures details ↓ Customer enters Lead Follow-up sequence ``` Or: ```text Customer asks about a product ↓ Product information ↓ Customer chooses "Send me updates" ↓ Sequence starts ``` The flow handles the immediate interaction. The sequence handles what happens later. ## Method 1: Trigger a sequence from a customer action This is useful when you want the customer to explicitly opt into the follow-up. For example: > Would you like us to send you product updates? Buttons: **Yes, send updates** **No thanks** The "Yes" action can subscribe the customer to the selected sequence. This creates a simple journey: ```text Question ↓ Customer clicks Yes ↓ Subscribe to Sequence ↓ Confirmation ↓ Scheduled Follow-ups ``` ## Step 1: Create the sequence Before connecting the flow, create the sequence you want to use. Give it a clear internal name. Good examples: * New Lead Follow-up * Product Education * Demo Follow-up * Abandoned Cart * Appointment Reminder Avoid names such as: > Sequence 1 or: > Test Sequence You'll eventually have more than one sequence, and clear names make them much easier to identify. ## Step 2: Create or open your Flow Open Flow Builder and create the flow that will lead into the sequence. For example: ```text Start ↓ Welcome ↓ Ask customer what they need ↓ Product information ↓ Subscribe ``` The sequence should be connected to a meaningful event, not simply placed somewhere because it is available. ## Step 3: Add the subscription action Add an interactive element such as a button where the customer makes the decision. Configure the button to subscribe the customer to the required sequence. Select the correct sequence. Double-check the sequence name before saving. A common mistake is selecting a similarly named sequence. ## Step 4: Add a confirmation message After the subscription action, send a short confirmation. For example: > Perfect. I'll send you the information over the next few days. This tells the customer that their action worked. The flow can then end or continue into another process. ## Method 2: Start a sequence from a keyword-triggered flow Sequences can also be associated with a flow triggered by a keyword. For example: ```text Customer: guide ↓ Guide Flow ↓ Subscribe to: Product Education ``` This can be useful when customers intentionally start a particular journey. However, a button-based opt-in is often clearer when the customer needs to make an explicit choice. ## Keyword trigger vs button subscription The two approaches serve different purposes. ### Keyword Useful when the customer intentionally starts a flow. Example: > Customer sends `guide` Then: ```text guide ↓ Guide Flow ↓ Sequence ``` ### Button Useful when the customer makes a clear decision during the conversation. Example: > Would you like the 5-day product guide? **Yes** → Subscribe This generally creates a clearer customer journey. ## Don't start every sequence immediately A common mistake is subscribing every customer to the same follow-up sequence. For example: ```text Customer asks: What's your price? ↓ Automatically start 14-day sales sequence ``` That customer may only have wanted a price. Instead, look for a meaningful event. For example: ```text Customer asks for pricing ↓ Provide pricing ↓ Customer asks for product demo ↓ Start Demo Follow-up ``` The sequence should reflect customer intent. ## Combine a flow with customer data A useful flow may collect information before enrolling the customer. For example: ```text Name ↓ Product Interest ↓ Budget ↓ Timeline ↓ Subscribe to Sequence ``` The customer then enters a follow-up sequence with their relevant information already stored. This is especially useful for lead qualification. For example: ```text Lead qualification ↓ Qualified Lead ↓ Add label ↓ Start Sales Follow-up ``` ## Starting different sequences based on a condition You don't have to use the same sequence for every customer. For example: ```text Customer selects: Enterprise ↓ Enterprise Follow-up Customer selects: Starter ↓ Starter Follow-up ``` Conditions can route customers into different journeys. This is one reason labels, custom fields and sequences work well together. ## Example: Real estate enquiry A flow could ask: > Which property type are you interested in? **Apartment** **Villa** **Commercial** Then: ```text Apartment ↓ Apartment Lead Sequence Villa ↓ Villa Lead Sequence Commercial ↓ Commercial Lead Sequence ``` Each sequence can contain different follow-ups. ## Example: Service business Customer: > I want a consultation. Flow: ```text Service ↓ Preferred date ↓ Contact details ↓ Confirmation ↓ Appointment Follow-up Sequence ``` The sequence can then send reminders or additional information at the appropriate stages. ## Prevent duplicate enrollment One of the most important rules is: > Don't repeatedly subscribe an already enrolled customer to the same sequence. For example: ```text Customer asks: Can you send me the brochure? Customer asks again: Can you send me the brochure? ``` If each message triggers the same enrollment logic, the customer could end up entering the same follow-up journey multiple times. Design the trigger around a meaningful event rather than a generic message. ## Remove the sequence when the goal is completed Starting a sequence is only half of the lifecycle. Suppose: ```text Customer ↓ Sales Follow-up ↓ Customer purchases ``` The customer should normally stop receiving pre-purchase follow-ups. Your workflow can remove the sales sequence when the purchase is completed, then start a post-purchase sequence where appropriate. This prevents customers from receiving messages that no longer make sense. ## Test the sequence trigger Always test the complete path. ### Test 1: Trigger works Perform the exact customer action. Verify that the customer enters the intended sequence. ### Test 2: Correct sequence Confirm that the right sequence was selected. ### Test 3: No accidental enrollment Repeat the trigger and make sure your logic doesn't unnecessarily enroll the customer again. ### Test 4: Sequence timing Confirm that the first scheduled message occurs according to the sequence timing. ### Test 5: Completion logic Complete the intended customer journey and verify that any required removal or replacement logic works. ## Common problems ### The sequence doesn't start Check: * The correct sequence was selected. * The button/action is connected correctly. * The flow is published. * The customer actually reached the subscription step. * The sequence itself is active. ### The wrong sequence starts Check the sequence selected in the action. This is particularly important when several sequences have similar names. ### Customer receives multiple follow-ups Check whether the same customer can reach the subscription action more than once. ### Sequence starts too early Move the subscription step later in the flow so it is connected to a meaningful qualification or customer action. ## Recommended architecture For many businesses, this structure works well: ```text Customer ↓ Flow ↓ Collect information ↓ Validate / qualify ↓ Customer reaches meaningful milestone ↓ Subscribe to Sequence ↓ Follow-up messages ``` The flow handles what is happening now. The sequence handles what should happen next. ## The key idea A sequence should start because something meaningful happened in the customer journey. Don't think of it as: > "Where can I add a sequence?" Think: > "At what point does this customer become ready for follow-up?" That point is usually the right place to trigger it. For the complete sequence setup, see [WhatsApp Sequences: How to Create Automated Follow-Ups](https://blog.zazzyagent.com/whatsapp-sequences-guide).