🚌 Weekly India Transit Grievance Redressal Audit

Window: 26 September–3 October 2026 (X date-filtered searches; run at 09:00 IST)
Scope: eight agencies; passenger-facing service grievances and visible agency replies only.

Findings at a glance

• 17 distinct complaints; 5 received an agency reply (29%). Follow-up posts within one incident were deduplicated.
• No complaint has a publicly confirmed resolution in the captured threads. Replies, docket numbers, and forwarding are acknowledgments, not proof that service was fixed.
• Most frequent primary category: safety/accessibility (5), followed by route/frequency (4), fare/ticketing (3), delay (2), crowding (1), and staff conduct (1).
• Handle corrections: the scheduled list contains stale handles for MTC, CMRL, DTC and Kerala KSRTC. Searches were expanded to the handles used in recent audits: @MtcChennai, @cmrlofficial, @dtchq_delhi and @keralasrtc. The airport case includes a thread originally tagging legacy @MTC_Chennai, answered by current @MtcChennai.

Agency findings

MTC Chennai — @MtcChennai

Complaints: 2 · Replies: 2 (100%) · Response time: ~16 min on Route 104; airport reply ~1m48s after follow-up (~34m after the initial post).
Categories: delay/frequency (1), safety/access (1).

• Route 104, Ambattur OT: rider reported no bus for 35–40 minutes and recurring peak-hour service gaps/crowding. MTC regretted the inconvenience and said it would review frequency and scheduling. ❌ No public evidence of a fix. Complaint · MTC reply
• Chennai Airport T4–Metro walk: passenger described a dangerous roadside walk and asked for a safer MTC drop point. MTC said it had referred the issue to officials. ❌ No outcome shown. Initial post · Follow-up · MTC reply

CMRL Chennai Metro — @cmrlofficial

Complaints: 2 · Replies: 0 (0%) · Response time: none observed.
Categories: station comfort/ventilation (1), fare/refund (1).

• Rider said air-conditioning at A and E stations and HC Metro was consistently off, leaving underground platforms humid despite raising it with staff. ❌ No CMRL reply found. Post
• Tamil-language post alleges Metro refused to return the author’s money. The transaction and reason for refusal are not clear from the post, so this remains an unverified, underspecified refund grievance. ❌ No reply found. Post

CUMTA Chennai — @cumtaOfficial

Complaints: 0 · Replies: 0 · Response rate: N/A. No passenger complaints found this week.

Chennai One — @Chennai_One

Complaints: 0 · Replies: 0 · Response rate: N/A. No passenger complaints found this week. App feature requests and praise were excluded; an undetailed observation about conductors preferring direct payment did not establish a specific Chennai One failure.

BEST Mumbai — @myBESTBus

Complaints: 5 · Replies: 1 (20%) · Response time: ~7h42m on the one replied-to case.
Categories: route/frequency (3), delay (1), breakdown/maintenance (1).

• Route 252 return bus reportedly runs 10–15 minutes late. ❌ No reply found. Post
• A-533 was shortened; A-517 reportedly appears every two hours despite an app display of 30-minute frequency. ❌ No reply found. Post
• Malad East–Pathanwadi–Santosh Nagar: rider says service is too infrequent, especially at peak hours. BEST replied, “Your request is forwarded to concerned HOD.” ❌ Forwarded, but no action or resolution shown. Complaint · BEST reply
• Passenger asked BEST to explain a bus breakdown at Makka Wadi Junction and any contractor penalty. ❌ No BEST reply found. Post
• A-471: rider says the route was closed after operating at 2–3-hour headways and asks for connectivity to be restored. ❌ No reply found. Thread

BMTC Bengaluru — @BMTC_BENGALURU

Complaints: 6 · Replies: 1 (17%) · Response time: ~27h47m for the docket acknowledgment.
Categories: safety/accessibility (3), fare/staff (1), crowding (1), delay (1).

• Passenger alleges a conductor refused E-Aadhaar/DigiLocker Aadhaar for a women’s free ticket. ❌ No reply found. Post
• Bus KA54F 5182: audio announcements reportedly failed and conductors did not call stops, affecting blind and older passengers. BMTC registered docket BMTC2026015936; no follow-up outcome is visible. ❌ Acknowledged, not resolved. Complaint/thread · Docket reply
• Buses leaving Banashankari depot allegedly blocked traffic and ignored a conflicting green signal. ❌ No reply found. Post
• Route 285M/Yelahanka–Hebbal reportedly overcrowded between 6–8 pm. ❌ No reply found. Post
• V365 departures scheduled for 4:35 and 5:00 reportedly both left at 5:10. ❌ No reply found. Post
• A broad post asks BMTC and KSRTC to address alleged driver seat-belt non-use; the allegation is not independently verified. ❌ No reply found. Post

DTC Delhi — @dtchq_delhi

Complaints: 2 · Replies: 1 (50%) · Response time: ~10m07s.
Categories: staff conduct (1), pass/fare clarity (1).

• Passenger says driver and conductor of bus DL1PD7188 misbehaved and questioned a valid monthly-pass holder. DTC apologized and referred the matter to the depot for investigation; no finding or action is public. ❌ Referred, not resolved. Complaint · DTC reply
• Rider says the ₹50 all-route AC pass was not accepted on Green City buses and asks which buses it covers. ❌ No reply found. Post

KSRTC Kerala — @keralasrtc

Complaints: 0 · Replies: 0 · Response rate: N/A. No passenger complaints found this week on the active handle.

City / system summary

• Most responsive agency: MTC (2/2, 100%; small sample). Least responsive among agencies with complaints: CMRL (0/2).
• City response rates: Chennai 2/4 (50%); Delhi 1/2 (50%); Mumbai 1/5 (20%); Bengaluru 1/6 (17%); Kerala N/A (0 complaints).
• Overall: 17 complaints, 5 visible replies (29%), 0 publicly confirmed resolutions.
• Best response: MTC’s Route 104 reply in ~16 minutes, with a stated frequency review; the promised fix is not confirmed.
• Needs improvement: CMRL—two service grievances and no public reply, including the underground-station ventilation report.
• Open issues: BEST A-517’s reported two-hour gaps despite a 30-minute app display; BMTC’s stop-announcement failure has only a docket number, with no visible corrective action.

Method and limits

X searches were constrained to 26 September–3 October 2026 and focused on direct agency mentions/replies and actionable passenger service failures. Counts are distinct public complaint threads; follow-ups were merged. Suggestions, praise, official announcements and unrelated transit posts were excluded. An agency reply means any visible response, including a generic forwarding or docket; it does not imply resolution. Response intervals are approximate elapsed times decoded from X post IDs. This is an X-visible sample, not a count of all complaints received by the agencies. No hourly scheduler data was used.