How a request runs

Forward, preview, approve, publish, receipt. Every step and what you see at each one.

A request is one email forwarded to your SquareJuice address. From there the agent works on its own until it needs a person's decision, and nothing reaches a live site without one. This page follows a request end to end.

1. Intake

The email arrives at your SquareJuice address. SquareJuice checks three things before anything else:

• Who sent it. The sender is matched against your roster: your own people, and the client addresses and domains you named for each site. A message whose sender cannot be confirmed (its mail system failed the usual SPF, DKIM or DMARC checks) is held, and you get a note saying so. Nothing is done with a held request until a person at your agency says it is genuine.
• Which site. The sender's domain and the words of the email name the site. If they could name more than one, or none, you get a note headed "Which site?" and nothing is done until you say.
• Secrets. A password that appears in a forwarded email is masked before anything is stored or read by a model.

Attachments, such as an image to swap in, are kept with the request.

2. Classification

The agent reads the request and decides what kind of change it is: text on a page, a menu change, an image swap, a plugin update, a question, or something that always goes to a person. Each kind has a setting in your policy, which you can read on the Policy page of the dashboard:

• Prepared without asking. The agent makes the change on the staging copy and sends a preview.
• Asks before work. The agent sends "Approval needed: Go ahead?" first. Approving prepares the change on staging; a preview follows.
• Sent to a person. The agent does nothing and sends "Needs a person" with a note.

When the agent is not confident it has understood the request, it is sent to a person rather than guessed. A request that is a question is answered in an email, and nothing on the site changes.

3. Work on the staging copy

The change is made on the staging copy of the site, never on live. The agent then runs its checks on the copy: the page loads, the page looks the way it should apart from the change asked for, the change matches the request, and the agent can explain every file and setting it touched. A change that fails its checks is not shown to you as a preview; the agent tries again or sends it to a person.

4. The preview

You receive "Approval needed: Preview ready" with:

• what was asked, in the client's words;
• what the agent changed, in plain words;
• before-and-after screenshots of the page;
• two links: Approve and publish and Request changes.

The same preview appears in the Queue of the dashboard, where an approver can also decide.

Approval links are personal. Each link is tied to the address it was sent to, to that one preview, works once, and stops working after seven days. Replying "approved" by email is recorded but does not approve anything; use the link in the same email or the dashboard. If an approver lost the email, the dashboard can re-send fresh links to the approvers on record, and the earlier links stop working when the new ones arrive.

A preview waits for a decision for a limited time. If nobody decides, the request closes without publishing and you can forward it again.

Request changes

Write what should change and send it back. The staging copy is revised and a new preview follows, up to three times on one request. After that the request comes to a person.

Reject

Nothing is published and the request closes.

5. Publish and the live check

On approval, the agent replays the approved change on the live site, then checks the live page the same way it checked the copy. If the live check fails, the change is rolled back automatically and you are told. See Rollback and recovery.

6. The receipt

When the request finishes, the approvers get a receipt. It records what was asked, what was done, the before-and-after screenshots, the checks that ran, and who approved it and when. The receipt includes a short draft you can forward to your client; sending it is yours. SquareJuice never writes to your client.

Receipts are kept on the Receipts page of the dashboard. The evidence behind them is kept for 400 days and cannot be altered in that time.

The outcomes you will see