The Fit-Finder Chat Playbook: Sizing Answers That Stop Returns Before They Ship

Chat is the confidence layer a static chart cannot be. It asks two or three questions, translates measurements into a recommendation for that exact garment, and handles the edge cases, between sizes, between brands, first-time buyers, in plain language. Here is how to build it.

Step 1 – Teach the bot garment truth, not just the chart

A generic size chart says a medium is a medium. Every shopper knows it is not. The same label fits differently across brands, fabrics and cuts, and sometimes across colourways of the same item. Train the bot on garment-level facts: how this item runs (true to size, small, generous), whether the fabric stretches, whether the cut is relaxed or slim, and how it compares with the brand’s other bestsellers. “This runs small, size up if you are between sizes” is an answer. “See the size chart” is a deflection.

Load the answers from real sources: product specs, warehouse notes, and the fit questions support already answers daily. The bot should also know what it does not know. If a garment has no fit data yet, it should say so and offer the closest comparison, not invent a recommendation.

Step 2 – Ask for measurements, not sizes

“What size are you?” is the wrong first question, because the shopper’s answer describes another brand’s garment, not yours. Ask for two or three measurements instead, chest or waist and height, or the size they wear in a brand they know, and let the bot translate. This is where conversational quizzes earn their keep: a short, friendly sizing quiz inside chat feels like help, while a long form feels like homework. Keep it to three questions maximum, and always show the recommendation with its reasoning: “Based on your waist and height, and because this fabric has no stretch, we recommend large.”

Show the reasoning because reasoning is what builds the confidence that stops bracketing. A bare recommendation is just another guess. A recommendation with a reason is advice the shopper can trust.

Step 3 – Handle the between-sizes shopper explicitly

Between-sizes shoppers are your highest-return segment, and most stores abandon them with “size up” or “size down” as if it were obvious. It is not, and the right answer depends on the garment. For a stretch fabric, size down. For a structured jacket, size up. For a shoe, ask about width and socks. Build a decision rule per category, and let the bot explain it: “You are between sizes, and this knit has stretch, so medium will relax to fit. If you prefer a looser drape, large is the safe choice.”

When the answer genuinely depends on preference, say so and offer both options with a clear return path. Honesty here converts better than false certainty, and it is the same principle behind conversational product discovery: the shopper who feels understood buys, and the shopper who feels pushed returns.

Step 4 – Put fit help where hesitation happens

Fit questions do not arrive on the homepage. They arrive on the product page, at the size selector, and in the cart when the shopper re-reads the size they picked. Trigger chat there, not everywhere. A quiet prompt near the size selector, “Not sure about sizing? Ask me in 30 seconds”, catches the shopper at the exact moment of doubt. A popup on arrival catches nobody and annoys everybody.

On the product page, the bot should also surface fit context proactively: model height and the size worn, fabric stretch, and the most common fit question for that item. Shoppers read model stats when they are deciding. They ignore them when they are browsing.

Step 5 – Turn fit answers into fit data

Every fit conversation is a product data point. Log which garments generate the most sizing questions, which sizes get recommended most, and which recommendations still end in returns. That loop is how a store fixes its catalogue instead of just answering its inbox. If one dress generates ten times the fit questions of the rest of the range, the product page is missing information, or the garment’s cut is genuinely inconsistent. Fix the page, and the questions stop.

This is also where fit work pays for the rest of the funnel. The returns chat playbook covers what happens when a return is unavoidable, but every return prevented by a fit answer is a return that never touches that playbook, never touches the warehouse, and never risks a lost customer.

Step 6 – Close the loop after delivery

Fit help should not end at checkout. A short post-delivery message, “How did the fit run?”, does three jobs at once. It catches a wrong-size buyer before they quietly return, it collects fit feedback that improves future recommendations, and it opens a conversation with a customer who just received the product. Shoppers who answer are also the shoppers most likely to buy again, which is why browse abandonment chat and post-purchase follow-up belong in the same system: the store that talks to customers after delivery keeps them, and the store that goes silent after payment loses them to the next ad.

When a shopper does report a fit problem, the bot should offer the fix immediately: exchange for the recommended size, with the exchange size chosen from the same measurement logic, not from a fresh guess. A shopper who exchanges once and gets it right becomes loyal. A shopper who returns twice leaves. And a successful exchange is a natural moment for a relevant add-on, which is why conversational upsell inside chat works best when it follows a solved problem, not a cold pitch.

Frequently asked questions