Teamwork Desk StrawberryThe ticket work, done and queued for one look
A companion works the 5 operations your Teamwork Desk account exposes. It can update a ticket and update a customer, and every one of those waits on an approval card showing the ticket before it changes.
Open the ticket. Check it against something else. Write the change. Move to the next one. That is the Teamwork Desk afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a ticket until you approve it.
What it can do is exactly what Teamwork Desk exposes to an account you authorise and nothing beyond it: 5 operations, no reads and 5 writes. In practice that means it can update a ticket, update a customer and reply a to ticket, and work across the tickets and customers.
The Teamwork Desk API stops at Teamwork Desk. 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.
What does it already know about your customers?
In the tab.
Teamwork Desk exposes no read operation to a connected account, so a companion opens Teamwork Desk in the session you are already signed into and reads the screens you would.
The tickets are what most of this inventory is about, alongside the customers. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of Teamwork Desk admin becomes a queue you review.
Who signs off on a new customer?
All 5 write operations wait for you.
A companion can update a ticket, update a customer and reply a to ticket, and each one is staged on an approval card first: you see the ticket, the field and the new value before it lands in Teamwork Desk.
Nothing in Teamwork Desk is sent, changed or deleted on your behalf without that click, and a rejected card leaves the ticket exactly as it was. The gate is the same one on every surface, described at security.
- Update Ticket
- Update Customer
- Reply To Ticket
- Create Ticket
- Create Customer
Can it update ticket on a schedule?
Yes.
Saved as a routine, the Teamwork Desk tickets 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 ticket queue, the Teamwork Desk tickets 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