UI/UX design for Thane product and operations teams

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
Line-art illustration of Thane’s Masunda Lake waterfront.

What the project can include

Working with teams in Thane

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.

Worked example

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.

Who this service is for

Bring the people who use, review and maintain the first release into the scope discussion.

Product managers

Test how users handle a mixed return before commissioning changes across the product.

Customer service and accounts teams

Make evidence and decision history easier to review across channels.

How we test the first release

  1. Observe how staff review a return

    Record the facts they check and where a handoff loses the original reason.

  2. Design mixed outcomes at line level

    Prototype a request with one accepted line and another requiring approval.

  3. Validate the customer-facing status

    Check that staff can explain which item has cleared and what happens to the rest.

Agree the project scope

The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.

Discuss your project
Current rules and cases

Share a redacted invoice, return policy and a case that needed manager approval.

Test roles and devices

Agree the staff roles and the phone or desktop environments used to review requests.

Questions before scoping

Ask us something else
Can you redesign part of an internal tool?

Yes. A first engagement can cover the return decision and the roles and systems directly connected to it.

Do you need to change our approval policy?

Your team sets the policy. We make the permitted actions and their reasons visible in the interface.

How do you test a prototype with staff?

We use representative cases and observe whether each participant can find the evidence, act and explain the result.

Review one returns workflow