RCS · Network Telemetry
Total volume vs. Jio-originated vs. terminating-on-Jio. Honours all filters except month.
Where Jio-originated messages land (the only origin with a full breakdown).
Rows = originating operator, columns = terminating network. Shaded by volume; hatched cells are off-net traffic the source does not report.
Total messages landing on each operator (all origins). Non-Jio totals are a lower bound — only the Jio-originated leg is reported off-net.
Share of visible terminating traffic by network.
Stacked volume terminating on each network per month. Honours all filters except month.
First-party vs third-party traffic terminating on each network.
First-party vs third-party total volume over months. Honours all filters except month.
OTP / Promotional / Transactional volume terminating on each network (stacked).
Reliance-Jio-originated traffic by account type × party, stacked across terminating networks.
Baked-in reports plus any files you upload. Uploads are kept in this browser (survive refresh); when the dashboard is hosted with server storage they're also saved on the server for everyone. To bake an upload into the permanent default for all users, use Save as default and redeploy. Duplicates are detected by internal date range.
Termination breakdown per operator for the current filters.
Drag fields between rows, columns and the unused area; click a field to filter its values; pick an aggregation (sum, count, average, % of total…) and a renderer (table, heatmap, bar). Operates on the full dataset (the terminating operator is a real dimension here). Starts as Origin × Terminates-On — change it however you like.
Generate a written analysis of the data currently in view (respects the filters at the top). Run it against a local model (keeps data on your machine) or the Anthropic API.
⚠ Generating insights sends a compact numeric summary of the in-view data to your chosen provider. The local option keeps everything on your machine.
python build_data.py.