Routed
Conversations reaching Mia
713
92 at 07-18 audit → +675%
Info
Reached the program-info stage
534
75% of routed
Commit
Committed to show up live
248
19 at audit · evaluator-confirmed
Leak
Warm leads dropped (unrouted)
47
missing ManyChat keywords
How to read this (plain-language glossary)
Routed
Conversations that actually reached Mia. Ninjo calls this "Agent Conversations". The thousands of others are broadcast sends with no reply.
Program info
Lead got as far as the program details / link stage in the chat. The closest thing to a CTR stage.
Committed
Lead said they'll show up live to the webclass. This is our main conversion signal for a show-up funnel.
Conversion rate
A stage count ÷ the routed base. We divide by routed, not by all the broadcast sends, so the % reflects real conversations.
Leak
Leads who replied on WhatsApp but never reached Mia — mostly because they typed a keyword (e.g. "cowork") we haven't wired up yet.
Funnel (713 routed conversations · Ninjo funnel steps · % of top · % vs previous)
Contactedrouted & engaged
713
100%
Prequalificationshared goal / pain / experience
673
94% · 94%
Nurturingresource shared / received
672
94% · 100%
Program Infoprogram details & interest
534
75% · 79%
Booking Sharedwebclass link, phone or email captured
206
29% · 39%
Conversion rates (base = the 713 conversations that reached the agent, not the broadcast sends)
Reached program info · "CTR"
75%
534 / 713 routed
reached the program details / link stage
headline
Conversion rate · committed
35%
248 / 713 routed
committed to show up to the webclass live
Info → commit
46%
248 / 534 reached info
of those who reached program info, how many committed
Confirmed outcomes (evaluator-filled boolean properties, label-keyed)
Booking link sent
187
confirmed sends
Show-up committed
248
terminal conversion
WhatsApp opt-in
47
reminder-eligible
Not interested
28
agent stops
Daily — conversations routed to the agent (the number under each bar is unrouted that day)
Routed to agentunr = unrouted (mostly outbound-only broadcast sends)
Who is showing up & what they want (evaluator segments across routed conversations)
| Buyer persona | Leads |
|---|
| non-technical aspiring AI consultant | 149 |
| aspiring AI consultant | 49 |
| busy professional | 34 |
| non-technical beginner | 8 |
| business owner | 6 |
| mum of two | 5 |
| Goal shared | Leads |
|---|
| get paid to help businesses with AI | 111 |
| get paid helping businesses with AI | 82 |
| learn how to get paid helping businesses with AI | 14 |
| get paid $5K–$10K+/mo helping businesses with AI | 11 |
| get certified and land first client | 4 |
| get certified and land first clients | 3 |
| Top pain point | Leads |
|---|
| no tech background | 3 |
| finding clients | 2 |
| VIP is too expensive | 1 |
| stakeholder indecision and lack of consensus in B2B deals | 1 |
| getting first paying users without organic reach | 1 |
| doesn’t have the money/funds available to join right now | 1 |
| Objection raised | Leads |
|---|
| price | 10 |
| time zone conflict | 7 |
| too expensive | 6 |
| too busy | 3 |
| not the right time | 3 |
| missed the live webclass | 3 |
Routing leak — 311 unrouted replies (leads who replied but never reached Mia · recovery list)
| First inbound | Count | Status | What it is / action |
|---|
| cowork | 31 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| consultant | 11 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| playbook | 3 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| launch | 2 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| "094 598 8589 mahlet
0911512369" · "20k in 12 weeks👏" · "ah i see" | 111 | Warm · free-text | real intent, no keyword — hard to catch |
| yes · aic · grow · live … | 45 | Now routing | registered triggers; residual mostly pre-fix |
| stop · delete my number | 16 | Ignored ✓ | opt-outs, correctly left alone |
| business autoresponders / links | 92 | Noise | other companies' WhatsApp bots, not leads |
What this says
✓
The setter works where it engages. 713 routed → 534 reached program info → 248 committed to show up live, up from 92 routed / 19 committed at the audit. Voice is clean, objections deflect to Friday, no leaks.
!
The keyword sync isn't finished. The yes fix helped, but cowork / consultant / playbook / launch are the real dropped bucket (~47 warm leads) — ManyChat keywords that need syncing as Ninjo triggers. Same fix, wider net.
→
The show-up engine is the next lever. "Can't attend live / wants replay" is the one repeating objection cluster, and 248 committed leads have no reminder cadence. WF-2 (WhatsApp 3d / 1d / 3h / 15min) converts commitment into attendance.
→
Operators are flying blind on wins. 248 leads committed to show up, but there's no notification when it happens — the operator would have to watch DMs. One upsert_custom_notification on show_up_committed closes that.