Someone still has to send direct message. It does not have to be you
Hand a companion the outcome. It reads the Flock channel messages, does the 2-operation version of the job, and stops for your click on anything that changes a record.
Open the channel message. Check it against something else. Write the change. Move to the next one. That is the Flock afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a channel message until you approve it.
What it can do is exactly what Flock exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can send a direct message and send a channel message, and work across the channel messages and direct messages.
The Flock API stops at Flock. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the channel messages come from?
In the tab.
Flock exposes no read operation to a connected account, so a companion opens Flock in the session you are already signed into and reads the screens you would.
The channel messages are what most of this inventory is about, alongside the direct messages. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Flock admin becomes a queue you review.
Which channel messages wait for your approval?
All 2 write operations wait for you.
A companion can send a direct message and send a channel message, and each one is staged on an approval card first: you see the channel message, the field and the new value before it lands in Flock.
Nothing in Flock is sent, changed or deleted on your behalf without that click, and a rejected card leaves the channel message exactly as it was. The gate is the same one on every surface, described at security.
- Send Direct Message
- Send Channel Message
What does the recurring channel messages pass look like?
Yes.
Saved as a routine, the Flock channel messages pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the Flock channel messages sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents