Xperiencify StrawberrySomeone still has to remove tag from student. It does not have to be you
A companion works the 5 operations your Xperiencify account exposes. It can remove a tag from student and remove a student from course, and every one of those waits on an approval card showing the student before it changes.
Open the student. Check it against something else. Write the change. Move to the next one. That is the Xperiencify afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a student until you approve it.
What it can do is exactly what Xperiencify exposes to an account you authorise and nothing beyond it: 5 operations, no reads and 5 writes. In practice that means it can remove a tag from student, remove a student from course and remove student from all courses, and work across the students and tags.
The Xperiencify API stops at Xperiencify. 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 students or ask you for them?
In the tab.
Xperiencify exposes no read operation to a connected account, so a companion opens Xperiencify in the session you are already signed into and reads the screens you would.
The students are what most of this inventory is about, alongside the tags. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of Xperiencify admin becomes a queue you review.
What happens before it can remove tag from student?
All 5 write operations wait for you.
A companion can remove a tag from student, remove a student from course and remove student from all courses, and each one is staged on an approval card first: you see the student, the field and the new value before it lands in Xperiencify.
Nothing in Xperiencify is sent, changed or deleted on your behalf without that click, and a rejected card leaves the student exactly as it was. The gate is the same one on every surface, described at security.
- Remove Tag From Student
- Remove Student from Course
- Remove Student from all Courses
- Add Tag To Student
- Add Student to Course
Does the student sweep have to be asked for every time?
Yes.
Saved as a routine, the Xperiencify students 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 busywork, the Xperiencify students 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