MarketRadar
← All ideas IDEA-022 6.0 india monitor-alert-tool emerging

One Telegram bot for two pains: paste PNR → push at every WL→RAC→CNF transition with ML-confidence at T-24h; OR set Tatkal-watch on a (train, date, class) → 3-second polling during the 10:00–10:30 secondary window with deep-link to checkout.

Problem

Indian rail travelers (a) refresh IRCTC PNR-status 5–20 times/day for 7–60 days waiting for waitlist → RAC → CNF transitions, and (b) miss the well-known 10:05–10:15 'secondary release' Tatkal window when failed-payment seats return to inventory. ConfirmTkt has the booking layer but its alert UX is buried; no tool exposes both jobs as one focused Telegram bot.

Audience

Indian IRCTC users (~80M waitlist bookings/yr + ~50M Tatkal bookings/yr) — long-distance multi-passenger families during Diwali/summer/Chhath, students traveling home, and regular metro-corridor commuters (Mumbai-Delhi, Bangalore-Chennai) who book 6–12x/yr.

Reasoning

What we ship

**Core features (MVP — Phase 1: PNR-watch only, low-risk)**

  • PNR-watch: paste a 10-digit PNR into Telegram → 1-hour polling → push on every WL→RAC→CNF transition.
  • ML confidence at T-24h: lightweight gradient-boost model trained on public IRCTC historical data → "Confirmation chance: 78%" 24 hours before departure.
  • Free tier: 1 active PNR-watch at a time (engagement loop). Paid ₹49 per PNR OR ₹99/mo unlimited.
  • Telegram-native UX (no app download required): /start → /track [PNR] → done.
  • Phase 2 (post-launch + IRCTC partnership review): Tatkal-watch via browser-extension workaround on the user's own IRCTC session (not central polling — avoids SB-002 scalper classification).

**Primary user flow**

1. Mumbai-Delhi family heading home for Diwali finds the bot via an r/indianrailways "anyone has a Tatkal bot" thread.

2. `/start` in Telegram → bot suggests /track [PNR] → user pastes PNR → free tier active instantly.

3. After 3 days WL12 → WL5 → push: "🚂 PNR 2516789432 — WL12 → WL5 (40% confirmation chance to T-24h)".

4. On day 4 WL5 → CNF B2/45 → push with upgrade CTA: "✅ CNF B2/45! Buy unlimited at ₹99/mo — track the whole family."

**What it looks like**

  • **Telegram bot first message**: "🚂 One bot, two pains: PNR-watch (WL→CNF push) + Tatkal-window (Phase 2). Free: 1 active PNR. Paid: ₹49/PNR or ₹99/mo unlimited. Razorpay UPI. /track [10-digit PNR] to start."
  • **Dashboard mock**: a single web view — active PNRs as cards (train, date, From-To, current WL/RAC/CNF status, ML confidence bar, last update). No booking button — we only alert; booking stays in the IRCTC app.
  • **Alert format**: "🚂 PNR 2516789432 UPDATE\nTrain: 12951 Mumbai Rajdhani\nDate: 02 Nov 2026\nFrom-To: BCT → NDLS\nStatus: WL5 → CNF B2/45 ✅\nClass: 3A\nML chance @ T-24h was: 78%\n[🔗 Open in IRCTC app]\n_Information only. Not affiliated with IRCTC._"

**MVP build plan (10 days)**

  • Day 1-2: FastAPI + Postgres + Celery beat + Redis on Railway Mumbai, Razorpay UPI per-PNR + subscription.
  • Day 3-4: IRCTC public PNR Status API integration (1-hour polling, smart caching, back-off on 429), WL→RAC→CNF state machine.
  • Day 5: ML WL→CNF confidence model (scikit-learn gradient boost on public historical data), trained once + persisted.
  • Day 6-7: Telegram bot (/start, /track, /upgrade, /pause), Razorpay webhook → unlimited tier toggle.
  • Day 8: Festival-season prompts (Diwali/Chhath/Holi peak window highlights), ML confidence in every push.
  • Day 9: Cloudflare Pages landing (focus: "Telegram-native, broker-agnostic, no IRCTC app required"), DPDP policy with 30-day PNR retention.
  • Day 10: Reddit r/indianrailways pre-launch posts, Telegram channel partnerships (BookingNow, RailFans), live launch with 100 free-tier seeds.

Source signals

  • **SIG-20260425-india-monitor-alert-tool-pnr-confirmation-tracker** — "I built FlightRadar24 for Indian Railways – Major Update: Real-Time Verification & Android App Beta."
  • **SIG-20260425-india-monitor-alert-tool-tatkal-secondary-window-bot** — "Stay logged in and keep refreshing during this secondary window. A confirmed seat might just pop up from a failed transaction."

Reasoning

Two SIGs describe the same end-user — an Indian rail traveler chasing a confirmed seat — but in two different temporal slots (pre-booking Tatkal recovery vs post-booking waitlist→CNF). A bot bundling both has a stronger LTV/CAC because one acquired user becomes a customer for 6–12 trips/year. ConfirmTkt's $50M+ acquisition by Ixigo (2021) validates Indian rail-traveler WTP; RailRadar.in solo dev's active beta-tester recruitment on r/indianrailways is pre-product community validation. White-space: ConfirmTkt has predictions but its alert UX is "spotty" per Reddit; no tool exposes the 10:05–10:15 secondary-release window as a feature; Telegram-native UX beats ConfirmTkt's app for Indian power-users. Stack-fit is excellent — IRCTC API is public with smart caching; one Celery beat schedule with two cadences (1h PNR / 3s Tatkal); ML probability model is a simple gradient boost on public historical data. Build window: 10 days. Legal guard-rail: notification-only, no auto-booking; booking stays in IRCTC app via deep-link.

Quick competitive read

  • **ConfirmTkt (Ixigo-owned)** — booking-first incumbent; alerts buried.
  • **RailRadar.in** — solo dev, pre-product, friend not competitor.
  • **trainman.in** — basic PNR predictions, no push.

White space: a focused Telegram bot doing both PNR push + Tatkal secondary-window does not exist. Competitive pressure ≈ 5–6.

Initial pricing hypothesis

Free: 1 active PNR-watch. Paid: ₹49 per Tatkal-watch event OR ₹99/mo unlimited. Razorpay UPI auto-debit.

Distribution hypothesis

Reddit r/indianrailways native posts in active "anyone has a Tatkal bot" threads; Telegram-partnerships with rail channels (BookingNow, RailFans); festival-season SEO ("Diwali Tatkal trick 2026"); referral-discount viral loop on each successful CNF push.