We built a team chat where conversations can turn directly into tasks
We’ve been working on Toolscase Chats, and the idea came from a problem that probably sounds familiar to anyone working in a team.
A conversation happens in chat.
Someone agrees to do something.
A few hours later, that action item is buried underneath dozens of newer messages.
We wanted communication and the work that comes out of it to stay closer together.
So we built Toolscase Chats as a team communication workspace that combines conversations with tasks and projects.
The platform currently includes:
Direct messages
Group conversations
Public and private channels
Threads
File and image sharing
Voice notes
Polls
Full-text search
Tasks and projects
Role-based access
Guest access
One of the features we particularly wanted was the ability to turn a message into a task instead of copying information from a conversation into a completely separate system.
The challenge has been deciding where communication software should stop.
Adding project-management functionality can make chat more useful, but adding too much can also make a communication tool unnecessarily complicated.
We’re trying to keep the workflow simple: communicate with the team, capture the work that comes out of those conversations, and organize it without constantly switching context.
You can explore it here:
For teams using Slack, Teams, or similar tools: how often do action items from conversations end up getting lost or manually copied into another system?
Interesting. How are you measuring whether it is working?
Thanks for sharing the numbers, that makes it much easier to follow.
Interesting approach. What was the hardest part to get right?
Solid lesson. Which channel has worked best for you so far?
The conversation → task connection is interesting. One thing I’ve noticed is that the task usually survives, but the context behind the conversation that created it can get lost.
How are you handling the “why” behind a task once the conversation moves on?