KeepLive — WhatsApp ban-risk screen for bot-run businesses

1. One-liner

KeepLive scores your WhatsApp bot’s logs and flags what triggers Meta’s 2026 ban — before your number dies.

2. Trend signal — why now?

On January 15, 2026, Meta’s prohibition on general-purpose AI chatbots on the WhatsApp Business Platform (API) went live for all existing accounts. New API users have been under the rule since October 15, 2025. Meta’s stated reason is blunt: open-ended LLM assistants “generated massive message volumes” without producing template-based billing revenue, so they’re being purged. Allowed: structured, business-scoped bots (support, bookings, order tracking, notifications). Banned: anything that reads as open-domain — a bot that will cheerfully answer “what’s the weather” or freestyle on any topic.

The problem: Meta published criteria but not a self-check. Every BSP and integration vendor has rushed out a blog-post “compliance checklist” (respond.io, Alibaba Cloud, Conferbot, imbrace, gmcsco) — but the underlying message to the customer is always “talk to us / migrate to our platform.” There is no self-serve product that ingests a business’s own bot conversation logs and scores how close that bot is to tripping Meta’s general-purpose classifier. The penalty isn’t a fine — it’s API restriction or account suspension, i.e. losing the number that is the storefront in WhatsApp-dominant markets (165M+ daily users in Brazil, ~84% reach in Malaysia, ubiquitous in India). Appeals take 24–48h with no guaranteed reversal.

This is a platform shift, not a government regulation — and it’s the rare category where the rule is permanent, machine-checkable, and the affected population (every SMB or agency that bolted an LLM onto WhatsApp in 2023–2025) is large and unaware of its exposure.

Provenance:

• Signal 1 (demand): Documented WhatsApp Business account-ban recovery pain — sudden suspension, 24–48h opaque appeals, lost customers — across Omnichat, Trengo, respond.io, ChakraHQ ban-recovery guides — https://blog.omnichat.ai/whatsapp-business-account-block/ — 2026-06
• Signal 2 (feasibility): Meta published explicit, machine-checkable “general-purpose vs structured” criteria + AI-disclosure/fallback requirements (Oct 15 2025 for new users, Jan 15 2026 for all) — https://respond.io/blog/whatsapp-general-purpose-chatbots-ban — 2026-06
• Signal 3 (economic): Entire BSP ecosystem reorganizing around the rule; WhatsApp is the primary sales channel in 165M-daily-user markets; voice/structured-bot category is funded (Bland $22M, Vapi, ElevenLabs partners) — https://www.alibabacloud.com/help/en/chatapp/use-cases/whatsapp-ai-policy-2026-guide — 2026-06 Category: Platform shift

3. The opportunity

The gap is between a published rule and knowing whether you personally violate it. Meta’s enforcement is a black-box classifier run on live traffic. A salon’s bot built on a GPT wrapper in 2024 might answer 92% scoped questions and 8% open-domain drift — and the owner has no idea that 8% is what gets the number killed.

Incumbents here are BSPs and chatbot platforms (respond.io, SleekFlow, Conferbot, Gupshup, Wati, AiSensy). Their “solution” is migrate your whole bot to our managed platform — a weeks-long rip-and-replace with switching cost and lock-in. What they do badly: nobody offers a fast, neutral, read-only diagnostic — “paste your logs / connect your BSP, get a ban-risk score and a fix list in 10 minutes, regardless of which platform you’re on.” A focused AI-first tool can do the one painful thing (classify your actual traffic against Meta’s criteria and tell you exactly which intents to scope or fallback) 10× faster than a platform migration, and stay vendor-neutral so it’s a no-brainer add-on rather than a bet-the-company switch.

4. Target market

• Primary customer: (a) WhatsApp automation agencies / BSP resellers managing 10–200 client bot numbers, and (b) SMBs running a custom LLM-on-WhatsApp bot — clinics, e-commerce stores, real-estate, education, services — in Brazil, India, SEA, MENA, LatAm.
• Why they buy: “I have a bot on my WhatsApp number, the rule is live, and I genuinely don’t know if I’m about to get cut off. Losing this number ends my business.” Agencies buy because one banned client number is a churned client and a support fire.
• Rough TAM reasoning: Millions of businesses use the WhatsApp Business API; a large minority deployed LLM-based bots in the 2023–2025 wave. Even a few hundred thousand at-risk numbers, served via agencies, is a multi-thousand-customer SaaS. Agencies concentrate the demand — ~thousands of WhatsApp automation agencies globally each managing dozens of numbers.
• Why now for them: The deadline already passed (Jan 15, 2026). Enforcement is ongoing right now. This is not “prepare for a future law” — it’s “you may already be in the crosshairs.”

5. Product sketch (MVP)

• Connect or upload: read-only connection to the business’s BSP/inbox (Meta Cloud API, or CSV/JSON export of recent bot conversation logs).
• Ban-risk score (0–100): a single number per WhatsApp number, with a plain-language verdict — “Likely compliant / At risk / High risk of suspension.”
• Violation breakdown: classifies sampled conversations and flags the specific failure modes — open-domain drift, missing AI disclosure in opening message, no human-fallback path, non-template proactive sends, off-policy content.
• Offending-message evidence: shows the exact real messages from your logs that read as general-purpose, so the owner sees the smoking gun.
• Fix kit: generates a compliant opening disclosure, a scoped intent boundary spec, and fallback-routing copy — paste-ready for whatever platform they’re on.
• Continuous monitor: re-scores weekly on fresh logs, alerts when drift creeps back above threshold (bots regress as prompts get edited).
• Agency console: one dashboard across all client numbers, sorted by risk, exportable client-facing PDF report.

6. AI angle — what’s load-bearing

The core engine is an LLM classifier that judges whether a conversation thread is scoped to a business process or open-domain — exactly the distinction Meta’s own classifier makes. This is the product. Remove the AI and you have a static checklist (which is what every BSP blog already gives away free, and which is useless because it can’t tell you whether your traffic violates). The leverage is turning Meta’s vague “general-purpose vs structured” line into a per-message, per-number, evidence-backed score on logs the customer can’t manually review. AI is doing the paralegal-grade reading at scale, not decorating a form.

7. Localization angle (if any)

Global-first by design — the rule is global and WhatsApp’s heaviest SMB markets are Brazil, India, SEA, MENA, LatAm. Localization is a distribution and trust lever, not the product: Portuguese + Brazilian-Real pricing for the 165M-daily-user Brazil market, Hindi/English and ₹ pricing for India, Bahasa for Indonesia. A ₹999/mo or R$99/mo tier reaches wallets a $49 tier can’t, and the classifier must handle multilingual logs (a Brazilian bot’s “drift” is in Portuguese). Vernacular agency partnerships (the people who actually built these bots) are the channel — see section 9.

8. Business model — path to $1M–$5M ARR

• Pricing: SMB self-serve $29/mo per WhatsApp number (monitor + monthly re-score); one-time $99 deep audit for the non-recurring buyer. Agency tier $199–$499/mo for 25–100 numbers with the multi-client console + white-label PDF.
• ACV: ~$350 blended (agency-weighted), ~$350/yr SMB, ~$3–6K/yr agency.
• Rough math to $1M ARR: 250 agencies × ~$330/mo avg = ~$1M ARR. Or a blend of 1,500 SMB numbers ($29) + 150 agencies ($300) ≈ $1.06M.
• Rough math to $5M ARR: ~1,200 agencies, or expand into a broader “WhatsApp policy + deliverability + quality-rating health” suite (template approval risk, messaging-quality-rating monitoring, spam-flag risk) and lift agency ACV to $1K+/mo across 400 agencies.
• Expansion path: start as ban-risk screen → add ongoing quality-rating + template-rejection + spam-report monitoring → become the “WhatsApp account-health” layer agencies run across every client. Land on fear, expand on operations.

9. Go-to-market wedge — first 100 customers

1. Agency directories + LinkedIn: there are public lists of “top WhatsApp Business API providers / automation agencies” per country (the same blogs ranking respond.io et al. list dozens of regional agencies). Scrape ~500 agencies across Brazil/India/SEA, send a personalized Loom: “ran your public demo bot through KeepLive — here’s its ban-risk score.” A scored teardown of their own bot is an irresistible cold open.
2. The fear-keyword crowd: people searching/posting “WhatsApp business account banned,” “API restricted,” “chatbot policy 2026” on r/whatsappbusiness, r/Entrepreneur, Indie Hackers, and BSP community forums are pre-qualified and panicked. Answer with a free instant risk-check link.
3. Free public scanner as lead magnet: a no-login “paste 20 messages, get a risk score” widget. Launch it on Product Hunt + the WhatsApp/no-code automation subreddits; vertical-AI tools with instant comprehension win there. Free scan → paid monitor conversion.
4. BSP co-sell: smaller BSPs that can’t build this themselves will white-label or refer it to reduce their own support load from banned-client tickets.

If I can scrape 500 agencies and convert 5% in 60 days, that’s 25 paying agencies — past ramen.

10. Build complexity — justification

Low. Off-the-shelf: LLM API for the classifier, standard web stack, Meta Cloud API read scopes + CSV ingestion, Stripe + local payment rails. No custom models, no proprietary dataset (the policy criteria are public and the training signal is the customer’s own logs). The only non-trivial work is tuning the classifier to match Meta’s actual enforcement behavior — which requires iterating against real banned/non-banned examples gathered from early users. A solo technical founder ships a credible v1 (upload logs → risk score → fix kit) in 6–8 weeks; the agency console adds another 3–4.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Read-only analysis of the customer’s own data; helping businesses comply with a platform rule.
Ethical — no harm / dark patterns	✅	Pro-compliance, anti-spam. Aligns with Meta’s intent, not against it.
Market exists (evidence above)	✅	Live enforcement deadline, large at-risk population, active fear-search demand.
1–5 person team can build this	✅	Solo-to-pair, ≤3 months.
Launchable with <$50K / ₹40L	✅	LLM + web app; main cost is founder time.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Losing your WhatsApp number = losing the storefront. Hair-on-fire for the exposed; but many at-risk owners don’t yet know they’re exposed, which caps urgency until they’re scared.
Demand evidence	15	11/15	Strong indirect signals (enforcement live, ban-recovery pain documented, BSPs scrambling). No direct competitor product = both opportunity and a “no one’s paying for this exact thing yet” risk.
Build feasibility	15	13/15	Classifier + log ingestion on off-the-shelf APIs. Tuning to Meta’s real enforcement is the only hard part.
Distribution clarity	15	12/15	Agencies concentrate demand; “score your own bot” cold open is concrete; fear-keyword crowd is pre-qualified.
Revenue mechanics	15	11/15	Pricing is reasonable but low ACV on SMB; agency tier carries the math. Retention depends on making it ongoing-monitor, not one-time scare.
Time to first revenue	10	8/10	Deadline-driven urgency + one-time-audit option = revenue in weeks.
Defensibility	10	4/10	Execution + accumulating enforcement-pattern data is the only moat. A BSP could bolt this on; the rule could also evolve. Speed and neutrality are the edge.
Total	100	75/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy — the value is a well-tuned classifier and clean log ingestion; light on sales because the urgency sells itself.

Key assumptions to validate (3–5)

1. Assumption: A meaningful share of WhatsApp-bot businesses are genuinely at risk (open-domain drift), not already compliant. How to test: run KeepLive’s classifier across 50 public/demo bots and real agency client logs; measure % flagged “at risk.” If <20%, the market is smaller than it looks.
2. Assumption: Agencies will pay for a neutral diagnostic rather than absorb it into their own platform. How to test: 20 agency interviews + a paid pilot ($199/mo) with 5 agencies.
3. Assumption: The classifier can predict actual Meta enforcement well enough to be trusted. How to test: correlate KeepLive scores against numbers that actually got restricted/banned in the cohort over 60–90 days.
4. Assumption: Buyers prefer “screen, don’t migrate.” How to test: A/B the cold pitch — neutral diagnostic vs platform switch — and measure reply/close.

Risk flags

1. Platform dependency: Meta can change the policy, build a first-party self-check into the Business Manager, or alter API read scopes — any of which dents the wedge. Mitigate by expanding to broader account-health (quality rating, template rejections) that Meta is less likely to fully self-serve.
2. Market timing / decay: This is partly a one-time scramble. After the initial compliance rush, demand could fall to the trickle of new bot deployments unless the product becomes a recurring monitor people keep paying for.
3. Commoditization: Low defensibility — a funded BSP could ship a “free compliance check” to win logos. First-mover speed, neutrality, and agency relationships are the only buffer.

14. Structured verdict

Score:                  75/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Solo/pair technical founder; bonus if ex-WhatsApp-BSP or messaging-infra background
Time to revenue:        2–6 weeks (one-time audits) ; 4–8 weeks (monitor subscriptions)
Capital to launch:      $5–10K / ₹4–8L (mostly LLM + infra + founder time)
Top 3 assumptions to validate first:
  1. % of real bot traffic that actually trips the general-purpose line — classify 50 live bots
  2. Agencies will pay for a neutral screen vs migrating — 5 paid pilots at $199/mo
  3. KeepLive score predicts real bans — track scored cohort vs actual enforcement for 60–90 days
Kill criteria:
  - Abandon if <20% of audited live bots score "at risk" (problem is rarer than assumed)
  - Abandon if Meta ships a first-party self-check in Business Manager before v1 traction
  - Abandon if <10% of 50 cold agency outreaches show interest after seeing their own bot's score

15. Next step — 1-week validation sprint

• Day 1–2: Build a throwaway classifier prompt against Meta’s published general-purpose criteria. Collect logs/transcripts from 20–30 live WhatsApp bots (own demos, agency contacts, public bot directories).
• Day 3–4: Score them. Hand 10 agency owners a one-page “your bot’s ban-risk” teardown and ask the only question that matters: would you pay $199/mo to keep this monitored across your clients?
• Day 5: Go / no-go. Go if ≥20% of bots score “at risk” AND ≥3 of 10 agencies say yes to a paid pilot. Falsifiable: if bots are mostly compliant or agencies shrug, the scare isn’t a market — kill it.