Active follow-ups
604
Overdue by date
416
Due today
0
No usable contact
61
Remaining planned updates / errors
0 / 0
Operating Queue Split
416 schools are overdue by follow-up date. 379 sit in the direct Overdue operating bucket, while contact capture and future-term buckets are separated for clearer action.
Calculated List Coverage
All calculated list additions are complete. 2 Due Today memberships remain report-only and were not removed in this pass.
Staff Operating View
| Priority | NinjaPipe View | Count | What Staff Should Do | Where To Open |
|---|---|---|---|---|
| 1 | SM Follow-Up - Overdue | 416 | Call, WhatsApp, SMS, or visit based on the task/contact instruction; record the outcome and set the next date. | NinjaPipe > Lists > SM Follow-Up - Overdue |
| 2 | SM Follow-Up - Review | 61 | Capture a usable phone, WhatsApp, or email before normal follow-up can proceed. | NinjaPipe > Lists > SM Follow-Up - Review |
| 3 | SM Follow-Up - Decision Maker Needed | 216 | Find or reach the owner, proprietor, headteacher, administrator, or decision maker. | NinjaPipe > Lists > SM Follow-Up - Decision Maker Needed |
| 4 | SM Follow-Up - A Callback | 343 | Execute callback instructions and update the follow-up task outcome. | NinjaPipe > Lists > SM Follow-Up - A Callback |
| 5 | Visit Required | 190 | Plan field visits and log the meeting outcome on the contact/company timeline. | NinjaPipe > Lists > Visit Required |
| 6 | WhatsApp Follow-Up | 375 | Use the contact WhatsApp number and task script; log SMS/WhatsApp activity. | NinjaPipe > Lists > WhatsApp Follow-Up |
| 7 | SM Follow-Up - A+ Closing Now | 10 | Same-day action for schools near subscription or conversion. | NinjaPipe > Lists > SM Follow-Up - A+ Closing Now |
| 8 | SM Follow-Up - Future Term Lock | 13 | Preserve next-term timing; do not chase as urgent today unless task says so. | NinjaPipe > Lists > SM Follow-Up - Future Term Lock |
Daily use: open NinjaPipe, go to Lists or Projects & Tasks, open a school, call/message/visit from the linked contact, log the outcome, and set the next follow-up date.
Calculated List Health
| List | Actual | Expected | Missing | Stale | Status |
|---|---|---|---|---|---|
| SM Follow-Up - Due Today | 2 | 0 | 0 | 2 | 0 missing, 2 stale |
| SM Follow-Up - Overdue | 416 | 416 | 0 | 0 | Aligned |
| SM Follow-Up - Review | 61 | 61 | 0 | 0 | Aligned |
| No Owner Follow-Ups | 0 | 0 | 0 | 0 | Aligned |
| SM Follow-Up - Decision Maker Needed | 216 | 216 | 0 | 0 | Aligned |
| SM Follow-Up - Gatekeeper | 45 | 45 | 0 | 0 | Aligned |
| SM Follow-Up - A Callback | 343 | 343 | 0 | 0 | Aligned |
| SM Follow-Up - A+ Closing Now | 10 | 10 | 0 | 0 | Aligned |
| SM Follow-Up - Future Term Lock | 13 | 13 | 0 | 0 | Aligned |
| WhatsApp Follow-Up | 375 | 375 | 0 | 0 | Aligned |
| SMS Follow-Up | 1 | 1 | 0 | 0 | Aligned |
| Visit Required | 190 | 190 | 0 | 0 | Aligned |
| Completed Follow-Ups | 0 | 0 | 0 | 0 | Aligned |
Lifecycle Lists For Management Review
| List | Companies | Status | Note |
|---|---|---|---|
| Active Clients | 0 | Report-only | client lifecycle truth must come from manual owner action, won deal evidence, subscription evidence, or FeedDash sync |
| Inactive Clients | 0 | Report-only | client lifecycle truth must come from manual owner action, won deal evidence, subscription evidence, or FeedDash sync |
| Trial Schools | 0 | Report-only | client lifecycle truth must come from manual owner action, won deal evidence, subscription evidence, or FeedDash sync |
| Lost Leads | 0 | Report-only | client lifecycle truth must come from manual owner action, won deal evidence, subscription evidence, or FeedDash sync |
| Renewal Watch | 0 | Report-only | client lifecycle truth must come from manual owner action, won deal evidence, subscription evidence, or FeedDash sync |
How Staff See The Workflow In NinjaPipe
Use NinjaPipe Lists for the daily buckets and Projects & Tasks for assigned work. Company pages hold the school context and visible follow-up brief. Contact pages hold phone, WhatsApp, email, and activity logging.
Native automations are intentionally narrow: intake, won onboarding, and lost re-engagement. Daily due/overdue/list maintenance is handled by the controlled runner because native scheduled/task-date triggers are not proven yet.