Enough information to start
A short or empty summary cannot enter the review queue. The form explains what is missing, while keeping the entered information in place.
CULVION STUDIO / BUILD 01SELF-INITIATED DEMONSTRATION
Customer Desk
A request comes in.
Nothing gets lost.
Try a customer portal and its review desk. Create a request, make a decision and see the result from both sides.
Try the working exampleA project we created to demonstrate our approach. Example data, with no client commission, external service connection or claimed business results.
The thinking behind Customer DeskThe original brief and first-release boundary.+
Show what happens
after “request received.”
A service form is easy to add. Making the next decision visible takes more thought. This example explores a common gap: a customer submits a request, but ownership, approvals and the final answer are scattered across different places.
The first release is deliberately narrow. It handles one access-request workflow, a second-review exception and a resolution note. Every action updates the record you can inspect.
A working example, under your control
Take a request
through the desk.
Try the Viewer path first. Reset and choose Administrator to explore the second approval. All actions happen in this page and can be reset.
FUNCTIONAL STUDIO EXAMPLE
Customer Desk
Submit a request. Review the decision. Record the outcome.
Draft requestExample record · DEMO-001
01 / REQUEST
What needs to happen?
02 / REVIEW
A decision with an owner.
Create the request to put it in the example triage queue.
03 / RECORD
The work leaves a trail.
- —
No actions yet. This record will reflect the decisions you make.
CUSTOMER VIEWYour request has not been submitted.
Watch the original animated walkthrough+
See the idea in motion
A short guide.
A useful exception.
Follow the captioned sequence or choose a chapter. The guide respects your device’s motion preference. The working example above stays independent.
GUIDED EXAMPLE / CUSTOMER DESKFollow the exception path.Four chapters · approximately 20 seconds · separate from your working example
DEMO-001 / ADMINISTRATOR ACCESSReady for triage
01 / REQUEST
Give a new colleague access to the partner portal
- Requested access
- Administrator
- Example customer
- Partner team
02 / REVIEW
Ready for the next owner.
The request is waiting for triage.
RECORD
Example request DEMO-001 created.
03 / CUSTOMER VIEW
Your request is with the service team.
01 / 04
A request arrives with the useful details.
The customer asks for Administrator access. The summary and requested role arrive together, ready for the team to review.
Look inside the design decisionsValidation, approval, outcomes and customer visibility.+
The decisions underneath the interface
Simple on the surface.
Deliberate underneath.
An exception gets its own route
Viewer and Administrator requests take different review paths. Higher access needs a second-review note before approval.
Approval is not completion
The request still needs a recorded outcome. The team cannot mark it resolved without explaining what happened.
One task, two useful views
The event record reflects the team’s decisions. The customer view gives a simpler status and shows the final answer when the work is resolved.
What a production version addsAccounts, persistent records, integrations and operating ownership.+
A prototype with clear boundaries
What works here.
What a real release adds.
In this demonstration
Input validation, decision rules, review notes, a resolution step, an event record and a customer status view. The controls are keyboard accessible and all data stays in the page’s memory until reset or navigation.
For your production workflow
Agree user accounts, real approval authority, durable storage, connected systems, access controls, notifications and the deployment plan. This demonstration does not claim to provide those services by itself.
A record you can inspect
Open the example record to see the request fields, approval reason, outcome and events together. It gives us something concrete to discuss when mapping the information your own workflow needs to retain.
See the work connect
The customer asks.
What happens next?
Try an order enquiry, an access request or a new business lead. Follow the context from the customer to the person who owns the next step.
Try the connected workflowEXAMPLE / FF-1042“My order arrived damaged.”
CONTEXT ATTACHED
Order record + handling rule
↓NEXT OWNERReturns reviewerDecision and customer update recorded together.
From example to your operation
Which request
would you untangle?
Bring the form, spreadsheet or handoff you use today. We can explore the smallest useful workflow and the decisions it needs to carry.