The Mojo Helpdesk tickets nobody wants to work through
It reads every ticket your Mojo Helpdesk account holds, drafts the changes that follow, and hands you a card for each one before a single ticket moves.
Open the ticket. Check it against something else. Write the change. Move to the next one. That is the Mojo Helpdesk 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 Mojo Helpdesk exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can create an user and create a ticket, and work across the tickets and users.
The Mojo Helpdesk API stops at Mojo Helpdesk. 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 users?
In the tab.
Mojo Helpdesk exposes no read operation to a connected account, so a companion opens Mojo Helpdesk 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 users. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Mojo Helpdesk admin becomes a queue you review.
Who signs off on a new user?
All 2 write operations wait for you.
A companion can create an user and create a 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 Mojo Helpdesk.
Nothing in Mojo Helpdesk 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.
- Create User
- Create Ticket
Can it create user on a schedule?
Yes.
Saved as a routine, the Mojo Helpdesk 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 Mojo Helpdesk 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