Reach and response
What was sent, what arrived, what failed, who replied and who opted out — by channel, by campaign and over time.
- Delivery and failure rates per channel
- Replies and response rates
- Opt-outs, so consent stays visible
Review delivery, conversations, form completion and payments. Events are captured as they happen, so reporting stays current without an overnight batch.
Real-time
8 412
Delivered
1 137
Replies
624
Forms completed
P74 880
Collected
Illustrative figures.
While a campaign is going out you can see it landing: what was delivered, what failed, who replied and who asked to stop. You do not wait until the end to find out something was wrong.
Explore results by channel, campaign and period to see where your team should follow up.
08:0012:00Now 16:0019:00
Messages today, by hour · illustrative
Events reach your reporting as they happen, so sending progress, replies and failures are visible while the campaign is still running.
Events are captured during the service journey rather than waiting for a nightly reporting cycle.
Look at the records behind a result to understand what happened.
Your own activity, across the channels your customers actually use.
What was sent, what arrived, what failed, who replied and who opted out — by channel, by campaign and over time.
How many conversations started and finished, how long they took, how often a person stepped in, and what customers were asking about.
Compare starts and completions to find the journeys that need improvement.
Successful and failed collections, amounts, and where a payment journey breaks down.
What your messaging actually costs, split by channel and by what generated it.
Which follow-ups ran, which completed, and which needed a person — so routine chasing stays accountable.
Explore reporting across WhatsApp, SMS, web chat and forms.
Choose the measures, periods and filters that answer your team’s questions.
Export results to Excel or CSV for finance and operations.
Form completion by district last month
Group completions by district for the previous month. Compare the totals and completion rate, then review the daily trend.
Illustrative request.
Form completion by district
Completions, daily
Daily completion trend.
Illustrative figures.
Give each report a purpose, an audience and a review date.
Use Excel or CSV exports to bring the numbers into your team’s regular reviews.
Reporting plan across one month · illustrative
Define daily, weekly, monthly or quarterly reporting needs around the decisions your team makes.
Formats your finance and operations teams already work in.
Identify who prepares, reviews and follows up on each report.
Choose the format and recipients for each report.
Put a number and a reason next to an application, a claim or a lead, so your team spends its time on the ones that need it.
Advisory scores give your team a starting point for assessment. A person makes the decision, with flagged cases held for review.
Illustrative workflow.
Set your criteria, thresholds and weights. Moozy applies the rules and returns a score with the reasons behind it.
Apply your team’s written assessment rubric to applications, claims or leads.
Each result includes a score out of 100, a band, the reasons behind it and any flags.
A red flag routes the case to a human. Your officer can agree, override or mark it unsure, and that choice is recorded alongside the score.
Choose the criteria and scoring bands for each service.
While a conversation is happening, Moozy can watch for the things you would want to know about straight away — someone attempting fraud, a scam aimed at your customers, a complaint heading somewhere serious, or wording that carries regulatory risk.
Your team receives the flagged conversation and the evidence behind it.
A signal reaches the right team while the conversation is still open, not in next month’s review.
Your team sees what was said and why it was flagged, and decides what to do.
What counts as worth flagging is set per service, so a health programme and a lender watch for different things.
Your figures are yours alone. What each person can open follows the access you already gave them, so a team that does not handle payments does not see payment data.
Set access and retention around the way your team works.
People see the areas their job covers, and nothing else.
Apply your organisation’s handling and retention rules to downloaded reports.
Review conversation, consent and payment records to see how a service was used.
Tell us the number your team argues about — completion, delivery, collection, cost — and we will show how Moozy reports it.