Design prototype — Ops "Client Requests" queue. This screen exists today; shown here carrying a restore request raised through the proposed client-portal flow. ← back to journey
sam
Current screen, proposed data

Client Requests

Open and in-progress requests, newest first. Resolved and rejected ones are hidden until you ask for them.

ReferenceTypeTitleOrganisationStatusCreated
RESTORE-4471 Request restore wrenfield.example — site not serving after plugin update Wrenfield Studio Needs action Today, 9:42am
MISC-4468 Other Question about invoice #8834 Alder Trading Pty Ltd New Yesterday, 4:15pm
RESTORE-4460 Request restore staging.marlowe.example — accidental page deletion Marlowe Nominees Pty Ltd New 2 days ago
Proposed: the "Needs action" pill and the request type "Request restore" reflect the type already passed today via /requests/new?type=request-restore&entityId=… in the client portal's link. This table's columns (Reference, Type, Title, Organisation, Status, Created) match the real, empty version of this screen seen live — only the row content here is invented.