RRavi Shah
How the catch-up decides what matters
A morning backlog of 180 messages becomes eight lines. What the catch-up looks for, what it leaves out on purpose, and why it never reads a message you couldn't open.
Yesterday we shipped Catch-up across channels: one summary of everything you missed, wherever it happened. People ask us two questions about it. How does it choose what to tell me? And what does it read to do that? This post answers both.
Start from what you can read
The catch-up runs as you. Before anything else, it builds the list of messages you are allowed to open: public channels you follow, private channels you are in, your DMs, threads you can see. Everything else is out before ranking starts. An admin's catch-up does not see more than their own sidebar does.
Four signals, in order
We tried scoring every message with one big model. It was slow, expensive and hard to explain. What works is four plain signals, checked in order, with a small model only for writing the sentences at the end.
- Things that need you. A direct question, a mention, a review request, an urgent message. These always make the summary, at the top.
- Decisions. Messages that close a discussion: “Approved”, “Let's go with B”, a huddle's notes, a thread sent back to the channel.
- Changes to plans. Dates that moved, owners that changed, things that got cancelled. We look for the diff, not the chatter.
- Everything else, weighted by how many people reacted or replied, and capped at a quarter of the lines.
Why eight lines
The length grows with the backlog, but slowly: roughly the base-2 logarithm of the unread count, between two and eight lines. Twenty messages get two or three lines. Six hundred get eight. We tested longer summaries and people stopped reading them, which defeats the point.
| Unread messages | Lines in the summary | Median read time |
|---|---|---|
| 20 | 2–3 | 9 s |
| 80 | 6 | 21 s |
| 180 | 7–8 | 30 s |
| 600 | 8 | 34 s |
Every line has a source
Each line of a catch-up links to the message it came from. Click it and Hum opens the channel at that message, highlighted, with the conversation around it. If a line ever surprises you, you can check it in one click. If we cannot point to a source for a sentence, we do not write the sentence.
{
"line": "Friday's release is on track. One bug left, fixed and approved.",
"sources": ["msg_l2", "msg_l2_r3"],
"signal": "decision",
"channel": "launch"
}What it leaves out on purpose
- Messages you already read on another device.
- Bots that post more than ten times an hour, unless something they posted got a human reply.
- Channels you muted. Muting means muting.
- Anything in a thread you left.
What is next
We are working on a weekly digest for Business workspaces: one catch-up on Monday covering the whole previous week, for people coming back from leave. It will follow the same rules: only what you can read, every line with a source. Follow the changelog to see when it ships.
Worth your 9 minutes?
Ravi Shah · Engineer, Catch-up, Berlin
Tunes what the summary leaves out. Writes about how Hum Labs works for the blog.
Meet the team