Slack and WhatsApp are built for speed, not for memory. A message scrolls past the moment the next one arrives, and there's no built-in way to say "come back to this one." That's exactly why a follow-up asked in either app is so easy to lose.
Habits that help, a little
Before reaching for a tool, a few habits reduce how often this happens:
- Star or pin the message the moment you read a request you can't answer right away. Both apps support this, and it's better than trusting your memory.
- Reply with a placeholder, like "on it, will send by Friday," so the other person knows it's not forgotten, and you've committed to a date.
- Set a specific reminder, not a vague one. "Remind me tomorrow" is easy to snooze forever; "remind me at 4 PM to send the deck" is specific enough to act on.
These help, but they all depend on you noticing the request in the moment and doing something about it manually. On a busy day, in a fast-moving channel, that's exactly when it's most likely to fail.
Why it gets worse across two apps
The real trouble starts when the same relationship spans both apps: a client asks a question on WhatsApp, then follows up over Slack Connect a day later, or a teammate pings you on Slack about something you'd discussed on a call. Nothing connects those threads. Each app only knows about itself, so a promise made in one has no way of showing up in the other.
A follow-up tracker that reads both
This is exactly what Nudge is built to solve. It reads the apps you allow, Slack and WhatsApp included, and notices the shape of a request or a promise as it's written, wherever it happens. Every open loop keeps the exact message it came from, so you never have to guess what "follow up with Rohan" actually meant. And when you actually reply or send the file, the loop closes on its own, no lists to maintain.