top of page
Wishlist for Virtual Shopping

Add VIC-interested products to Wishlist during TourRing

lv cover.png




Virtual Wishlist is an exigent white label request from our white label clients as they need a function to add VIC’s interested product into the wishlist during TourRing (the following abbrieviation as TR) .




Researcher, UI Designer

User problem

Clients cannot effectively record the needs of guests during TR, since there’s no way to clearly list down who may like certain product in which TR session. Therefore if clients want to catch up with the discussion with guests, an extra long and tedious information recollecting will have to be conducted afterward.

Roles & scenario

Right before TR session, the Host will be the one to start TR and send the link to VIC from editor platform, while Sales, who does the shopping guide, will enter TR in the viewer platform with the link, and subsequently, VIC will enter TR with the link when the session begins. During the session, Host shares the screen to wander around in the LiveTour showroom as Sales elaborates each product to VIC, jotting down what VIC likes and their special needs into the wishlist.
After the session, Sales will filter certain session, VIC or product and export the result as excel or pdf file for the follow-up analytic or contact use.


Roles and scenarios in the wishlist flow

Early research findings

Prerequisite as early research is, it articulates details of clients’ request including the scope of wishlist, particular situation they may encounter, and concrete reason why they want different types of data result.

1. Clients want to add wishlist and make notes for each guest

Although most of the situation only involve one single VIC, we should still reserve some space for multiple VICs since clients may expand their usage to group TR, according to EMEA team. In this sense, Host is capable to assign certain VIC a wishlist and assign another as well.

2. Clients have to be able to change name of guest for correct data result

Since VICs need to fill in their name in the TR landing page before entering, this situation may cause certain scenarios such as

  • They type their name wrong which brings about the confusion of the follow up data analyzing

  • TR session accidentally disconnects (which happens often) and in the new TR session VIC types a different name from the previous one

Hence, access to edit VIC’s name become necessary at this point.

3. Clients need to export wishlist as excel for analytic use and as PDF for guests

Two types of file are required in editor platform export, one as excel for internal analytic use, and one as pdf for Sales to send it to the guests and boost purchase.

pdf and excel.png

Excel result

PDF result

Flowchart and user story

Firstly, flowcharts are established depending on different user mode (editor and viewer) and user journey (sign in, add to wishlist, and filter wishlist data, etc.) It helps developers and us to confirm not only structure and scope of data but also whether there is any breaking point during the whole process.


Flowchart of each user journey

UI & prototype

1. Editor

On web, users can filter TR session and guest name, and even search for certain tag, to get a full wishlist result. The list shows TR session, tag name, tag ID, guest name and wishlist notes.

Prototype video of editor

2. Viewer

On mobile, guest users have to fill complete name to enter TR. On web, host users can show around the room and click tags, adding wishlist for each guest once at a time.

Prototype on mobile and laptop

bottom of page