We read every support ticket for four weeks and tagged them by cause. The result was uncomfortable: most tickets were not support problems at all. They were product pages that failed to answer three ordinary questions before checkout - what size to choose, how to care for the item, and when it would arrive.
Why we did this
Small stores handle support as a cost centre and product pages as a marketing surface. That is backwards. A product page is the cheapest support channel you own: it answers the same question for every visitor, at any hour, without a reply time.
We wanted to know which questions kept arriving after someone had already read the page. Those are the gaps.
The tagging method
Every ticket got one label, chosen from a fixed list, plus the page the customer had visited before writing. We kept the list deliberately boring:
| Label | What it means |
|---|---|
| Pre-order question | asked before placing an order |
| Post-order logistics | where is it, when will it arrive |
| Care and use | how to clean, store, or handle |
| Returns | how to send it back |
| Payment | failed or unclear payment step |
Four weeks, 103 tickets. No sampling, no filtering.
What the numbers said
Pre-order questions were 41% of the total, and almost all of them fell into three buckets: sizing, care, and delivery timing. Payment was 12%. Returns was 9% - lower than we expected, which told us the returns page was doing its job.
The surprise was where pre-order questions landed: not on the product page alone, but on the product page after the customer had scrolled past the gallery and stopped at the specification block, which was a wall of short labels with no explanation.
What we changed
- A sizing block above the fold on mobile. One sentence, one table, one line telling the reader what to do if they are between two options.
- A care block with three steps. Wash, dry, store. Written as instructions, not adjectives.
- A delivery expectation line on the page itself. Not "fast shipping" but the actual dispatch window and what the customer will receive by email.
- A visible link to the returns page at the point where a hesitant reader usually stops scrolling.
We did not add a chatbot, a popup, or a new help centre. The page had to carry the answer.
What we deliberately did not change
We kept the specification block. It is useful to a smaller group of readers who want exact dimensions, and removing it would have traded one support load for another.
We also kept category pages free of figures, because the questions we were seeing were not about cost - they were about fit and certainty.
The second-order finding
Once the page answered sizing and care, the next wave of tickets was about timing: not "when will it ship" but "what exactly will happen after I order". That is a different kind of question - it is about the sequence of events, not the product.
We answered it with a three-line timeline on the page: order confirmed, dispatch window, delivery window, plus what the customer receives by email at each step. Tickets in that bucket fell by roughly half in the following month.
The lesson generalises: a product page should describe the product and the process. Most stores describe only the product.
A checklist you can copy
- Tag every ticket for two weeks. Counting beats guessing.
- Map each ticket to the last page the customer read.
- Fix the three highest-volume gaps on the page, not in a FAQ document.
- Re-measure after four weeks. If the mix shifts, you fixed the right thing.
FAQ
How many tickets do you need?
Fifty is enough to see a pattern in a small store. Two weeks of real tickets beats a survey.
What if support volume is too low to measure?
Then read your own checkout abandonment reasons and your contact-form messages; the same three questions usually appear.
Does this replace human support?
No. It removes the repetitive part so the human part gets real attention.
What we would tell another small store
Your product page is a support document that happens to sell. Write it for the person who is one question away from leaving, and answer that question in the place where they stopped reading. The care guides and the returns page on our own store were rewritten after this exercise; if you want to compare notes, write to us.
LoveyDovey is a small Indian online store; the guides it publishes on materials, care and delivery are at lovedovey.com/learn.
Top comments (0)