How to stop tasks getting lost in chat
Most jobs that go missing in a small business were asked for in a chat and never written down anywhere else. One rule and a short daily check fix most of it.
A Tuesday, 4.12pm, in a channel called general. Someone writes “can someone ring the tile supplier about the delay?” Three people react with a thumbs-up. Nobody rings. On Friday the tiles still haven’t arrived, the fitter turns up anyway and loses half a day, and everyone in the channel can scroll back to the message they all saw and point at it as if that proves something.
That’s most of the problem, probably. It’s also why so many owners end up searching for how to stop tasks getting lost in chat. Nobody was lazy. The request just had nowhere to live except a stream of messages that kept moving.
We ran a 12-person business before we built Klusko, and we lost more jobs this way than we’d like to admit. What follows is the method we settled on. Most of it works in any chat app. Some of it is easier in ours, and we’ll say where.
Why a thumbs-up isn’t a yes
A reaction in chat means “I’ve seen this”. People read it as “I’m on it”. In a group of five, the gap between those two is wide enough for a whole job to fall through.
It gets worse as the group grows. With two people in a chat, a request is obviously for the other person. With eight, everyone can reasonably assume it was meant for someone closer to the problem. (Psychologists have a name for this. We just call it Tuesday.)
The who, what, by when rule
Every request that’s meant to get done needs a name, an action and a date before the conversation moves on. Compare two versions of the same message:
“Can someone look at the Hendersons’ invoice?”
“Marta, can you chase the Hendersons’ invoice (the £1,840 one from August) by Friday?”
The first is a thought said out loud. The second is a job. Marta knows it’s hers, knows which invoice, and knows when somebody will ask about it. Everyone else knows they can ignore it, which matters more than it sounds.
The what is the part people skimp on. “Sort the van” could mean book the MOT, clear out the back or find the spare keys. Start it with a verb and make it specific enough that a stranger could tell when it was finished. “Book the Transit in for its MOT before the 14th” passes. “Van stuff” doesn’t.
The by when can be loose. “Before Thursday’s delivery” is fine. “ASAP” doesn’t count, because everyone reads it as a different day.
If you only take one habit from this page, take this one: when a request arrives without a name or a date, the next reply asks for them. “Who’s taking this, and by when?” is a perfectly polite message. After a couple of weeks people start adding the name themselves, mostly so they don’t get asked.
One owner, even when two people do the work
A job with two owners has none. When Dan and Priya both “have” the stock take, each expects the other to start it, and the first one to notice it’s late gets to be annoyed.
So every task gets one owner. Other people can help and even do half the work. The owner is the person who says it’s finished, or says early that it won’t be.
That’s why a task in Klusko has exactly one assignee. We don’t do multiple assignees, and it’s deliberate. If a job really needs two names on it, it’s usually two jobs: Priya counts the stockroom, Dan counts the shop floor, and each has a date. Subtasks handle that well enough.
How to stop tasks getting lost in chat: move the job out
The rule gets a name and a date onto the request. That still isn’t enough, because the message scrolls away. The job has to live somewhere that stays put: a task list, or a whiteboard by the kettle if that’s all you’ve got.
Our rule of thumb is that anything taking more than a couple of minutes, or not happening today, becomes a task. Replying “done” to a quick question is fine. Anything with a date on it leaves the chat.
The person who takes the job writes the task, not the person who asked. That sounds backwards. But the owner is the one who has to know what finished looks like, and writing it down is the moment they find out whether they’ve understood. It takes about thirty seconds.
Then close the loop: reply in the thread with a link to the task. Anyone who finds the original message later can see where the job went, and nobody has to ask whether it happened.
In Klusko this part is short. Tasks and chat are in the same app. You create the task in the right project, mention it in the thread, and the mention becomes a live link to the task. When Marta ticks it off, whoever opens the link sees it’s done. The command bar (Cmd/Ctrl + K) searches tasks and messages together, so “where did we get to with the Hendersons?” has one place to look. The chat page and the tasks page show how both sides work.
What Klusko won’t do is read your messages and create tasks for you. We don’t have automations or AI features, and we aren’t convinced a bot guessing which messages are jobs would beat a person spending thirty seconds deciding.
The five-minute daily sweep
Even with the rule, some requests slip past. Someone asks at 5.55pm on a Friday, someone agrees to something in a direct message, someone says “I’ll look into it” and means it at the time. A short sweep once a day catches most of these.
Pick one person to do it. In a small business that’s often the owner or whoever runs the office, though it can rotate weekly. At the same time each day, they go through the busy channels:
- Start from where they last read. The “new” divider in Klusko marks it; most chat apps have something similar.
- Look for questions that got no reply.
- Look for requests with no name on them.
- Look for “I’ll do it” messages with no task linked underneath.
- For each one, either ask “who’s got this, and by when?” or make the task and link it.
- Check their own mentions last, since those are the ones they can close on the spot.
On a normal day that’s five minutes. On a day when something went wrong it’s ten. If it regularly takes half an hour, too much work is being agreed in chat and too little anywhere else, and a short weekly check-in might help (our weekly team meeting agenda runs to 15 or 20 minutes).
Klusko’s Inbox puts every mention and assignment in one list along with task updates, and chat has separate Mentions and Threads views, so the person sweeping doesn’t have to open every channel. They still have to read, though. We haven’t found a way round that.
Where WhatsApp groups fail
Plenty of small businesses run on a WhatsApp group, and for quick messages it’s hard to beat. Everyone already has it and nobody needs showing how it works.
The trouble starts when the group becomes the task list. A group chat has one dimension, which is time. The job someone posted on Monday morning is under a hundred-odd messages by Wednesday, mixed in with delivery photos and somebody’s lunch order. There’s no owner field or due date. You can’t see what’s still open. Search helps if you remember the exact word someone used.
It also sits on personal phones, next to the family group and the five-a-side chat, so people either mute it or read it at ten at night. When someone leaves the business you take them out of the group, and whatever they’d promised in it stays buried in the scrollback where nobody will look again.
None of that makes WhatsApp bad. It was built for talking to people and it’s good at that. It wasn’t built to track jobs, and asking it to is how the tile supplier never gets rung.
If your team lives on WhatsApp now, the change is smaller than it looks. Keep the habit of messaging, and put the jobs somewhere with names and dates attached. We wrote more about team communication for small businesses with exactly that kind of team in mind.
Getting everyone to stick to it
Rules like this tend to die in week three. Two things keep them alive.
The first, and we think the bigger one, is that the owner or manager follows the rule hardest. If the boss posts “can someone sort the rota” and walks off, everyone learns the rule is for other people.
The second is leaving the old messages alone. Start from today. Trying to rescue six months of half-agreed jobs from the scrollback will eat a whole afternoon, and anything that mattered will come back up on its own.
You can try the rule in whatever you use now. If you’d rather have tasks and chat in one place while you do, Klusko is free during early access, and we’ll give at least 30 days’ notice before anything is charged (pricing has the details). Give it a fortnight either way. By the second Friday you’ll know whether the surprises have stopped.
Questions
Why do tasks get lost in team chat?
Tasks get lost in chat because a message has no owner and no due date, and it scrolls out of sight as soon as the next message arrives. A request like “can someone ring the supplier” collects a few reactions, everyone assumes somebody else took it, and by Thursday it’s forty messages up the channel with nobody’s name on it.
Should we ban task requests in chat?
No. Banning requests in chat rarely works, because chat is where people naturally ask for things. Let requests arrive there and move them out quickly instead: whoever agrees to do the job makes a task with their name and a date on it, then links it back in the thread. The chat stays quick and the job stays visible.
How long does a daily chat sweep take?
For most small teams a daily chat sweep takes about five minutes, maybe ten on a messy day. You read from where you last stopped, look for requests with no name or no date, and either answer them or turn them into tasks. If it regularly takes half an hour, too much work is being agreed in chat.
Tasks and chat in one app
Free for up to 10 people, and free on every plan during early access.