Two hundred messages read, back as decisions, owners and open questions with a message link on every line. Then written into the doc or ticket where the work actually lives.
A space with eight people and two hundred messages contains one sentence that mattered, usually phrased as "ok let us do the second one". Finding it a month later requires knowing it exists.
A companion reads the whole space, separates the argument from the conclusion, and names who committed to what. Where nobody committed, it says the thread ended without an owner.
01
What does a companion pull out of a busy space?
Decisions, owners and open questions, in that order.
Where nobody committed to anything, it says the thread ended without an owner, which is the most useful line in most weekly digests.
Message links come attached. Nobody trusts a summary of their own chat without being able to check it.
02
Can the decision end up somewhere durable?
A companion works your signed-in browser sessions, so the decision extracted from a space gets written into the doc, the ticket or the project tool where the work lives, with the chat link as evidence.
The write is confirmed before it lands. You read a three-line summary, fix one word, approve. Eight seconds, replacing the note you were going to make later and did not.
03
The space that is really an untracked queue
Most companies have one: a space where another department asks for things, nothing is tracked, and requests scroll away. A companion reads a week of it and returns the requests with no reply, the ones asked twice, and the ones that are the same request from three people.
Space membership, retention and external access are Workspace administration and belong there under their own audit trail. This connection reads spaces and messages, and posts only after your confirmation.
The reachable surface follows Google Chat’s API, which is narrower than what the client shows you. Confirm the object you need is exposed before building a Monday routine on it.
Yes, through a connected Google Chat account. You get decisions, owners and open questions with message links attached, and threads that ended without an owner get named as such.
Yes. Gmail and Google Drive connect to Strawberry directly, and Chat is its own connection. Once it is in place a companion reads spaces, threads and messages and hands back decisions, owners and open questions with the message links attached.
Ask for the decision and its owner, then have it written into the doc or ticket where the work lives. A companion works your signed-in sessions for the destination, and the write is confirmed before it lands.
Yes. Ask for a week of messages with no reply, plus the ones asked twice. Spaces that function as untracked queues generate a surprising amount of both.
It drafts and posts after your confirmation, which is the right speed for anything that goes into a shared space with a name attached.
Google Chat Strawberry