A Week of Try-On Support Questions to Prepare For

A Rehearsal, Not a Ticket Log

What follows is a tabletop exercise, not a report from a help desk. None of these questions are logged tickets; they are the questions a virtual try-on feature invites by its nature, worked out from how Looksy's shopper flow is built. Walking through them as a hypothetical week gives your support team a rehearsal before real shoppers arrive. The format is deliberate. Each day pairs a question a shopper could plausibly ask with the answer your team can give from the published mechanics — and, where the mechanics are not published, the homework to do before launch instead of guessing live. That distinction matters more than any single answer: a team that knows which answers are grounded and which need checking stays accurate under pressure. Run this with the people who will actually answer messages. Read each question aloud, let someone answer cold, then compare what they said to the material below.

Monday: Do I Need to Download Anything?

Start with the easiest one, because it sets the tone for the week: a shopper asks whether they need an app, an account, or anything else before trying something on. The answer is fully grounded in the published flow — no. Photo try-on runs on the product page itself. The shopper uploads one photo and the result appears on that page in about 20 seconds, with no app download, no account creation, and no camera permission involved. The follow-up worth rehearsing is where the shopper actually does it. The answer is the product page of the item they are looking at, which is worth stating plainly, because shoppers used to app-based try-on may go looking for a separate experience. This is also the moment to rehearse the boundary of the answer. If a shopper asks about trying things on in live video, that is a different flow — Realtime video try-on is part of the Scale plan — and support should know which plan the store is on before Monday morning.

Tuesday: What Happens to My Photo?

Sooner or later a shopper will ask where their photo goes, and this is the day to be honest with yourselves about what you actually know. The app listing describes the upload flow — one photo, processed into a result on the product page — but it does not publish retention or storage specifics. That means this answer cannot be improvised from the listing alone. The preparation here is homework rather than rehearsal: before launch, pull the current answer from Looksy's own documentation and privacy materials, align it with your store's privacy policy, and write the agreed wording into your support notes. Support should read that answer, not reconstruct it in the moment. There is a second, softer version of this question: whether the shopper can keep the image afterward. That one is grounded — the shopper can download or share their result directly from the product page, and can retry if they want a different photo. Knowing which version of the photo question is being asked keeps the answer short.

Wednesday: The Result Doesn't Look Right

Midweek, rehearse the quality complaint, because it is the one that tests composure. The grounded part of the answer is procedural: the shopper can retry directly on the product page, and there is a feedback control for flagging a result. A reasonable first response is to suggest a retry with a different photo and invite the feedback. What the listing does not publish is a specification for the ideal input photo, so resist inventing one. The preparation is empirical: before launch, have the team run the flow with a range of their own photos — different lighting, distances, and angles — and note what they observe about which inputs produce better results for your catalog. Those observations become your internal guidance, clearly labeled as your own testing rather than official requirements. Agree on the escalation boundary in advance too: how many retries before support stops troubleshooting and simply thanks the shopper for the feedback. Deciding that during the rehearsal is cheaper than deciding it live.

Thursday: Will This Fit Me?

The sizing question is the one your store controls most directly. Looksy's Size Help works from your own size charts, not a generic database, which means the quality of the answer a shopper receives is a merchandising responsibility before it is a support one. Rehearse two branches. If the product has a current chart, support can point the shopper to the size guidance with confidence. If it does not — a new arrival, a one-off, a category nobody charted — the honest answer is to help the shopper manually and then flag the gap to whoever owns the catalog. The rehearsal is the right moment to find out which of your products fall into that second branch, because discovering chart coverage live, with a shopper waiting, is the avoidable version of this problem. A useful Thursday exercise: pick a handful of products across your categories and check, right then, whether each has a chart and whether it is current. What you find tells you whether this question is ready for launch.

Friday: Can I See It in Motion, and in My Language?

End the week with two questions that both hinge on knowing your own configuration. The first is whether the shopper can try things on in video. Realtime video try-on exists, but it is part of the Scale plan. If the store is on Free, Starter, or Growth, the accurate answer is that photo try-on is available; if the store is on Scale, support should have run the video flow themselves before promising it. Either way, the answer depends on a fact — your plan — that belongs in the support doc, not in anyone's memory. The second is the language question, in either direction: why part of the experience appears in one language, or whether it is available in the shopper's. Looksy's listing enumerates 47 supported languages, so the headline answer will be yes for many storefronts. What the listing does not detail is exactly what is covered for any given language. The preparation is a walkthrough: run the full try-on in your storefront's language before launch and note what the shopper actually sees. Promise what you observed, not what you assume.

Turning the Rehearsal Into a Living FAQ

The output of the week should be a short internal FAQ with two sections: answers grounded in published mechanics, and answers you verified yourselves — the privacy wording, the photo guidance from your own testing, chart coverage, the language walkthrough. Label which is which. When something changes, the second section is where updates land. After launch, real questions will start arriving, and the document should absorb them. Add the questions you did not anticipate, retire the rehearsed ones nobody asks, and re-check the verified answers whenever you change plans, since credit allowances and video availability shift with the plan. The feedback shoppers leave on their results is another input worth reviewing alongside the FAQ, because it reflects what people experienced rather than what they chose to write in. Keep the rehearsal frame even after the feature is live. A short re-run before each peak season — new agents, new products, possibly a new plan — keeps the team's answers as current as the store.

Facts in this post come from the public Shopify App Store listing for Looksy. Last checked 29 July 2026.