LoopMessage StrawberryHand the LoopMessage message statuses to a companion
Your LoopMessage, worked while you do something else: 2 reads to go through it, 3 writes to change it, and a card in front of every one of those changes.
Open the message status. Check it against something else. Write the change. Move to the next one. That is the LoopMessage afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a message status until you approve it.
What it can do is exactly what LoopMessage exposes to an account you authorise and nothing beyond it: 5 operations, 2 reads and 3 writes. In practice that means it can send an outbound voice message, send an outbound message and send a reaction, and work across the message statuses, outbound messages and outbound voice messages.
The LoopMessage API stops at LoopMessage. 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.
Does it read the message statuses or ask you for them?
2 of the 5 operations are reads.
Your account, not a guess at it: a companion can show a typing indicator and check message status, and the full list below is the whole list, with nothing inferred from LoopMessage's documentation.
The message statuses are what most of this inventory is about, alongside the outbound messages. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of LoopMessage admin becomes a queue you review.
- Show Typing Indicator
- Check Message Status
What happens before it can send outbound voice message?
All 3 write operations wait for you.
A companion can send an outbound voice message, send an outbound message and send a reaction, and each one is staged on an approval card first: you see the message status, the field and the new value before it lands in LoopMessage.
Nothing in LoopMessage is sent, changed or deleted on your behalf without that click, and a rejected card leaves the message status exactly as it was. The gate is the same one on every surface, described at security.
- Send Outbound Voice Message
- Send Outbound Message
- Send Reaction
Does the message status sweep have to be asked for every time?
Yes.
Saved as a routine, the LoopMessage message statuses 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 operations playbook catalogues the other recurring shapes of the messages, the LoopMessage message statuses 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