Why footwear support is dominated by sizing
Footwear has one of the highest return rates in ecommerce — typically 20–30% — and the overwhelming majority of returns are sizing-related. The problem is that shoe sizing is inconsistent across brands: a size 10 in one brand is a size 10.5 in another. A running shoe that fits snugly when the box goes on feels tight after three miles. Customers who have been burned before ask questions before they order.
Those pre-purchase sizing questions are the single largest category in most footwear support queues. If the agent cannot answer them well — or worse, gives a generic 'refer to size chart' response that the customer has already seen — the customer either orders the wrong size (return) or does not order at all (lost sale).
The footwear brands that handle this best treat sizing knowledge as a competitive asset. They document how their shoes actually fit: do they run narrow? Is the toe box roomy or snug? Do the insoles compress with wear? An AI agent loaded with this real-world fit data gives recommendations that are meaningfully better than a generic size chart.
Sizing and fit questions represent 30–40% of footwear support volume pre-purchase, and exchange requests (wrong size) represent an additional 15–20% post-purchase. Together they account for roughly half the queue — and both are addressable with better sizing information at the point of sale.
Top ticket types for footwear brands
The first two categories — pre-purchase sizing questions and post-purchase exchange requests — are directly linked. Better sizing answers before the order means fewer wrong-size purchases and fewer exchange requests after. Investing in sizing knowledge pays dividends in both support cost and return rate.
| Ticket type | Typical share | Notes |
|---|---|---|
| Sizing and fit questions (pre-purchase) | 30–40% | Highest ROI for product knowledge investment |
| Exchange requests (wrong size) | 15–20% | Directly reducible with better sizing guidance |
| WISMO and shipping status | 12–18% | Standard ecommerce, easily automated |
| Drop / release questions (limited inventory) | 8–15% | Spikes sharply on release day |
| Returns (fit, preference) | 8–12% | Often size-related |
| Product care and cleaning questions | 5–8% | Answerable from care guides |
Sizing and fit questions: going beyond the size chart
A size chart tells a customer their measurement. What they actually need to know is: does this shoe fit to measurement, run small, or run large? Does it have a wide toe box? Does the arch support hit in the right place? Is there enough room in the heel for a thick sock?
Load your Bookbag knowledge base with per-style fit notes that answer these real questions. 'This trainer runs a half size small — we recommend sizing up if you are between sizes.' 'The toe box is generous; customers with wide feet find this style comfortable in their standard size.' 'This boot has a higher instep than our other styles — if you have a high arch, size up.'
These notes do not take long to write once and they last for the product's lifecycle. Every conversation where the agent uses this data to give a genuine fit recommendation is a conversation that either prevents a return or converts a hesitant browser into a buyer.
- Write per-style fit notes for every SKU: runs true, runs small, runs large, and by how much.
- Note toe box width: narrow, standard, generous — this is a critical dimension for wide-footed customers.
- Include heel fit notes for slip-on styles: snug, normal, room to slip.
- Note sock compatibility: styles suited for thick athletic socks vs thin dress socks.
- Document significant differences between colorways if the construction differs (sometimes it does).
Width, orthotics, and specialty fit needs
Width is an underserved question in most footwear support. Customers with wide or narrow feet have often had bad experiences with brands that do not acknowledge width variation, and when they ask 'do you have wide sizes?' or 'will this work for narrow feet?', they want a direct, informed answer.
If you offer wide widths (2E, 4E) or narrow widths (B), document them clearly in the knowledge base by style. If you do not offer extended widths, note which of your standard styles run generous or narrow so customers can make an informed choice.
Orthotic compatibility is a growing question as more customers wear custom insoles. 'Is the footbed removable?' is the key question — if yes, the shoe can accommodate an orthotic. Load this information per style so the agent can answer it directly rather than escalating.
- Document width availability per style: standard only, or available in wide/narrow.
- For standard-width-only styles, note whether they run narrow, standard, or generous.
- Flag which styles have removable footbeds (orthotic-compatible).
- Include any arch support characteristics: neutral, moderate arch support, high arch support.
- For customers asking about very specific orthopedic needs, configure the agent to recommend consulting a specialist while providing the available product specifications.
Drop releases and limited inventory support
Sneaker and specialty footwear brands with limited releases face the same challenge as fashion brands on drop day: ticket volume spikes sharply the moment a drop goes live or sells out. 'Did I get my pair?', 'the site went down when I was checking out', 'is there a waitlist?', 'when is the next restock?' — all of these questions flood in simultaneously.
Pre-load drop-specific FAQs into the agent before each release: how the release process works (first-come first-served, raffle, waitlist), what happens if the site had issues during the drop, what a restock timeline looks like if you have one, and how to join a waitlist. An agent with these answers can handle thousands of simultaneous drop-day conversations without a human.
For raffle-based drops, the common anxious question is 'did I win?' before the announcement. The agent should be clear about the timeline and confirmation process so customers know when to expect results.
At least 24 hours before a limited release: load drop FAQs, set the release process explanation, update WISMO with expected dispatch windows for successful orders, and brief the escalation queue on what issue types to expect. Most drop-day questions are the same every time — the agent can handle them all.
Returns and exchanges for footwear
Footwear returns have an important policy nuance: worn shoes typically cannot be returned. This creates an inherent tension — customers who want to try shoes at home to assess fit need to know whether a home try-on (without actually walking outside) qualifies as 'worn'. Clarity on this point prevents disputes.
Configure the agent to explain your exact return policy for footwear: trial period duration, condition requirements (unworn, original packaging), exceptions. For size exchanges — the most common footwear return reason — make the exchange path as frictionless as possible. An agent that can initiate a size exchange and issue a return label in one conversation keeps the customer buying from you instead of going to a competitor.
- 1Load your exact footwear return policy: return window, condition requirements, whether trying at home (not outside) qualifies.
- 2Enable size exchange initiation — confirm the replacement size is in stock, initiate the return label, and place the exchange order.
- 3For worn-outside shoes, explain the policy clearly and escalate to a human for exceptions (genuine defects).
- 4For limited edition or sale items, note any final-sale restrictions explicitly.
- 5Follow up with exchange customers at delivery to confirm the new size fits — this single touchpoint recovers potential repeat churners.
Key takeaways
- Sizing and fit questions make up 30–40% of footwear support volume — per-style fit notes beyond the size chart are the highest-ROI knowledge investment.
- Width and orthotic compatibility questions are underserved but answerable with structured product data.
- Drop day queues are manageable for AI at any volume — pre-load release-specific FAQs before every launch.
- Exchanges for wrong size should be as frictionless as possible — one-conversation resolution keeps the customer buying.