messaging-performance-analyzer

Messaging performance analyzer Overview Use this skill to turn raw Sent message evidence into a concise diagnosis of what changed, where the funnel leaks, and what to fix first. Anchor every analysis to Sent message IDs , message status , message activities , and webhook events before interpreting carrier, WhatsApp, or RCS provider codes. Sent’s v3 send endpoint accepts a template-based request and returns per-recipient message_id values for asynchronous tracking. Status is retrieved with GET /v3/messages/{id} , and detailed lifecycle evidence is retrieved with GET /v3/messages/{id}/activities . Webhook endpoints support event ingestion, event-type discovery, event history, test delivery, and secret rotation. When to use Use this skill when the user asks why messages failed, why delivery or read rate dropped, whether fallback is working, whether a provider is filtering traffic, or how a campaign performed. Trigger on words such as “MDR,” “delivery report,” “webhook event,” “activities,” “status,” “failed,” “undelivered,” “read rate,” “fallback,” “filtering,” “throttling,” or “carrier reject.” Do not use this skill to register 10DLC, design a Sender Profile, onboard RCS, or author WhatsApp templates. Hand those workflows to the