must-read is your digital communication assistant. He will help your team to collect important messages and links and track who have read it.
You get and send lots of messages every day, some of them are more important some of them just “for your consideration” or “great article, have a look”. Some messages you send in Slack will evolve in Trello cards, Asana tasks, JIRA issues, Zendesk tickets, etc. and they should be treated respectively.
It becomes difficult sometimes to focus on the most important ones and define those that need a reaction. You have to spend much time scrolling channels, answering DM’s and reacting to notifications. It influences personal and team productivity and makes communication not so clear and fluent as you want to.
How can you understand what is a must-read and what you can easily set aside? How not to miss the most important messages and always keep up with your team?
must-read will help every team member to control must-read information workflow no matter how many channels you have and how big your team is.
must-read will help authors of messages to see if colleagues miss them or not. No more “Did you read it guys?” questions needed.
Stop scrolling channels. Start building controllable must-read lists for your team!
Hi guys, you had filling a hole in Slack. It is handling "must-read" messages really well. I'm not sure that what @Ujjwal suggested (a scale from 1 to 10) is a good idea. In my opinion, your bot must remain simple, a message is a "must-read" or not, if there is a scale, there is no value anymore.
@sylvainlaffont Thank you for your feedback! It is crucial for us! We promise to stay simple. We also think that message is a "must-read" or not (1 or 0).
@ujjwal wants that our bot automatically knows whether the message is must-read or not without a user having to tag (mention) any message with must-read bot. And his idea is using machine learning and deep machine learning to do that. And for an initial stage of learning, he suggests that every must-read message author to grade it on scale 1 to 10 how close this message to must read.
We think that it is not that simple with machine learning, deep learning as it may sounds. The most important thing with these technologies is a percent of mistakes that bot will make. It will either create great user experience or will totally break it forcing to correct manually mess that ai bot created.
I. Need. This.
I honestly signed up for the newsletter before I even integrated it with slack for my agency - http://www.thedsmgroup.com/ ... Previously, I was adding things to my pocket account, then sorting it, then assigning tasks in asana to read it if I thought everyone should read it.
GREAT job here guys!
Kelp.app
Must-Read for Slack
Must-Read for Slack