Features
Every message sent through the WhatsApp Business API returns delivery callbacks, and ConneXus stores each transition — sent, delivered, read, failed — against the message record. That gives you real delivery reporting rather than a send count, and it is also the early-warning system for a number in trouble.
Message-level status, account-level health, and business outcomes.
Meta assigns your number a quality rating driven largely by blocks and reports. A downgrade cuts your messaging tier, and a sustained one gets the number restricted. Because a bad campaign can move that rating within hours, quality is monitored on a schedule and surfaced rather than left for you to discover in Business Manager after the damage.
Per-template performance breakdowns — read and click rates for an individual template across campaigns — are not built yet. Delivery status is tracked per message today; the per-template rollup is on the roadmap.
| Status | What it tells you |
|---|---|
| Sent | Accepted by WhatsApp for delivery |
| Delivered | Reached the recipient's device |
| Read | Opened — only if the recipient has read receipts on |
| Failed | Rejected, with a reason such as an invalid number or a closed window |
Read receipts are a recipient-side setting. If a customer has them switched off you will see delivered and never read, even though they read it. Judge campaigns on replies and conversions, not read rate alone.
Blocks and reports from recipients, driven by messaging people who did not opt in, sending too frequently, or sending marketing content under a utility template. Honouring opt-outs is the single most effective protection.
Yes — because orders, invoices and payments share the same contact record as conversations, revenue can be attributed by channel rather than guessed at.
Connect your number through Meta Embedded Signup, keep ownership of your WhatsApp Business Account, and pay Meta directly for messages — we never add a markup.