# How to Monitor WhatsApp Sequence Delivery and Performance in ZazzyAgent Creating a sequence is only part of the job. You also need to know what happened after the messages were scheduled. Did [ZazzyAgent](http://zazzyagent.com) target the customer? Was the message sent? Was it delivered? Did one particular step fail? Sequence reporting helps answer those questions. ## Why monitor sequences? Suppose you create this sequence: ```text Day 0 Welcome ↓ Day 1 Product information ↓ Day 3 Follow-up ↓ Day 7 Final message ``` You may discover that the Day 3 message has a much higher failure rate than the others. Without reporting, you may only know: > "The sequence isn't working." With reporting, you can identify which part needs investigation. ## What should you monitor? Useful sequence metrics can include: * Targeted * Sent * Delivered * Message status * Send time * Subscriber * Response or error information Each metric answers a different question. ### Targeted How many subscribers were selected to receive the message? ### Sent How many messages were attempted or sent? ### Delivered How many were successfully delivered? A lower delivered number than sent means delivery did not complete for every targeted message. ## Open the sequence report Open the Sequence section in ZazzyAgent. Find the sequence campaign you want to inspect. Open its available reporting or performance view. The available report provides delivery information for the selected sequence. Depending on the interface, you may also see message-level or time-based detail. ## Understand the sequence at the message level A useful way to think about reporting is: ```text Sequence ↓ Message 1 ↓ Message 2 ↓ Message 3 ↓ Message 4 ``` Each step can be examined separately. This matters because a sequence may be mostly healthy even when one step has a delivery problem. ## Example Imagine: | Step | Targeted | Sent | Delivered | | --- | --- | --- | --- | | Welcome | 1,000 | 1,000 | 980 | | Product Info | 980 | 975 | 960 | | Follow-up | 960 | 950 | 720 | | Final | 720 | 710 | 690 | The third step deserves investigation. The problem may not be the sequence itself. It may be something specific about that message, timing, eligibility or delivery conditions. ## Use time-based reporting to find patterns Time-based reporting can help you identify whether a problem happens at a particular point. For example: ```text 09:00 → Normal delivery 10:00 → Normal delivery 11:00 → Increased failures 12:00 → Normal delivery ``` A pattern like this is much more useful than simply knowing that some messages failed. ## Find a specific subscriber When troubleshooting an individual customer, use available search tools to locate them in the report. This can help answer: > Was this particular customer targeted? Then: > Was the message sent? Then: > Was it delivered? This creates a much clearer troubleshooting path. ## Targeted but not sent This usually means the customer was selected for the sequence step, but the message did not complete the sending process. Check: * Message configuration * Template requirements * Account status * Error information * Sequence timing ## Sent but not delivered A sent message isn't necessarily a delivered message. Check the message status and any available response or error details. Possible causes can include: * Invalid customer information * Delivery problems * WhatsApp restrictions * Customer blocking * Template-related issues * Temporary platform errors Use the available status information rather than assuming one specific cause. ## Delivered but customer did not reply This is not necessarily a delivery problem. The message may have worked exactly as configured. At this point you're looking at customer engagement rather than message delivery. For example: ```text Delivered ↓ No reply ``` is different from: ```text Failed ↓ Not delivered ``` Keep those situations separate. ## Compare sequence steps A sequence should be reviewed as a journey. For example: ```text Day 0 → 98% delivered Day 1 → 97% Day 3 → 75% Day 7 → 72% ``` The drop begins around Day 3. That suggests the investigation should start there. Possible questions: * Did that message require a template? * Did the timing change? * Was the message configuration changed? * Is the audience different? * Are more customers reaching that stage than expected? * Are there message-level errors? ## Use reports for troubleshooting When someone says: > "The sequence isn't sending." Don't immediately rebuild it. Check: ```text Subscriber ↓ Sequence assignment ↓ Targeted ↓ Sent ↓ Delivered ↓ Error / response ``` Each stage narrows down the problem. ## Check error information When a message fails, inspect the available response or error details. An error can tell you whether you need to investigate: * Authentication * Template configuration * Customer eligibility * Delivery * API behavior * Account configuration For broader troubleshooting, see [How to Check Bot Error Logs in ZazzyAgent](https://blog.zazzyagent.com/how-to-check-bot-error-logs-zazzyagent). ## Sequence reporting vs conversation monitoring These serve different purposes. ### Sequence reporting Answers: > What happened to scheduled sequence messages? ### Shared Inbox Answers: > What is happening in the customer's conversation? You may need both. For example: ```text Sequence report ↓ Message delivered ↓ Customer replies ↓ Shared Inbox ↓ Human handles conversation ``` ## Monitor before changing the sequence A common mistake is changing timing or message content whenever a few customers don't respond. First determine whether the issue is: **Delivery** or: **Engagement** Those are different problems. A delivered message with no reply is not automatically a failed automation. ## Example: Lead follow-up Suppose a sequence contains: ```text Message 1 Thanks for your enquiry. Message 2 Would you like pricing? Message 3 Would you like a product demonstration? ``` Reporting may tell you: ```text Message 1 → 1,000 delivered Message 2 → 980 delivered Message 3 → 940 delivered ``` The decreasing count may simply reflect sequence progression and customer eligibility. Don't assume every subscriber should necessarily reach every step. ## Example: Delivery problem Suppose: ```text Message 1 → 1,000 delivered Message 2 → 990 delivered Message 3 → 400 delivered ``` Now the third message deserves closer investigation. Check the message itself, timing and applicable WhatsApp requirements before changing the whole campaign. ## Best practice Create a reporting habit for important sequences. For example: ```text Create sequence ↓ Test ↓ Launch ↓ Check delivery ↓ Identify failures ↓ Investigate ↓ Improve ``` You don't need to change a sequence every time the numbers move. Use reporting to find consistent patterns. ## What a healthy review looks like Ask: ### Is the sequence reaching the intended audience? Check targeted counts. ### Are messages actually being sent? Check sent counts. ### Are messages reaching customers? Check delivery. ### Are failures concentrated in one step? Compare message-level performance. ### Are customers responding? Look at conversation activity separately. This gives you a much more complete picture. ## The key idea Sequence analytics are most useful when you use them diagnostically. Don't look at a report simply to find a large number. Use it to answer: > Where exactly is the customer journey breaking? That question leads you to the right fix much faster. For the complete sequence setup, see [WhatsApp Sequences: How to Create Automated Follow-Ups](https://blog.zazzyagent.com/whatsapp-sequences-guide).