People helping people as they get from here to there

Premium User – you are in control

May 5th, 2017  |  Published in examples

[contentblock id=2 img=gcb.png]

We’re doing our best to keep the data volumes manageable…and will be enhancing our duplicate-checker soon.
A future version of the app will allow you to limit your alerts by
  • message category
  • duration of the underlying issue


Tags: ,

Granular control over your alerts, texts, pushes, e-mails

May 5th, 2017  |  Published in announcements

[contentblock id=2 img=gcb.png]

Fine-grained ability to set your delivery preference as you like!

Tags: ,

Identifing the train makes Alerts even more helpful

February 26th, 2017  |  Published in Feature

Summary: The Participate feature allows you to optionally identify the train affected. That information is then shown as part of the alert (in Recent Alerts, push notifications, and e-mails [Premium feature])

Based on your My Commute settings (Origin, Destination, Primary route), and the time of day, the app queries official schedule data provided by NJT, LIRR and MNR to show you a list of relevant choices (see screenshots below).

More Info: People generally know the station and time of their trains (but not the provider-issued train number). For example, I know the NJT 8:14 AM from Watchung Plaza to NY Penn. That train just-so-happens to be #6214. As 6214 travels toward NY, it is known as

  • 8:17 AM at Walnut Street
  • 8:21 AM at Bay Street
  • Etc

The app now figures all this out…for both the Sender and the Receiver of the Alert!


  • The app dynamically adjusts the view of the alert based on the Origin of the person reading it.

Therefore, a rider from Bay Street is presented is told that the problem is with “the 8:21 AM from Bay Street to NY Penn [#6214]”.

We do our best to make the app as smart as possible for both the Sender and the Receiver. There are some nuances and exceptions (e.g., not all trains make all stops…so in that case we show the reader the Origin/Destination of the train).


Overall: We love it when our Senders identify the train when sending an alert.  Some final notes:

  • If you don’t see your train in the pick list, then please let us know
  • Senders can write in the train number if they know it
  • Senders should not put any train identify info in the body of the actual alert…because it’s now automatically/consistently added based on the official train number

Here’s another example that shows how cool this is:

Tags: , ,

All riders benefit from all sharers

February 12th, 2017  |  Published in examples

Some alerts are only of interest to riders on the route where it happens. Other alerts are of broader interest. Clever Commute supports this need two ways

  1. Some users (including the Admin [Conductor Josh]) have the ability to direct an alert to a wider audience. These are the so-called Rail Warriors.
  2. Clever Commmute technolgy uses artificial intelligence and machine learning to automatically determine if a message is of broader interest.

In either situation, these cross-shared posts are labeled in 2 ways (see picture below)

  • The broadcast icon to the left of the route name
  • The word Source followed by the color-coded name of the route on which it originated

This alert was generated by a user who has
Montclair-Boonton Line as their Primary route.



This alert was generated by a user who has
Gladstone-Morristown Line as thier Primary route

Tags: ,

Control the time-of-day and day-of-week for your alerts

December 30th, 2013  |  Published in Feature, premium

This page explains one or more of the dozens of amazing features found in Clever Commute Premium.

One of our most-popular features: Control the days / times that you receive alerts.

Available in…
Set Controls for Free Service? Premium Service?
Time Of Day Yes  Yes
Day of Week No Yes

[Click to enlarge]

Tags: ,