Routed
Conversations reaching Mia
163
92 at 07-18 audit → +77%
Info
Reached the program-info stage
112
69% of routed
Commit
Committed to show up live
28
19 at audit · evaluator-confirmed
Leak
Warm leads dropped (unrouted)
17
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 (163 routed conversations · Ninjo funnel steps · % of top · % vs previous)
Contactedrouted & engaged
163
100%
Prequalificationshared goal / pain / experience
146
90% · 90%
Nurturingresource shared / received
145
89% · 99%
Program Infoprogram details & interest
112
69% · 77%
Booking Sharedwebclass link, phone or email captured
40
25% · 36%
Conversion rates (base = the 163 conversations that reached the agent, not the broadcast sends)
Reached program info · "CTR"
69%
112 / 163 routed
reached the program details / link stage
headline
Conversion rate · committed
17%
28 / 163 routed
committed to show up to the webclass live
Info → commit
25%
28 / 112 reached info
of those who reached program info, how many committed
Confirmed outcomes (evaluator-filled boolean properties, label-keyed)
Booking link sent
36
confirmed sends
Show-up committed
28
terminal conversion
WhatsApp opt-in
14
reminder-eligible
Not interested
2
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 | 25 |
| aspiring AI consultant | 12 |
| non-technical beginner | 6 |
| busy professional | 5 |
| mum of two | 2 |
| non-technical mum | 2 |
| Goal shared | Leads |
|---|
| get paid helping businesses with AI | 25 |
| get paid to help businesses with AI | 12 |
| get paid $5K–$10K+/mo helping businesses with AI | 9 |
| learn how to get paid helping businesses with AI | 2 |
| grow | 2 |
| organic growth | 1 |
| Top pain point | Leads |
|---|
| determining what to market/sell with confidence of success | 1 |
| finding clients and doing AI audits/consultations | 1 |
| getting organic growth in a restricted niche | 1 |
| not knowing which AI tools to use, how to prove ROI, or how to set them up | 1 |
| where to find clients willing to pay | 1 |
| not knowing what to offer or where to find clients | 1 |
| Objection raised | Leads |
|---|
| price | 1 |
| space is ridiculously crowded | 1 |
| restricted niche and low traction on Meta | 1 |
| cannot attend live | 1 |
| wants replay/recording | 1 |
| what to offer and where to find clients who will pay | 1 |
Routing leak — 110 unrouted replies (leads who replied but never reached Mia · recovery list)
| First inbound | Count | Status | What it is / action |
|---|
| cowork | 11 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| consultant | 3 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| playbook | 2 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| launch | 1 | Warm · fixable | ManyChat keyword, not a Ninjo trigger → sync it |
| "ah i see" · "bonjour je suis à afrique" · "coworke" | 35 | Warm · free-text | real intent, no keyword — hard to catch |
| yes · aic · grow · live … | 21 | Now routing | registered triggers; residual mostly pre-fix |
| stop · delete my number | 10 | Ignored ✓ | opt-outs, correctly left alone |
| business autoresponders / links | 27 | Noise | other companies' WhatsApp bots, not leads |
What this says
✓
The setter works where it engages. 163 routed → 112 reached program info → 28 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 (~17 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 28 committed leads have no reminder cadence. WF-2 (WhatsApp 3d / 1d / 3h / 15min) converts commitment into attendance.
→
Operators are flying blind on wins. 28 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.