People helping people as they get from here to there

examples

Clever Commute Premium – The Cost

May 30th, 2016  |  Published in examples

Our Premium service is a collection of dozens of value-added features.
See the whole story at the Clever Commute Premium service home page.

 

Clever Commute Premium is sold as an in-app purchase via the Apple App Store or Google Play.

It is a subscription product, with a cost of just $3.33 a month (billed annually).

NOTE: There are currently 8 ways to qualify to have the subscription free waived (and therefore get the premium service for free).

Basic vs Premium

May 30th, 2016  |  Published in examples

Our Premium service is a collection of dozens of value-added features.
See the whole story at the Clever Commute Premium service home page.

 

The basic app is free…and is a great tool for any commuter. However, its functionality is limited to providing user-generated alerts on one commuter line…delivered as push notifications.

Below is a high-level comparison of our basic and premium services. Please clock through here to see the complete list of the dozens of amazing  premium features.

Basic

Premium

# of routes you may follow 1 3
# of hours of viewable history 3 Up to 12
Track metrics & predictions No Yes
View a train’s geolocation No Yes (NJT)
Delivery options Push notifications Push notifications
E-mail
Text message
Advertisements in the App Banners None
List of Features Impressive Incredible
Source of Data Crowdsourced Crowdsourced plus 4 additional sources
Control over the timing and flow of data None Extensive (time-of-day, day-of-week, pause/resume etc)
Cost Free $3.33/month

 

Train geolocation….just like that

May 5th, 2016  |  Published in examples


Clever Commute Premium has dozens of amazing features.
This page explains one or more of them...


Open the Departureboard (click on picture to enlarge)

CleverCommuteDepartureboardAM

1, 2, 3, 4 – Clever Commute uses current time and your Origin / Destination from your app Settings to show you the time-sensitive view from  your home station (yes – we reverse it for the trip home)

5 – Real-time ETA from the transit provider

6 – Click on the pin to see the location of this train…

Click on the #6 – geolocation icon

CleverCommuteGeolocationAMExample

 

 

 

<== There it is…on a Google map!

Introducing Clever Commute app version 2.0

January 28th, 2016  |  Published in App, examples

Not yet released…but here are the working notes for what will be included:

The big headline: Clever Commute v 2.0 includes a premium service with a slew of amazing features

The new FREE version also includes all this…and more:

  • New feature: Leaderboard. It currently shows 4 types of rankings.
  • New feature: Departureboard with custom views for your commute
  • New feature: Profile
  • New feature: Settings
  • New feature: Help menu
  • Enhancements to Send An Alert
    • New field: The Issue*
    • New field: Impact * – used to capture the estimated effect of the reported issue
    • New field: Hashtag – Add a descriptive tag to your message
    • New feature: Real-time checking for duplicates
  • Enhancements to Recent Alerts 
    • Streamlined the look / Reduced whitespace
    • New field: The Issue (in bold, in brackets) for each alert
    • New field: Est Impact – The estimated impact of this issue on your commute
    • New option Show Check-Ins  and Show Vents

* NOTE: It is preferred that the user select the proper value.
However, Clever Commute technology will assign a value when user does not populate this field.

“It’s like Twitter for commuters, right?” Well, kind of…

January 5th, 2016  |  Published in admin, examples, ITFeatureWriteUp

There are at least 4 very important differences between Clever Commute and Twitter:
(1) We use a variety of technologies (keywords, semantics, patterns, user history, etc.) to ensure the alerts are actionable and appropriate content regarding the in-process commute.
(2) We enrich each message with
– the category of the problem
– the impact on your commute (in minutes)
– the train route and number (and origin/destination)
– the geolocation of the alerts
(3) We eliminate duplicate messages about the same issue
(4) We deliver all messages in real time

 

Please see our best practices for sending an alert to learn more about what makes a message a good message.

The filters are technology-based, so all messages are subject to the same rigor. There are indeed some false positives. and some false negatives. We do our best to resolve those in real-time.
Our robots are there to help ensure a good experience for our commuters, and also to respect our sponsors and other business partners.

Other notes:

Sending a message? Do this…not that

December 18th, 2015  |  Published in examples

Is commuting tough? You betcha. Can it make you want to scream? Yes. Is Clever Commute the place to release unfiltered quips and snarks? Sorry…no. Let me explain:

Sure, we’re all adults here. But Clever Commute is designed to be a focused, purpose-centric network where people share actionable, real-time info about the in-process commute.

To that end, our proprietary software scans each message for unsuitable content. “Unsuitable content” includes (but is not limited to) profanity, questions, insults, sarcasm.  So here is what happens:

Message which are 100% venting / complaining about the commute will not be sent out to the commuting community. (If you want to see those messages, then check out @CleverVent on Twitter) .

However, it’s sometimes the case that a message contains both content which is helpful…and other content which is not helpful. Our technology will also hold those messages for review. More often than not, they go stale before one of our moderators can override the hold…and the message never sees the light of day.
Please look at the examples below and appreciate that there is virtually no technology which could differentiate between the two types of examples there. All of these messages below were held.

Therefore, in order to be as helpful as possible, please only send info which is constructive and actionable.  (FYI – our best practices)

Examples: These messages are simply venting…as they have virtually zero actionable information. Clever Commute will not release messages such as these

  • Its amazing how NJT increases fares & quality of customer care doesn’t improve. Single deck train can’t support the morning rush.
  • Conductor on the train to–where?–in hiding, lest he be forced to communicate any information
  • What purpose is there sending us to Hoboken when there are zero MTD trains to Dover???
  • b/c I decide 2 avoid the chaos @ terminals, I don’t get the “cross-honor”? NJT s/b happy there’s 1 less person packed in
  • 5:43 got a talking-to over the PA system about not making rude gestures at the conductors when the train arrives late. Yeah.
  • After the past week of delays I think everyone is s little shell shocked 🙂 #buildanothertunnelnow
  • NJT stinks!!! how can anyone trust making an appointment – morning or night.
  • Re: that 7:25 CC post – wonder if Uber was cross honoring

However, these could have been OK…if the sender simply omitted the bolded portion

  • They post the 6:18 on track 1 it’s SRO. Then they post the 5:50 on 10. WTF?
  • 5:50 from NY Penn is running late… Still still here and there is an Adidas bag still unattended. Really people?
  • The bus lane is stuck as usual. Gov Christie, NJT, Port Authority do your jobs AND FIX THIS PROBLEM
  • Train 6616 sitting waiting for space to open up at Hoboken terminal – always sounds like a good idea to divert trains but it never quite works
  • 6:30 to Huntington left 10 minutes late. No explanation. Tkt collector had no clue.
  • 8:41 from Nyc held at Rahway due to police activity hold the entire train for a fair jumper ?????????really ? worth it??
  • 8:51 out of Penn delayed after SEC due to signal problems. would like a beer please.

See your alerts on a map!

October 2nd, 2015  |  Published in examples

We know you want to know “where was the commuter when s/he sent this alert?”

It’s one more cool feature of our free app.

Look for a green pin…and click on it to see the map view.
(green pin means the user sent the message from a properly-configured device)

Newsfeed view After clicking on the green pin
CleverCommuteGeoLocation1 CleverCommuteGeoLocation2

Feb 17 – Metro North Power Issue – Chronology of events

February 17th, 2015  |  Published in examples, MNR

The good news is that the problem was resolved relatively quickly.
The bad news is that this issue pretty much could not have happened at a worse time of day.

Metro North’s area for improvement: Communications. There was a one-hour-and-fifteen-minute stretch of silence from Metro North…at the height of rush hour (5:08 PM to 6:23 PM).
In this window, there were no e-mail alerts sent by Metro North.

The good news: Clever Commuters stepped up and filled the information void.

Here is a color-coded breakdown of how the news flowed during this evening’s incident.
Color key:
Red – Information from Clever Commute 
Blue – Information from Metro North 

[4:39 PM] Hudson, Harlem and New Haven Line Service is temporarily delayed into and out of Grand Central Terminal due to power issues.  As more information becomes available we will notify you as soon as possible.  Please listen for announcements at your station.

[5:08 PM] Hudson, Harlem and New Haven Line Service is currently experiencing delays of 30 to 40 minutes into and out of Grand Central Terminal due to earlier power issues. Please listen for announcements at your station.

[5:14 PM] No northbound trains since 4:30

[5:24 PM] Track numbers are only posted for 2 trains. The rest of New Haven line is standing around waiting for a track number

[5:45 PM] 536 Grand Central to Croton tried to leave at 540 but now stalled 50 yards along platform.

[6:23 PM] Hudson Line Service is currently experiencing delays of up to 25 minutes due to earlier power issues in Grand Central Terminal. Please listen for announcements at your station.

[6:25 PM] 536 Grand Central to Croton took 20 mins to clear Park Ave tunnel…but moving full speed since

[6:27 PM] Harlem Line Service is currently experiencing delays of up to 35 minutes due to earlier power issues in Grand Central Terminal. Please listen for announcements at your station.

[6:31 PM] New Haven Line Service is currently experiencing delays of up to 35 minutes due to earlier power issues in Grand Central Terminal. Please listen for announcements at your station.

 [6:33 PM] 6:13 Stamford to Bridgeport was 19 mins late departing

Tuesday is the new Monday

July 8th, 2014  |  Published in examples, NJT

Here is a color-coded breakdown of how the news flowed during this morning’s incident.

Color key:

Red – Information form Clever Commute (not all entries shown)
Blue – Information from NJ Transit  (e-mail plus web site) 

The incident began at approx 7:59 AM…and was immediately reported by the commuters. The first e-mail from NJ Transit comes approximately 20 minutes later. 
7:59 AM – Power problems. Train stopped.
8:01 AM – Conductor announces Amtrak losing power
8:03 AM – All NE Corridor inbound trains stopped, heard in conductors radio, no explanation given to passengers yet.
8:04 AM – Amtrak voltage problems. All NJT trains are stopped.
8:06 AM – Going to Hoboken (trains to NYP are diverted)
8:16 AM – 8:01 Madison to NYPENN re routed to Hoboken. Conductor reporting all midtown direct trains are going to Hoboken
… (more Clever Commute messages)…

8:20 AM – MidTown Direct Service is diverted to Hoboken. We are cross honoring with NJT bus and PATH
8:25 AM – Northeast Corridor and North Jersey Coast Line service is suspended in both directions, due to Amtrak overhead wire problem
(End. No other communication from NJ Transit)

8:35 AM – Conductor on train stuck at Princeton Jct says trains are moving in front of us. Waiting out turn to move.
8:35 AM – NJT3926 7:45 fr:PJCT now on the move towards NB – supposedly NWK is next stop
8:38 AM – Anecdotal reports of trains at Eliz and Metro moving. Westbound train just came by Metuchen w/o stopping.
8:46 AM – Just board a local train from metuchen. Conductor announced delay into NY, but trains are moving
… (more Clever Commute messages)…

 

Monday came on Tuesday for NJT Riders

July 8th, 2014  |  Published in examples, NJT

Here is a color-coded breakdown of how the news flowed during this morning’s incident.

Color key:
Red – Information form Clever Commute (not all entries shown)
Blue – Information from NJ Transit  (e-mail plus web site) 

The incident began at approx 7:59 AM…and was immediately reported by the commuters. The first e-mail from NJ Transit comes approximately 20 minutes later. 

7:59 AM – Power problems. Train stopped.
8:01 AM – Conductor announces Amtrak losing power
8:03 AM – All NE Corridor inbound trains stopped, heard in conductors radio, no explanation given to passengers yet.
8:04 AM – Amtrak voltage problems. All NJT trains are stopped.
8:06 AM – Going to Hoboken (trains to NYP are diverted)
8:16 AM – 8:01 Madison to NYPENN re routed to Hoboken. Conductor reporting all midtown direct trains are going to Hoboken

8:20 AM – MidTown Direct Service is diverted to Hoboken. We are cross honoring with NJT bus and PATH
8:25 AM – Northeast Corridor and North Jersey Coast Line service is suspended in both directions, due to Amtrak overhead wire problem