User need
A client needs to understand whether a request was received and what information is missing without contacting support repeatedly.
VSPO-authored work sample · VSPA-SIM-015
ClearDesk Partners • Request Journey
A local interactive request prototype showing status, next action and an accessible review path. Synthetic records only.
VSPO-authored demonstration based on an existing VSPA simulation brief. Organizations, records and figures are fictional. This is not completed client work, an assessed learner submission, a client endorsement or evidence of live commercial results.
Service: UI/UX Research, Wireframes & PrototypesFamily: Digital Product & Web SolutionsSource: VSPA-SIM-015 — Customer Portal UI/UX Simulation
Representative output
Explore the work.
REQUEST DEMO-101
Review in progress
The editorial reviewer is checking the supplied content. Next step: review the consolidated comments.
Owner: Editorial reviewer
All records are synthetic.
This example illustrates part of the package. It does not imply that all contracted deliverables, integrations or production controls are present. Interactive previews use synthetic data and do not send messages, process payments or save business records.
The complete written sample
Content, decisions and handover context.
Journey
Open requests, select a request, review its status and next action, then provide missing information through the agreed channel. Each state uses text as well as color.
Design decisions
Use a single request title, a visible owner role and a dated next step. Separate active work from resolved items. Show a helpful empty state rather than an empty table.
Research status
These decisions are authored design assumptions for the simulation. No interviews or usability results are claimed. A real project would validate them with agreed participants.
| Screen | Main task | Exception state |
|---|---|---|
| Overview | Find an active request | No active requests |
| Request detail | Understand next action | Information required |
| Confirmation | Confirm receipt | Submission failed |
How a commissioned output is reviewed
Acceptance is part of the brief.
- ✓ Each screen maps to a defined task
- ✓ Loading, error and empty states are specified
- ✓ Prototype journeys can be followed
- ✓ Research observations are separated from assumptions
These are review criteria, not a claim that this demonstration was independently assessed.