What a great way to start the day: A great story in the national press!
announcements
In the USA Today…today
Looking forward to more media coverage
Looking forward to more media coverage
Clever Commute will be featured on Fox Business Network. Here are the details:
Program: Your Questions, Your MoneyÂ
Date: Saturday, Aug 22
Time: 10:00 to 2:00 EST. I am expected to be on between 1:30 and 2:00
A link to the channel finder
What a day – The Sunday Star Ledger!
What a day – The Sunday Star Ledger!
We are thrilled to share a link to a Clever Commute story from NJ’s largest newspaper – The Star Ledger. And…it’s the Sunday edition!
We are featured prominently on page 1 of the NJ section.
It’s been a great day…with lots and lots of new people signing up. Welcome aboard!
Nice press is nice (MainStreet.com)
Nice press is nice (MainStreet.com)
It was nice of the folks at MainStreet.com to reach out to us and offer to do an article. We are very pleased with the way it came out.
Here is a link to the story
“Too much e-mail”?…Not from us ;)
“Too much e-mail”?…Not from us ;)
A few weeks back, we told you about a new feature that would actively seek to find and eliminate duplicate messages in the Clever Commute system.
We continue to phase it in…but in case you are interested, here is an example from today’s commute (on NJ Transit Northeast Corridor Line – the largest commuter rail line in North America)
6:55 AM
HAMLTN 6:36 to NYP is now 14 minutes late. NJT says 18 minutes due to mech failure. Empty train blew by the station 3 minutes ago.
6:56 AM
646 out of PJ 18 minutes late
As you’d expect…the 6:55 message was sent along to the Clever Commuters…and the 6:56 message was suppressed.
Just one more example of how we are continually working to make Clever Commute better.
How we manage duplicate messages
How we manage duplicate messages
Here is how it works:
If user A tries to Send an alert which is similar to a previous messge from user B” the app will pop-up a message with details of B’s message to expain that they are potentially sending a duplicate.
User A then has 3 choices
- Edit their message…and therefore differentiate it from the one sent by user B
(an then re-send) - Cancel their message…since the one sent by user B suffices
- Send the message as-is
Our intent here is to fully leverage the wisdom of the crowd…while also being sensitive to the amount of data you get.
We certainly don’t mean to frustrate anyone….or fail to share relevant information.
But also want you to understand that it is very difficult for technology to determine true duplicates. Our approach will never be perfect. However, as time goes by, we “tune the dials” to improve the features and richness of this algorithm.