# A Slack standup bot that already knows what happened

> Standups built from the record, not from memory. How it works, what it looks like in a channel, and what Ray does not do here.

Source: https://heyray.io/use-cases/standups-and-digests

Most standup bots ask everyone what they did. Ray already knows.

A form that asks three questions every morning gets you three answers written from memory, by whoever has time. Ray builds the same update out of the systems the work actually happened in, and asks people only about the parts no tracker can know.

## How it goes now

- The standup prompt arrives at nine and gets answered at eleven, from memory, in one line.
- Half the answers are a paraphrase of a ticket that already says the same thing more accurately.
- The people who reply are the people who always reply, and the quiet ones are the ones worth hearing from.
- Nobody reads yesterday's, and everyone would notice if it stopped.

## How it actually works

1. **Ask for it in a sentence.** No builder, no form designer and no configuration screen. Say what you want posted, where, and when, and Ray sets it up.
2. **Ray builds it from the record.** What moved, what is blocked and what is overdue come from the trackers the work lives in, read fresh at the moment it posts rather than collected from people in advance.
3. **It posts itself, on your schedule.** Any cadence, in the channel you name, in the workspace's timezone. Change it by asking, and cancel it the same way.
4. **People fill the gaps, not the form.** The only thing worth asking a person is what a system cannot see. Everything else is already written down somewhere Ray can read.

## What that looks like in a channel

**"Post a standup in here every weekday at 9."**

Ray schedules it and posts what moved, what is blocked and what is overdue, built from the live trackers rather than from replies.

Tools: Linear, Jira, Asana, ClickUp

**"Make it Tuesdays and Thursdays instead, and add what shipped."**

Ray changes the existing schedule rather than making a second one, and confirms the new shape in the thread.

Tools: GitHub, GitLab, Linear

**"What did we actually get done last week?"**

Ray reads the record and answers, which is the same question the digest answers, asked out of band.

Tools: Jira, Linear, GitHub, Notion

## The tools this touches

Linear, Jira, Asana, ClickUp, GitHub, GitLab, Trello, Notion, Todoist, Google Sheets, Basecamp, Wrike

Every one has its own page saying what Ray reads there and what waits for an approval. The full set is at https://heyray.io/integrations.md

## What Ray does not do here

- Ray does not run a question-and-answer standup where each person is prompted privately and the answers are collected. If a form-style standup is what your team wants, a dedicated standup tool does that better and we say so on the comparison pages.
- A digest is only as good as what the team actually tracks. If work never reaches a tracker, Ray cannot report on it.
- Free workspaces get one scheduled digest. More than one needs Pro.
- Ray posts to channels it is a member of, and reads only those.

## What it costs

Free covers 25 tasks a month plus a one-time 50-task starter grant that never expires. Pro is one flat price for your team size: $49 a month for 1 to 3 people, $99 a month for 4 to 10 people, $199 a month for 11 to 25 people. No seats, and using Ray more never costs more. Failed work is never counted and never billed.

## What people ask first

**Is this a replacement for Geekbot?**

Not exactly, and the honest answer is on our comparison page. Geekbot runs a proper asynchronous standup where each person is asked and the answers are gathered. Ray builds the update from the systems instead of asking. If you want the ritual, Geekbot does it well. If you want the facts, Ray gets them without interrupting anyone.

**Can people still add things by hand?**

Yes. Anything said in the channel is context Ray can use, so the parts no tracker knows still get in.

**How do I change the time?**

Ask. Ray edits the schedule you already have rather than creating a second one, which is the usual way these quietly turn into three digests nobody remembers setting up.

**What timezone does it post in?**

The workspace's, which Ray resolves when the schedule is created rather than assuming your own.

**Will it post if nothing happened?**

Yes, and it will say that nothing moved. A digest that goes quiet when there is bad news is worse than no digest.