« seattle suburbs: the silence of sundays | Main | willingness to pay for transit improvements »

03/10/2010

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83454714d69e201310f86ccd5970c

Listed below are links to weblogs that reference new media and transit complaints:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Jennifer

We actually encourage our riders to tweet us at @STLMetro if they have something to say. We can follow up with them and have a pretty substantive exchange, right out there where the whole world can see it (Transparency!) via (on their end, usually) mobile device. I think it's helping us improve our image with customers because it's responsive in a very public way.

Yes, more substantive issues should be dealt with more substantively sometimes; but Twitter is a quick way to get a quick answer or alert us to a problem so we can get right on it.

I agree that the #TransitFail tag doesn't help much; for one thing, it doesn't identify the specific agency. Even using "#MetroLink" or "#Metro" doesn't help us because there are several systems with that name, though we do keep an eye on those tags, too. But you're more likely to get a response using our actual handle.

EngineerScotty

What we need is a way (via Twitter) to tell the driver of your bus that the next stop is yours, so you don't have to reach up and pull the cord... :)

Aaron Antrim

I think SF BART does the best job at engaging social media networks. They see Twitter as a way of extending and enhancing the social experience and world of transit (http://tinyurl.com/yelunxa).

The SF BART page about their Twitter feed recommends that complaints are submitted by email form (http://www.bart.gov/news/twitter/index.aspx), not Twitter.

A better open space for collecting, displaying, and responding to rider feedback is something like GetSatisfaction.com. Feedback submissions are as questions, ideas, complaints, or compliments, and are organized by agency or company. Responses are threaded, and public. Should the agency choose to participate, agency responses can come from an "Official rep." I think GetSatisfaction.com and similar sites like Uservoice.com, could be used well for community engagement in planning and transit.

Here's my blog post on GetSatisfaction.com for transit: http://www.trilliumtransit.com/blog/2008/12/02/rider-powered-customer-service-for-transit/

You can see GetSatisfaction.com in action for a small transit agency in Humboldt County, California, here: http://getsatisfaction.com/humboldttransit/

I like to highlight this example of passengers helping passengers by answering their questions: http://getsatisfaction.com/humboldttransit/topics/dogs_on_the_bus

EngineerScotty

A common mistake that many people make, including myself from time to time (see prior comment), is confusing Twitter with text messaging. A transit agency might respond to text messages, but the destination for such messages need not be a Twitter account--many conversations are better conducted in private. (By the same token, if you call 'em up on the phone--the old fashioned way--they're not likely to post a recording of the call on the Internet somewhere).

But the larger point is a valid one--and in contexts larger than transit. Complaints for the purpose of achieving satisfaction, and complaints for the purpose of complaining, are generally take different forums and are intended for different audiences.

M1EK

Playing devil's advocate, it appears to many frustrated riders of bad transit (such as city buses or poorly maintained older rail lines) that any input they gave in private, directly, would be ignored; while the tweet may at least have some impact in aggregate via embarassment.

Or, as a cautionary tale to others. The goal might NOT be "improve your service" so much as it is "hey, everybody, don't make the mistake I made and rely on this bus being on time".

Alon Levy

I wish this feature had been available a few weeks ago, when my girlfriend showed up at Penn Station around 2:50 am for a 3:10 train, only to be told it had left at 2:40. (The next train was an Acela at 6:22; it got her to Providence for an interview in time, but she missed the breakfast and lab tour.)

EngineerScotty

Gads.

Its one thing for a frequent-service city bus to be ahead of schedule... but scheduled long-distance services ought not be departing early--or if there is an early-departure window, it ought to be well-publicized.

And with long-distance rail; one of its touted advantages is far faster checkin procedures and formalities than the bus with wings. If you need to get to the train station an hour early in order to be sure of catching the train... rail loses an important selling point over air travel.

Daniel

Apart from the lack of detail prevalent on Twitter, I don't see the point of everyone using a hashtag like #TransitFail. Far better to adopt a particular hashtag for your area, eg the name of the local operator, if you're going to stand any chance of them noticing it.

In Melbourne, common ones are #MetroTrains and #Myki (the new ticket system), both of which are (sometimes) reviewed by the organisations involved. Adding #TransitFail is just another 12 characters wasted which could have been used to more specifically describe what the problem was.

Angusgmelb

I agree with Daniel. I'm also getting pretty sick of the word "fail", both in hashtags and everywhere else on the internet. It's especially unhelpful in a context like public transport, where small failures are part of life.

EngineerScotty

Perhaps transit agencies ought to ignore #TransitFail, and only pay attention to #TransitEpicFail. :)

But the use of "fail" as a noun is an interesting linguistic phenomenon, I'll give you that. Especially since this particular usage seems to derive from poorly-translated Japanese video games...

Barbchamberlain

Found this very interesting--I'm a heavy user of Twitter.

The use of Twitter I'd really like to see transit adopt is to provide info on anything that's affecting service right now, including retweets from people who are reporting something (with specifics enough to be helpful as noted above).

It's that real-time quality that gives it value, and the crowd-sourcing can provide far more info than transit staff alone ever could (with the caveat that it's only as good as what people tell you, but Twitter users know that).

As a parallel, Washington State Dept of Transportation @wsdot provides updates on clogged or closed highways so you can choose an alternate route, they tweet links to road cams, they provide information on things you may have wondered about. GREAT use of the tool.

For customer service, I'd also love to see a Twitter version of the trip planner info I can get by either calling or going to that function on spokanetransit.com. If I could ask when the next #45 will go past 3rd and Sherman and get a speedy answer that would be great. (I can call and ask this so they have the staff--it's just another medium).

For me, Twitter lends itself to this customer service use because the answer is visible to all users and there may be others who are interested in any given question. You get wider information dispersion than a 1-to-1 phone or email exchange.

While the #fail tag isn't much use unless you know which system and what the issue was, I'd still say that any public agency should be monitoring sentiment to whatever extent you can. If your stakeholders are really mad, you need to know.

If we're going to hashtag ourselves to death, how about using #transitWIN whenever your local system works great, gets you there on time, and so forth? People remember to complain--they forget to thank.

@BarbChamberlain

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Blog Widget by LinkWithin
My Photo

Coming Events

  • BALTIMORE
    Feb. 7 12:00 - 1:00 PM, Metro Gallery, 1700 N. Charles Street near Penn Station. RSVP to info@buildthetrolley.org
  • CALGARY
    Apr 14 evening. Time/location TBD
  • NEW YORK
    Feb 6, 3-5 PM, CUNY Graduate Center, 365 Fifth. To be sure of a place, register here.
  • SILVER SPRING, MD
    Feb 7, 7:30 PM. Public lecture sponsored by Montgomery County Planning Commission, Park and Planning Headquarters Auditorium, 8787 Georgia Ave., Silver Spring.
  • WASHINGTON
    Feb 9, 12:30-1:30p, National Building Museum. Free, but click here to be assured of a space.

    Feb 9. 6:30-8:30 PM. APTA Headquarters, 1666 K St NW, Suite 1100. See details (and request for reservations) here. Note discounted book offer if you order fast.

Jarrett is now in ...

Stuff You Need to Know

Technophile Blogs

Books I Recommend (Transit and Urbanism)

Blog powered by TypePad