How to Run Async Standups With Geekbot in Slack

November 12, 2026

Geekbot sends each teammate a direct message with your standup questions at a fixed time, collects the answers, and posts one digest to a channel. Setup takes about ten minutes for a five-person team.

The reason to do it: a 15-minute synchronous standup across four time zones costs most people a meeting slot and half an hour of context switching. A text digest costs three minutes of typing and is searchable later.

What is Geekbot and how does it work?

Geekbot is a Slack app (it also supports Microsoft Teams) that runs scheduled check-ins. Each participant gets a DM, answers at their own pace, and the bot compiles the responses into a threaded report.

Core behaviour:

  • Per-user scheduling windows, so each person gets the DM at 9am their local time.
  • Answers posted to a channel as a single digest with per-person threads.
  • Reminders for people who do not answer by the cutoff.
  • Optional anonymity for sensitive check-ins.
  • Reporting over time, including participation and blocker frequency.

Free plans cover a limited number of participants and active standups; paid plans are per active participant per month.

How do you set up a standup step by step?

  1. Install Geekbot from the Slack app directory and authorise it for your workspace.
  2. Create a new standup and name it after the channel it reports to.
  3. Add participants one by one rather than selecting the whole channel. People who did not agree to a daily DM will mute the bot, and muted participants still count on paid plans.
  4. Set the report channel.
  5. Choose scheduling: per-user local time or one fixed time for the whole team.
  6. Write the questions. Defaults are usually fine for the first week; revisit after.
  7. Set a reminder cutoff.
  8. Run it for a week before judging.

Step three is the one that saves money and goodwill. Start with volunteers.

What questions actually work?

The classic three (yesterday, today, blockers) are fine for co-located teams. For distributed teams they produce flat, forgettable updates.

Better patterns:

  • Two questions, not three. “What is the one thing you will finish today?” and “Anything blocking you?” Half the noise disappears.
  • Ask for decisions, not activity. “Anything you need a decision on?” surfaces more useful replies than “what are you working on.”
  • Add a cadence selector for weekly reports. Different questions for Monday and Friday keep people from pattern-matching their answers.
  • Number answers where possible. “Blocked on review for 2 days” is scannable; “waiting a while” is not.

Change questions with notice. Silent question changes produce a week of confused answers.

How do you handle time zones properly?

Per-user local time is the right default. Each person answers at the start of their own working day, so blocking issues surface roughly in the order people start work.

Two practical rules:

  • Set the digest cutoff 90 minutes after the latest member’s DM, so the report lands before the team’s overlap window.
  • For teams spanning more than 10 hours, split into two standups by region and cross-post only blockers. One global digest at a fixed time means someone always answers at 6am.

When does async standup fail?

When nobody reads it. A digest that accumulates unread in a channel is worse than no standup, because people assume coordination is happening.

Fix: assign one owner who reads the digest and replies to blockers daily. Without that person, the tool is a notification generator.

It also fails for teams of three or fewer. A quick message in a shared channel does the same job with less machinery.

What are the limits worth knowing?

The free plan caps participants and active standups. Reporting history is limited on lower tiers, and some integrations (Jira sync, custom reporting) need paid seats.

The DM-only interface is also a limit: people who prefer a web form or email will be slower to adopt. Adoption is the main risk, not features.

Quick Summary

  • Geekbot runs scheduled Slack DMs, then posts a digest with per-person threads.
  • Set per-user local scheduling and a cutoff 90 minutes after the latest DM.
  • Two sharp questions beat the classic three; ask about decisions, not activity.
  • A named digest owner is what keeps the ritual alive past week three.
  • Free tier caps participants and standups; reporting history is limited.
Tags: