NGI
NGI Sale SupportLead Command Center

Sign in

Admins upload data. Viewers can filter and download.

Dashboard
Active admission pipeline
loading…

Railway Zone

College Cluster

Top Areas

Course Demand

Status Breakdown

Source / Platform

Active vs Closed

within current filters

Daily Upload Trend

Course Demand by Cluster

course-wise count per cluster
0 leads
StudentMobileOriginal AreaDetected AreaState ZonePrimary ClusterAlt. OptionsCourseDetection SourceStatusCounsellorBranchPriorityFollow-upCommentUploadedFlags

Upload lead JSON

.json only · replaces shared data

Drop your .json file or click to browse

Uploading replaces the dashboard data for everyone on this link.

.JSON

How it works

  • 1. JSON can be an array of leads, or { "leads": [ ... ] }.
  • 2. Column names are auto-mapped (name, mobile, area, course, status, comment, counsellor, branch…).
  • 3. Area & course are detected from Comment first, then the field; spellings are normalized.
  • 4. Each lead is placed in a Railway Zone → Cluster; flexible Central areas get alternative cluster options.
  • 5. Closed / admitted leads are separated out; the dashboard shows Active by default.
  • 6. Upload publishes to the server so every viewer sees it on refresh.
Recognised keys: name · mobile/phone · area/city · state · course · source/platform · status · comment/remark · counsellor · branch · followup · admission status · crm status · date

Railway zones & college clusters

area → cluster reference

Lead