Pinpoint delivery drops by template before they hurt your sender quality.
Go from workspace-wide delivery and latency charts to template, tag, and country breakdowns so your team can fix rejected sends, trace missing notifications, and reconcile WhatsApp spend.
Break delivery down by template, campaign tag, and country.
A healthy workspace average can hide a single paused template or a destination market where messages are failing. Slice accepted, delivered, and failed volume by sender number, template slug, template category, custom send tag, or recipient country, and flag any segment that drops below healthy delivery thresholds.
Trace error spikes and latency down to the individual message.
Compare p50, p95, and p99 processing and delivery latency to tell whether a slowdown sits in your send pipeline or on offline customer handsets. Group failures by error code to catch expired 24-hour service windows, template parameter mismatches, or opted-out recipients, then open the WhatsApp log to inspect a message’s full event timeline and Meta error code.
Track read receipts, inbound replies, and two-part Meta spend.
Follow outbound sends from acceptance through delivery and read timestamps, including when a customer already has the chat open and WhatsApp reports a read receipt without a separate delivery event. Monitor inbound reply volume per business number, and inspect each message’s Bird transaction fee and Meta passthrough charge in your wallet currency across utility, authentication, and marketing sends.