CP26 recovery journey Step 2 of 4 · Client portal proposed

Get lumenpress.example working again

This becomes a support request our team picks up — the same request queue as any other request, with a few extra questions so we can start faster.

Which environment?

Carried over from where you clicked "Get this fixed."

When did you first notice it stopped working?

Doesn't need to be exact — this helps us find the right point to restore to.

What changed right before, if anything?

Plugin or theme updateInstalled or updated through the site

Code or file changeUploaded or edited files directly

Domain or DNS changeMoved a domain, changed records

Not sure / something elseDescribe below

Anything else that would help us (error message, what you were doing, etc.) Which copy should we try first?

My most recent backup — 18 Sep 2026, 7:04 PM Taken by you, 2 days before the site went down

Not sure — let Ayuda work out the best copy Our team will check what's available, including copies you haven't taken yourself

You have 1 of 3 self-service backups used. Take a fresh backup first instead →

Submit request Cancel

What's real vs. proposed here

VerifiedA "Restore a site from backup" request type already exists in the client portal's request form, pre-filled with the site when you arrive from that site's page. Manual backups (up to 3, self-service) already exist and are listed with a timestamp.

Proposed: structured intakeToday this request type is just two free-text fields — Subject and Details. Everything above (when it broke, what changed, which backup) is new: it turns a blank page into a short set of questions so the customer doesn't have to know what to write, and the operator gets a head start.

Proposed: backup pickerSurfacing the customer's own backup list inline, with a way to fall back to "let Ayuda work out the best copy," doesn't exist today — currently the customer would have to separately check the Backups tab and describe what they saw in free text.

AssumptionThat operators want backup selection suggested by the customer rather than always deciding it themselves — flagged for the team to confirm, since backups can expire (see step 4) and a customer's guess may be stale.