412 messages since 18:00 yesterday come back as the overnight pricing decision, the deploy blocked for two days, the two mentions that need you and the eleven that do not.
The channels hold real signal: decisions, blockers, commitments, customer smoke. Getting it out means reading everything, and reading everything eats the morning.
A companion reads all ten channels before standup, quotes the decision with a link to the message it was made in, and names who owes what by when. Then it does the part a summarizer cannot: it goes and acts on what it found, in your other tools, in the same pass.
01
What does the 08:15 catch-up contain?
A routine runs before standup. Ten channels, 412 messages since 18:00 yesterday, one screen:
The pricing decision that landed in #revenue overnight, quoted, with a link to the message it was made in.
One deploy blocked on a review nobody has picked up in two days.
Two mentions that need you. Eleven that do not, listed so you can see they were read.
One customer complaint in a channel you do not follow, found by meaning rather than by keyword.
02
How do decisions get out of threads?
The decision was made at 23:40 in a forty-message thread, and by Thursday four people remember it differently.
A companion extracts it, plus who owes what by when, and stages the durable version: a calendar event through the native calendar integration, a row in the tracking sheet, a note in the CRM. Each one is staged for your review, so what enters the tracker is what was agreed rather than what a model inferred at 23:41.
03
Replies and updates, drafted and approved
For the messages that need you, a companion drafts responses with context from the thread and your other tabs: status from the sheet, dates from the calendar, the number from the dashboard.
The weekly team update is assembled the same way, figures gathered from where they live and the draft staged in the channel until you say post. You read it first. Nothing reaches a team channel that you have not seen.
04
Do the work the thread points to
The work the messages point to is not in Slack.
The doc, the dashboard, the CRM record, the customer’s site: all of it lives in tabs.
A companion reads the thread natively and then goes and does the thing, signed in as you, with no webhook plumbing and no per-app tokens. A summarizer tells you the doc needs updating. A companion opens the doc, updates it, and shows you the diff.
Yes. A scheduled routine reads your channels and delivers a digest of decisions, blockers and the mentions that actually need you. You define once what matters.
A companion can send Slack messages through the native integration, with drafts staged for your approval first. Posting to a team channel stops at an approval card.
A companion extracts decisions and commitments from threads and stages them where they survive: calendar events, sheet rows, CRM notes. The thread stays in Slack and the obligations escape it.
Reading and drafting run freely and posting waits for you. Chats are stored on your device rather than on Strawberry’s servers, and your passwords are never exposed to LLM providers.
Yes. The companion drafting your reply checks the sheet, the calendar or the CRM in your other tabs and puts the actual answer in the draft, instead of “let me check” becoming your task.
Slack Strawberry