Delivery Reports & Usage Analytics
Know exactly what happened to every message. Track sent, delivered, read, and failed statuses in real time, retry failures in one click, and export everything to CSV.
Every Message, Every Status, One Dashboard
Campaigns, API sends, auto-replies, and bot messages all land in a single delivery report. Statuses update live as WhatsApp confirms delivery and read receipts.
The Usage Report adds the money side: total messages, charges, delivery rate, and breakdowns by API key, instance, message type, and Meta template category.
Built for Marketers, Finance & Developers
What Each Message Status Means
Every message moves through a few stages. Here is what you'll see in your reports and what it tells you.
| Status | What it means | What you should do |
|---|---|---|
| โณ Pending / Queued | The message is waiting its turn to be sent. Large campaigns are sent in a controlled queue to protect your number. | Nothing โ it will go out shortly. |
| ๐ค Sending | Wabiss is handing the message to WhatsApp right now. | Nothing โ this takes a moment. |
| โ Sent | WhatsApp has accepted the message (single grey tick). | Wait for delivery โ the customer's phone may be offline. |
| โโ Delivered | The message reached the customer's phone (double grey tick). | Success. Nothing more needed. |
| ๐ Read | The customer opened the message (double blue tick). Shown only if the customer has read receipts turned on. | Great engagement signal โ consider a follow-up. |
| โ Failed | The message could not be delivered. Common causes: the number isn't on WhatsApp, your number was disconnected, or your balance ran out. | Fix the cause, then use Retry. |
Your Reporting Tools, Explained
Delivery Reports โ "Did my messages arrive?"
The Delivery Reports page lists every message you've sent: campaigns, API messages, chatbot replies, and auto-replies. While messages are being delivered, statuses refresh on their own, so you can watch a campaign progress live.
Narrow the list with filters:
- Status and delivery result (successful or failed)
- Contact group โ see how one campaign audience performed
- Template โ compare how different Meta templates did
- Date range and phone number search
Retrying failed messages
Fix whatever caused the failure first โ reconnect your number or top up your balance โ then click Retry on a single message, or use Retry Failed to resend every failed message that matches your current filters in one go.
Usage Report โ "How much did I send and spend?"
The Usage Report shows four headline numbers: Total Sent, Total Charges, Delivery Rate, and Failed. Below them you'll find breakdowns by API key and by message type, plus a full message log.
- Time periods: Today, Yesterday, This/Last Week, This/Last Month, Last 3 Months, All Time, or a custom range.
- Views: detailed message-by-message logs, or day-wise and month-wise totals.
- Filters: API key, instance, message type (text, template, image, video, document, audio, buttons, list, location), delivery status, Meta template category, and phone number.
Exporting to CSV
Both Delivery Reports and the Usage Report can be downloaded as CSV files that open in Excel or Google Sheets โ perfect for monthly accounting, sharing results with a client, or building your own charts.
Wallet, payments & message activity
The Billing area keeps a running history of every top-up, subscription payment, and per-message deduction from your wallet, so your balance always adds up and you can answer "where did my credits go?" in seconds.
Flow run history
For each chatbot flow you can open a history of every run: whether it succeeded or failed, which steps ran, how long it took, and the exact error message if something went wrong. This makes it easy to find and fix a broken step.
Per-API-key tracking and spending caps
If you give API keys to developers, clients, or different projects, usage is tracked per key. You can also set a cap on a key โ by number of messages or by wallet amount โ so no integration can overspend.
Reporting Questions, Answered
The customer's phone is probably switched off or offline. WhatsApp will deliver it when they come back online, and the status will update automatically.
Customers who turned off read receipts in their WhatsApp privacy settings never send a "read" signal. Their messages will stay at "Delivered" even after they open them.
If a message fails while Wabiss is sending it, the credit or wallet amount for that message is returned to your balance automatically. You can confirm every deduction and refund in your wallet history and Usage Report.
Yes. The REST API offers endpoints for a single message's status, bulk message reports, template reports, and usage statistics. See the Developer API page.
Choose "All Time" in the Usage Report to see your full history, or pick any custom date range.