Returns review prototype
Put invoice lines, evidence and the next available action on the review screen.
Make a return or credit request easy to review without leaving the decision screen. GreyBath designs the information hierarchy, role-specific actions and feedback users need at each step.
Explore what we build
01 / What we build
Put invoice lines, evidence and the next available action on the review screen.
Show the reason for a review and the wording customers see while a line is pending.
Hand over decision states, keyboard order and error feedback for implementation.
City context, honestly stated
For a Thane distributor supporting counter staff and account managers, a return can start in a different channel from the sale. Design the review around the invoice line and the evidence needed for each decision. GreyBath delivers through remote workshops, reviews and handover.
A counter employee opens a return for two parts from the same invoice. One is unopened and the other has a scratched housing. The review screen shows the quantity and condition for each line and suggests the actions allowed by the current policy. The employee can accept the unopened part and send the damaged one for review. The account manager sees the attached photo and the reason for escalation. In testing, the employee must explain the resulting customer status, and the manager must find the evidence and record a decision without changing the accepted line.
Where it fits
Bring the people who use, review and maintain the first release into the scope discussion.
Test how users handle a mixed return before commissioning changes across the product.
Make evidence and decision history easier to review across channels.
How we work
Record the facts they check and where a handoff loses the original reason.
Prototype a request with one accepted line and another requiring approval.
Check that staff can explain which item has cleared and what happens to the rest.
The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.
Discuss your projectShare a redacted invoice, return policy and a case that needed manager approval.
Agree the staff roles and the phone or desktop environments used to review requests.
Yes. A first engagement can cover the return decision and the roles and systems directly connected to it.
Your team sets the policy. We make the permitted actions and their reasons visible in the interface.
We use representative cases and observe whether each participant can find the evidence, act and explain the result.
Start with one workflow