What the agent does
The changes the agent makes on its own, the ones it asks about first, and the ones that always go to a person.
SquareJuice works on WordPress sites hosted on WP Engine, the sites you name at setup. The agent handles routine changes end to end, asks before some kinds of work, and sends the rest to a person. Whatever the kind, nothing reaches a live site without your approval.
Prepared without asking
The agent makes these on the staging copy and sends you a preview to approve:
- Text and content edits to pages and posts.
- Menu changes: adding, renaming, moving or removing items.
- Swapping an image for one already in the media library or one sent with the request.
- Small style fixes, such as a color or a spacing that is wrong.
- Fixing a broken link.
- Changing where a form sends its notifications.
- Clearing the site cache.
On a WooCommerce store, style fixes ask first rather than being prepared without asking.
Asks before work
For these the agent sends "Approval needed: Go ahead?" before it starts. Approving prepares the change on staging; a preview follows as usual.
- Plugin updates, theme updates and WordPress core updates.
- Product text on a WooCommerce store: names, descriptions, stock notes.
Updates carry more checks than text edits: the agent confirms the site's core files and plugin state after the update, and a form on the site still submits.
Always goes to a person
The agent does not do these on its own. The request comes back to you as "Needs a person" with a note that says what was asked and what to ask your client.
- Payments, checkout and shipping settings.
- Installing a plugin.
- User accounts and roles.
- DNS and hosting settings.
- Database work.
- Deleting content.
- Bulk changes across many pages or products.
Design work and new features are outside the service.
Questions
A request that asks something rather than changes something ("do we offer local pickup?") is answered by email from what is on the site. Nothing on the site changes, and the receipt says so.
When the agent is unsure
When the agent cannot tell what kind of change the request asks, or is not confident enough in its reading, the request goes to a person rather than being guessed. The same happens when the request could be about more than one of your sites.
Your policy
The Policy page of the dashboard lists each kind of change and how the agent treats it for your agency. An owner can tighten a kind so the agent asks before work. Two rules hold whatever the policy says: every change is built on a staging copy first, and every change waits for a person's approval before it goes live.
Not there yet
Hosts other than WP Engine, requests sent from Slack or GoHighLevel, and the nightly checkout test on stores. Each is included when it ships, at no change to your price.