# How to Unsubscribe and Resubscribe Customers to a Sequence in ZazzyAgent Sometimes a customer should stop receiving a sequence. Sometimes you need to remove them and start the sequence again from the beginning. This is useful when: * A customer completed the original journey. * The customer purchased. * A sequence was started by mistake. * A test customer needs to be reset. * A delivery problem interrupted the sequence. * You need to restart a customer's follow-up journey. Understanding the difference between **unsubscribe** and **resubscribe** makes sequence management much easier. ## What does unsubscribing do? Unsubscribing removes the customer from the sequence. For example: ```text Customer ↓ Sales Follow-up ↓ Customer purchases ↓ Remove Sales Follow-up ``` The customer should no longer continue receiving messages from that sequence. ## When should you remove a customer? The most obvious example is when the original goal has been completed. ### Sales sequence ```text Lead ↓ Sales Follow-up ↓ Purchase ↓ Remove Sales Follow-up ``` ### Appointment sequence ```text Appointment Reminder ↓ Appointment completed ↓ Remove Reminder Sequence ``` ### Abandoned-cart sequence ```text Cart Abandoned ↓ Cart Recovery ↓ Purchase completed ↓ Remove Cart Recovery ``` Leaving customers in the old sequence can cause irrelevant messages later. ## Remove a sequence from a subscriber Open Subscriber Manager and locate the customer. Open the customer's profile. Review the sequence information associated with the subscriber. Remove the sequence assignment and save the change. The exact controls available can depend on the connected channel and account configuration. ## What happens after removal? The customer is no longer enrolled in that sequence. This does not mean the customer is removed from ZazzyAgent. The customer record can still contain: * Name * Phone number * Labels * Custom fields * Previous conversation information * Other sequence information Removing one sequence should be treated as a change to the customer's automation journey, not deletion of the customer. ## When should you resubscribe a customer? Resubscription is useful when you intentionally want to start the sequence again. For example: ```text Customer ↓ Sequence started ↓ Customer removed ↓ New qualifying event ↓ Sequence starts again ``` This can also be useful while testing a sequence. ## Example: Restart a lead journey Suppose a lead entered: > New Lead Follow-up The lead later asks: > Can you send me the information again? You may decide to restart the follow-up journey. The process can be: ```text Existing Sequence ↓ Remove customer ↓ New subscription ↓ Sequence starts again ``` Use this deliberately rather than restarting sequences every time a customer sends a message. ## Resubscribe from the original flow A customer can re-enter a sequence through the automation that originally subscribed them. For example: ```text Customer ↓ Clicks Subscribe ↓ Sequence ``` After the customer has been removed: ```text Customer ↓ Clicks Subscribe again ↓ Sequence ``` The same flow can therefore be used as the entry point again. ## Resubscribe through a trigger Where your sequence is connected to a keyword or another supported trigger, the customer can trigger that path again. Example: ```text Customer sends: course ↓ Course Flow ↓ Subscribe to: Course Follow-up ``` Removing and then re-triggering the flow can restart the customer's sequence journey. ## Don't confuse sequence removal with unsubscribing from the platform There are several different concepts that can sound similar. ### Remove from a sequence Stops one specific sequence. ### Unsubscribe from broader automation May affect other communications depending on the configured action. ### Delete subscriber Removes the customer record. These are not the same operation. Be careful when choosing an action. ## Example: Customer purchases Imagine a customer is enrolled in: > Product Follow-up Then they purchase. Your automation should ideally do: ```text Purchase detected ↓ Remove Product Follow-up ↓ Add Customer label ↓ Start Post-Purchase Sequence ``` This creates a clean lifecycle. ## Example: Customer changes their mind Suppose a customer entered: > Premium Plan Follow-up Then they say: > I'm actually interested in the Starter plan. The old sequence may no longer be appropriate. A better workflow is: ```text Premium Follow-up ↓ Remove ↓ Starter Follow-up ↓ Continue ``` This prevents conflicting messages. ## Using sequences with labels Labels can make lifecycle management easier. For example: ```text Interested ↓ Sales Follow-up ↓ Purchased ↓ Remove Sales Follow-up ↓ Add Customer ↓ Post-Purchase Sequence ``` The label records customer state. The sequence controls ongoing communication. These are different jobs. ## Resubscription during testing Sequence reset is especially useful while building automations. For example: ```text Test Subscriber ↓ Sequence Message 1 ↓ Test configuration ↓ Remove sequence ↓ Subscribe again ↓ Test Message 1 again ``` This lets you repeatedly test the beginning of a sequence without waiting for the entire campaign to finish. ## What if a customer never received a sequence message? Don't immediately rebuild the sequence. Check: 1. Whether the customer is still enrolled. 2. Whether the sequence is active. 3. Whether the message was targeted. 4. Whether the message was sent. 5. Whether the message was delivered. 6. Whether a WhatsApp template was required. 7. Whether an error occurred. If the problem is fixed, removing and re-enrolling the customer can be one way to restart the journey. ## Avoid accidental duplicate enrollment Before resubscribing a customer, confirm that they aren't already enrolled. Otherwise you can create confusing customer journeys. A useful lifecycle is: ```text Not enrolled ↓ Enrolled ↓ Completed / Removed ↓ Eligible again ↓ Re-enrolled ``` The important word is **eligible**. Don't make resubscription automatic simply because a customer sends another message. ## Common problems ### Customer remains in the sequence Check that the sequence was actually removed and the change was saved. ### Customer receives follow-ups after purchase Review the purchase workflow and make sure the relevant pre-purchase sequence is removed. ### Customer cannot re-enter the sequence Check that the previous subscription was removed and that the trigger or subscription action is still configured correctly. ### Customer appears to receive the wrong journey Check whether another sequence is still active. A customer can have more than one automation path, so inspect the complete sequence state. ## Best practice Treat a sequence as a lifecycle stage. When the customer moves to another stage, update the automation. For example: ```text New Lead ↓ Sales Follow-up ↓ Qualified ↓ Demo ↓ Purchased ↓ Post-Purchase ``` Each transition should be intentional. ## The key idea Removing a customer from a sequence doesn't delete the customer. It changes what automated communication should happen next. Use unsubscribe when the current journey should stop. Use resubscribe when the customer genuinely needs to start that journey again. For the broader sequence workflow, see [WhatsApp Sequences: How to Create Automated Follow-Ups](https://blog.zazzyagent.com/whatsapp-sequences-guide).