Microsoft Teams StrawberryAutomate your Microsoft Teams catch-up with an AI agent
A companion reads the channels you were away from and hands back what changed, what is waiting on you, and what closed itself. It posts nothing until you approve the card.
You were out for three hours. The launch channel has forty-one new messages and two of them are yours: QA asking whether the migration still ships Thursday, and the partner team asking for the deck by end of day. Finding those two costs eleven minutes of scrolling.
A companion reads all forty-one and comes back with the two. Then it drafts both replies, with the ticket, the deploy log and last week’s pricing change already checked. You approve each send on a card showing the destination and the exact text.
| Job | Copilot in Teams | A Strawberry companion |
|---|---|---|
| Read channel history | Yes | Yes. Fifty messages a page, cursor for older |
| Posting a message | Sends when asked | Stops on an approval card every time |
| Answer a thread from the ticket and the deploy log | Inside Microsoft 365 content | Reads both in the accounts you are signed into |
| Run the catch-up on a schedule | You open Teams and ask | A routine that reports what is waiting on you |
| Carry what you decided into next week | Session by session | Memory the companion keeps between runs |
Catch up on Teams in one minute
A companion reads back through the channels you name, sender and timestamp attached, and returns three lists rather than a summary blob: what changed, what is waiting on you, and what closed itself while you were out. The third list is where the time goes. A thread that ended in "never mind, fixed it" costs you forty seconds today and zero tomorrow.
Ask for it in the shape you think in:
- "Read the launch channel since I left and tell me which threads are waiting on me."
- "Draft a reply to QA confirming Thursday, and tell me what I am promising before you post it."
What can a companion read in Teams?
Channel messages, fifty at a time with a cursor for older pages.
Your chats are listed by topic, type and last activity, and a companion can send into one. The messages inside stay in Teams, so your direct conversations are private from it by construction.
Two shapes worth knowing. You point a companion at named channels rather than asking it to hunt a phrase across the whole tenant, and a channel post lands as a new message rather than threaded under message twelve.
Why does every post wait for a click?
Sending to a channel, sending to a chat and creating a chat are actions Strawberry treats as consequential. The browser stops and shows you a card with the exact destination and the exact body. You approve once, for the session, always, or never, and the choice is remembered per tool.
There is no fan-out either. One message is one card, so "post this to thirty channels" is thirty approvals, which is the right amount of friction for something everyone will read.
Answer a thread that needs four other systems
The QA question about Thursday depends on a ticket, a deploy log and a customer email. The partner asking for the deck needs the version that reflects last week's pricing change. A companion opens those tabs in the accounts you are signed into and drafts a reply that already contains the answer, which is operations work with the research done first.
Copilot, as of this writing, works from inside the tenant on meeting recap and chat content, under the admin controls your organisation already runs across Microsoft 365. A companion reads the four systems around the thread and writes the reply that needs all of them to be right.
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