Message Delivery and Campaign Reporting

We start by defining what each message type is for. An appointment reminder aims for attendance, an order update aims to reduce support questions, a promotion aims for replies or sales, and a support message aims for resolution. Reporting is judged against these goals. Then we map the data sources. The WhatsApp Business API provides status updates for each message through webhooks: accepted, sent, delivered, read and failed, with error codes for failures. Your API provider’s dashboard, your CRM, your website analytics and your order or booking system supply the rest. We check that webhooks are received and stored reliably; see API integration with websites and CRMs. We build a message log that keeps, for each message, the template, campaign, audience, send time, status history and error code, with phone numbers stored securely and masked in reports. We group failures by cause: numbers not on WhatsApp, recipients who have not accepted the latest terms, frequency caps, template problems, invalid parameters, recipients who blocked the business and temporary platform errors. For each cause we suggest an action, such as cleaning lists, adjusting send timing or revising wording. We track template health: quality ratings, any pauses or reduced limits, and opt-out and block signals after each send; see approved template message setup. We analyse engagement by template, audience segment, time of day and day of week, including replies, quick-reply button taps and link clicks, and we separate human replies from automated ones. For conversations that continue, we connect the thread with the support or sales workflow; see customer support workflows. We connect messages to outcomes by tagging links, using reference codes in replies and matching records in the CRM, to show bookings, payments or leads that followed a campaign. We note when attribution is partial. We also track costs, because conversation-based charges differ by category and country. We calculate cost per delivered message and per outcome from your provider’s billing, keeping the figures separate from any estimate. We present results in three layers: a one-page summary with the headline numbers, three insights and recommended actions; a detail section for each campaign; and an appendix explaining each metric. Reports are delivered after major campaigns and monthly, with alerts for sudden rises in failures or blocks. We suggest tests, such as one change in wording, button, time or segment at a time. We cannot see message content you do not store, cannot fully measure reads for users who disable receipts, and cannot control platform limits, but clear reporting shows where messages stop and what to fix.