Quantcast

Dear Mr Ford

haightbus.jpgWhile we encourage you to report all immediate commendations, concerns and complaints to Muni directly, we'd also love to hear about them. Venting can be fun, and our clever commenters can frequently provide you with a solution or, at least, some sympathy. Send your good and bad Muni tales our way!

Muni service continues to be a headache for many of us, as SFist Reader Catherine can attest:

We understand that sometimes there are accidents (like how the N recently collided with a car), but can you please, please improve the method of communicating closures to riders at stops along the way?

I take the N from Cole Valley to the Ball Park. Suddenly at the Embarcadero, they told us that the train would only go to Harrison and we’d need to either take the shuttle or the 10 bus. Unfortunately, there was conflicting stories of where to catch the shuttle and a bunch of confused passengers. It would have been great to get this info 2 stops ago, when I could have gotten off at Powell and taken any one of the 4th street buses.

Not being able to discern where to catch the shuttle, I decide to enjoy our rare sunshine and walk. Along the way, I noticed every N stop had a number of very confused riders. Why can’t they have an announcement system that can broadcast to multiple stops?

SFist Reader Kim also has some service concerns, some of which concern lines Mr Ford rides:

Here’s an SF Muni story for you. On May 17, I waited at the transbay terminal for a #6 – Parnassus for 25 minutes from 5:21pm to 5:50pm. A coach was just leaving as I got to the stop so I am expecting the wait for the next coach to be about 10 minutes, after all it is commute hour. The next coach was at the terminal in approximately 10 to 12 minutes, but was only going to Van Ness Ave and not 14th Ave, Masonic and Haight was my destination.

Another coach did arrive at the terminal but that coach was not scheduled to leave for another 10 minutes or so, which it did. Therefore, I waited the 10 minutes or so for this bus to leave, but once this coach made it to Van Ness Ave there was a shift change so we had to wait for a driver change. I notice this happens on the #71 line also, Muni seems to think this is a good idea to do a driver change in the peak of the commute hour at Market and Van Ness Sts?

So, my commute home from work yesterday took approximately one hour and I only had to catch one bus. Does this sound like a pleasant commute to you? If this wasn’t a frequent occurrence I wouldn’t bother writing, but something like this happens once sometimes twice per week.

My next complaint concerns the lack of proper Muni service to the Upper-Haight St neighborhoods. The #7-Haight has been discontinued during non-commute hours, which could almost work if they were scheduled at 6 to 8 minute intervals. But, the morning wait for a #7-Haight is approximately 20 minutes, and the reason I know this is because I see the 7 going inbound while walking down the hill to the Haight and Masonic bus stop.

That means I have time stop for coffee and maybe a breakfast to-go then grab a newspaper at the corner store, make my way to the bus stop just in time to board the same coach I just witnessed going inbound. The upper Haight as well as the lower Haight contents a highly condensed population and most of this population is not very pleasant and are frequently rude to the drivers, I have no affiliation with Muni by the way. Aside, from the typically unpleasant riders the drivers are force to deal with the “street” people who frequently harass the drivers for free rides, and naturally become verbally abusive if the drivers refuse. In the interest of customer service, and the care and well being of your operators’ mental state frequent service in and out of the Haight area would go a long way in relieving everyone’s stress.

Contact the author of this article or email tips@sfist.com with further questions, comments or tips.

Comments [rss]