People helping people as they get from here to there


In case you want to test out sending a Clever Commute message

June 20th, 2015  |  Published in App, documentation, Ops, techdoc

Here is how to create an alert which will test your account…but will NOT be visible in the app.

  1. Select the Participate menu option
  2. Set (1) What do you want to do to
    Send test message
  3. Ignore (2) What’s happening?
  4. Ignore (3) What’s the impact? 
  5. Ignore (4) Does this relate to a train? 
  6. Set (5) Tell us a bit more to
    I am a commuter doing a verification of my account
    …and press Send.

    Do NOT use the word test in your alert.

Step 7. – Use the Contact feature of the website to let us know you did a test…and we’ll let you know if we got it. 


How to use Clever Commute

July 25th, 2011  |  Published in announcements, community updates, Ops

We continue to grow and grow…so here are some basics about using Clever Commute:

Almost all of our information comes from the commuters. Therefore…it’s key that you each understand how you can each SHARE information with your fellow commuters.

How you SHARE information*

  • Use your e-mail program to send a message
  • Put your entire message in the SUBJECT line (e.g., do NOT use the body of your e-mail)
  • Each train line / bus route / etc has its own “community”.Therefore, for THIS community, you should send it to [see e-mail]
    (please add that address to your “Contacts”)

How you can RECEIVE the information

* Two things to note before you share

  1. If you are new to Clever Commute, please sit back and get the feel of how things work here before you “post” anything.
    FYI – We actually won’t allow you to share for your first 30 days
  2. Over these past 5 years, we’ve learned a few things about how to best harness “the wisdom of the crowds”.
    Here is a blog post with “the top 6 reasons your messages was NOT sent out”

Another great new feature: “Rate this message”

May 10th, 2011  |  Published in admin, announcements, Ops, social

One of the tough things about my job as “Conductor” is actually trying to manage the content & volume of the messages that people send.  Maybe you have been a part of the conversation about:

As you can imagine, sometimes, the answer is it depends. So, in the spirit of crowdsourcing, we are pleased to announce a great new feature: Rate this message. How it works:

At the bottom of every commuter-generated message you get, there will be a new section, as follows:

Was this message helpful?
Report abuse

The blue text above are links. When commuter clicks on their choice, they are taken to a web page which thanks them for casting their vote. That’s it!

A few things to note:

  • Our database records the rankings…and our program safeguards against multiple votes on a given message by the same person.
  • Regarding that last category: sometimes, Clever Commuters break the rules…and we then need to remind them of our Rules of the Road. Even more rare is the situation where true spam (from a non-Clever person) slips through. It’s a huge help if the commuters can help us identify that, too.

As you can imagine, this lays the groundwork for several new features:
1. We can give feedback and coaching to post-ers who are consistently rated “low”
2. We can reward post-ers who are rated “high”
3. We can explore new features like “ALWAYS send me updates from this person” and “NEVER send me updates from that person”
4. Automate the process for handling spam and abusive mails
5. …what else?  I’m sure there is more

“Step 1” was just to get the framework in place. This is “version 1.0″…so I’m sure there are ways to improve it…so send me your feedback.

Thank you for using our “B2B” datafeed product. As an overview of this offering:

April 17th, 2008  |  Published in examples, Ops, techdoc


When an alert is not in compliance with our best practices

January 31st, 2006  |  Published in Ops

If a message violates our best practices:

If it comes from a registered Clever Commute user…

  • our technology changes the category to I just want to vent (and follows the existing “Vent” logic)
  • it will NOT be found in the B2B datafeed

If it comes from a non-user, then it is deleted


Placeholder – Tech Doc on Possible Dupes

January 31st, 2006  |  Published in Ops

This is the Ops/Tech doc which explains “Poss Dupe”