Slack is where a small team thinks out loud. That is what makes it useful and what makes it exhausting. Every thread is a potential decision. Most of them are not. You cannot tell which is which without reading them, so you read them all, or you stop reading and miss the one that needed you.
Waveloom reads the channels you choose in the background and surfaces the thread that actually needs you. When that thread is a DM, it drafts the reply. The rest stays in Slack, where it belongs.
You pick the scope
Connect Slack and choose what Waveloom watches. Specific channels. Your direct messages. Both. It does not read your whole workspace by default, and it does not need to. #customers, #sales and your DMs is a typical starting point. #random is not.
Threads that resolve themselves never surface
This is the core of it. A question gets asked in #engineering at 09:10. Someone answers at 09:14. Thread done. Waveloom saw it, decided nothing needed you, and moved on. No card, no notification, nothing to dismiss.
Same for the thread where you were mentioned but the mention was "thanks, sorted it". Same for a discussion that is ongoing but does not need your input yet. Waveloom waits for a thread to need you rather than reporting on every thread that mentions you.
If it is not confident, it does nothing. Low confidence is a drop, not a "maybe". Rate caps apply here as they do everywhere else, and a topic that already has a card doesn't get a second one; new messages on it join the existing card's thread.
The thread that needs you
A teammate DMs you because they are blocked on a decision only you can make. A partner DMs you and has been waiting for a day. A customer asks a question in a channel you watch and nobody on the team has the answer. This is what gets a card.
The card has the thread and a one-line "why this matters" written for you. When it is a DM, there is an editable draft reply too; for a channel thread, the card shows you what is waiting and you answer in Slack. The draft comes from the context of the message and what you have told Waveloom.
Reply to a DM, after approval
Reply in Slack is one of the two background actions Waveloom can execute, and it replies to direct messages. It posts the reply in the DM, as you. It does this only after you approve the draft. You can edit it first, or dismiss the card and handle it yourself.
There is no setting that lets it reply on its own. The approval gate is in the code.
Quiet hours
Set quiet hours and Waveloom stops pushing notifications during them. Cards still get created, so the feed is ready when you come back. A thread that needed you at 23:00 is waiting in the morning brief, not in a late-night email.
Everything Waveloom surfaces is still there in Slack, with the reply you approved.