Kollabe
Retrospectives
Planning Poker
Standups
IceBreakers
Pricing
Dashboard

Posts

Daily standups in Slack: why moving the prompt fixes the completion problem

A stylized Slack DM thread on the left with short conversational reply bubbles from a developer holding a coffee, and on the right a clean channel summary card with threaded team replies underneath, modern flat editorial illustration in purple and pink
Kelly Lewandowski

Kelly Lewandowski

Last updated 14/05/20267 min read

Every standup tool I've watched a team adopt eventually loses to the same problem. The product is fine. The form works. The prompts are reasonable. But the tool sits behind a tab nobody has open at 9:14am, and the submissions trickle in at 10:30, or 11, or never. By Wednesday the manager is chasing status in DMs. By Friday the standup tool is a tab the team closes on Monday and reopens when someone reminds them. We hit this pattern on our own product. So we moved the prompt into Slack.

The completion problem nobody fixes

Standup adoption looks great in week one and falls off a cliff by week six. The reason isn't laziness, it's friction. A few flavours of it. Context-switch cost. Your engineer is in a pull request, an IDE, a Linear ticket, and Slack. The standup tool is a fifth tab. The cost of switching apps to type the same thing in a slightly different shape is what gets skipped. The 9am punctuality assumption. Standup tools assume people will open them at the standup time. People don't. They open the tool when they remember, which is usually after lunch. Manager chasing. When submissions are sparse, the manager opens DMs and asks individuals. The standup tool now exists to be ignored, while the actual standup happens one-to-one in private DMs the rest of the team can't see. The fix everyone tries first is more reminders. Email at 9:01, push notification at 9:05, Slackbot at 9:10. Reminders raise the submission rate a little. They don't fix the underlying issue, which is that the prompt is in the wrong place. A developer at a desk with four browser tabs floating around them: a pull request diff, a Linear ticket, a Slack channel, and a half-empty standup form that looks neglected. Modern flat editorial illustration in purple and pink, isometric perspective

What changes when the prompt lives in Slack

We rebuilt the loop so the Kollabe bot DMs you the standup questions at the configured time, and you reply in the thread. Plain English. However you'd answer if a colleague asked you in person. A few things change once the prompt is conversational. No form, no buttons. You type something like "shipped the auth migration last night, today wrapping the rollout, blocked on the design review for the new settings page" and the AI splits that into the right answers under each question. Edit anything in Kollabe. If the parser gets a split wrong, you jump into Kollabe and fix it in five seconds. The Slack reply is the draft. The Kollabe record is canonical. Late submissions don't pollute the channel. When someone submits an hour after the window closes, the late reply appends to the existing thread instead of creating a second top-level post. The channel scroll stays clean. The summary updates in place. The underlying product hasn't changed. The data still lives in Kollabe's standup record, and the AI summary, search, per-group breakdowns, and historical view all stay where they were. What changes is the part everyone bounces off, which is the daily act of opening a separate tool.

How conversational submission actually works

  1. The bot DMs you at the configured time
    Each standup has its own window. When yours opens, the bot drops the questions into your Slack DMs with the team space.
  2. You reply in plain English
    Write naturally in the thread, however you'd answer in person. One reply per question is fine. One long reply that covers everything is also fine.
  3. The AI splits your reply into the right answers
    The model maps your text to the configured questions. "Shipped auth, today rolling out, blocked on design" becomes three structured answers.
  4. Fix anything off in Kollabe
    The standup view in Kollabe shows your submission. Edit, expand, or add media there.
  5. The channel summary lands at the configured time
    Once the window closes, the bot posts the daily summary to your team channel: TL;DR up top, blockers called out, full submissions threaded underneath.

The channel summary that closes the loop

The other half of the change is what shows up in the team channel. Once the standup window closes, the bot posts a single tidy summary: AI-generated TL;DR, who's blocked, who's asking for help, with each person's full submission threaded underneath. A stylized Slack channel feed showing a single summary card with a TL;DR header, three team avatars threaded underneath, and a small purple blocked badge on one. Two manager figures lean in to read calmly. Modern flat editorial illustration in purple and pink Stakeholders who don't want to read every reply read the top of the post. Engineers who want the detail open the thread. The same channel post serves both audiences without anyone having to ask "anyone blocked today?" in a separate message. It also makes cross-team visibility easier. Drop the summary into a wider 
#standups-engineering
channel that PMs and design lurk in. They get context without being invited to a meeting. The summary becomes a passive broadcast instead of an active DM round.

Where it doesn't help

Dedicated standup tools are still right in a few cases. Very small teams with one engineer and one PM don't need any of this. A shared Slack channel and the muscle of habit is fine. Heavily regulated environments where every submission needs a strict audit trail with identity assertions sometimes need the tool to be the source of record, not Slack. You can still use this pattern, you just need to flip the dial toward Kollabe-first edits. Standups that have always worked. If your team is already submitting consistently and the manager isn't DM-chasing, you don't have the problem this solves. Don't fix what works. The honest version of the argument is this: if your standup completion rate is already high, leave it alone. If your standups exist but everyone ignores the tool and the manager is back to DM rounds by Wednesday, the prompt is in the wrong place.

How teams are actually using it

☕Standups without the meeting

Engineers reply async over morning coffee. Managers scan the channel summary for blockers around lunch. No 9am call, blockers still surface.

🌏Distributed teams with no shared morning

The DM lands at the configured time for each team. Nobody gets pinged at 6am because someone in another timezone forgot to think about it.

👀Cross-team visibility

Drop the summary into a wider engineering channel that PMs and design lurk in. They get context without joining the meeting.

🎥Hybrid live-and-async

Pre-submitted answers via Slack, then a 15-minute call where the time is spent on blockers and help-asks, not on roll-call.

Setting it up

If you're already on a Kollabe Premium or Enterprise plan, an org admin installs Slack at the workspace level once. After that, each standup gets its own integration tab:

Open the standup settings and go to the Integrations tab

Pick the channel where the daily summary should land

Flip on DM reminders so the bot prompts each member at standup time

Choose the time the summary posts to the channel

Send a test DM from settings to confirm everyone's Slack identity is matched

That's the whole setup. Microsoft Teams is next on our list, same shape: conversational DM submission, AI-parsed answers, channel summary at the end of the window.

The rule of thumb

Before you pick a standup tool, ask one question: is the prompt going to land in a place my team already opens? If the answer is yes, the rest is implementation detail. If the answer is no, you're going to spend the next six months trying to install a habit that competes with every other tab on your team's screens. You won't win. For most software teams in 2026, the place the team already opens is Slack. So that's where the prompt should be. If you want to try it, Kollabe's Slack standup integration is available now on Premium and Enterprise. For the broader argument about why synchronous standups are fading, see our take on why daily standups are dying.

Yes. The Slack DM matches each user to their Kollabe account by email. If a teammate's Slack and Kollabe emails differ, they can link the accounts manually from the standup view.

Open the standup in Kollabe and edit. The Slack reply is treated as a draft, your edits in Kollabe are canonical. Most teams find the parser gets the split right when the reply mentions each question's topic at least once.

Not currently. Pick the channel where the team actually reads. If you want cross-team visibility, choose a shared channel that adjacent teams already follow.

Late replies append to the existing summary thread rather than creating a new top-level post. The TL;DR updates in place to include the late submission.

No, it's an additional door. The full standup view, AI summaries, comments, reactions, and per-group reporting still live in Kollabe. Slack is the prompt, Kollabe is the record.