Design prototype — proposed guided restore request, replacing a single generic "Request a restore" link. ← back to journey · ← previous step
My sites  ›  wrenfield.example  ›  Get this site working again
sam
Proposed — does not exist today

Get wrenfield.example working again

Production · cp-40112 · This still goes to our team — nothing here restores anything automatically.

What happened?

This is the same information the current "Request a restore" link already asks for in its own description — we're just asking it up front instead of leaving it to free text in a support form.

Before we send this

This site is still "not serving" right now. A backup taken today would capture it in its current, broken state — useful mainly so nothing is lost if the team needs to compare, not as something to restore to.

Take a backup of the site as it is right now

Uses 1 of your 3 self-service backups. Kept until you remove it — there's no expiry on backups you take yourself.

Left open: should this be on by default, optional, or required? Arguments exist for all three — a broken site is exactly the moment you don't want to accidentally lose evidence of, but a customer under pressure to fix things fast may just want to skip it. Shown here as on-by-default and skippable; worth confirming with support/ops before building.

Review and send to our team

A person reviews this before anything is restored — that doesn't change today.

Sitewrenfield.example — Production (cp-40112)
Likely causeA plugin or theme update
Roughly whenThis morning, around 9am AEST
Snapshot firstYes — will take one before sending