5 repetitive customer questions every webshop gets (and how to automate them)
A typical support inbox on a busy week has the same pattern. It is often the same five questions, just in a different order: “Where is my order?”, “Can I return this?”, “Do you have this in size M?”
Your team already knows the answers. The difference is speed and consistency.
This is a practical playbook for handling those five recurring questions with automation, so people can stay focused on issues that need judgment.
Repetitive queries
60-80% — Source: Gurusup (opens in a new tab)
of tickets a support team receives are repetitive queries
Cost per ticket
$2.70-$12 — Source: Matrixflows (opens in a new tab) ≈€2.50-€11
per e-commerce support interaction
Agent burnout
74% — Source: Sentisum, on Toister Solutions data (opens in a new tab)
of agents are at risk of burnout, with repetitive work a leading cause
AI resolution
~80% — Source: IBM (opens in a new tab)
of routine queries can be resolved without a human
Sources: Gurusup (share of repetitive tickets), Matrixflows (cost per ticket), Sentisum (agent burnout), IBM (routine-query resolution)
Why these five questions hurt so much
Most e-commerce stores eventually hit the same wall: high-volume questions that repeat in predictable patterns. They’re simple for agents to answer, but expensive because they arrive when customers are already deciding whether to buy.
Internal teams report the same pattern. The queue grows, response quality varies by who happens to be on shift, and customers get the impression your support is busy instead of reliable.
Support teams typically find that 60-80% — Source: Gurusup (opens in a new tab) of the tickets they receive are repetitive queries - order status, pricing, policy questions that already have a documented answer. In practice, that repeat traffic is usually the first place to look when a younger store has fast product movement and a small support team.
A practical way to think about it: when a meaningful share of your tickets are repetitive, a large share of your team’s day is spent repeating the same explanation.
At a retail benchmark of $2.70-$12 — Source: Matrixflows (opens in a new tab) per assisted ticket, a mid-sized webshop with 2,000 monthly tickets spends thousands of euros a month on repetitive work alone. The bigger cost is not the ticket price. It is the cognitive debt: your team cannot invest in conversion-critical moments when the same simple question repeats all day.
Set the split clearly: automation handles scripted questions, humans handle the ones that need judgment. The five sections below show exactly how to do that.
1. Where is my order?
If a customer has already paid, this question is often about trust. WISMO is the point where your post-purchase flow is either reassuring or weakening.
The practical fix is one source of truth for inventory and shipment status across channels.
Why customers ask
88% — Source: Capital One Shopping (opens in a new tab) of shoppers find real-time delivery tracking critical to a positive experience. When tracking pages are hard to find or updates lag, they contact support.
The support burden
Each WISMO ticket costs $4-$16 — Source: Ringly (opens in a new tab) depending on channel (≈€3.70-€14.70), and WISMO is 30-50% — Source: Ringly, on Gorgias data (opens in a new tab) of all DTC support contacts. A store with 3,000 monthly WISMO tickets spends $12,000-$48,000 (≈€11,000-€44,200) on order status alone.
The automation fix
An AI chatbot connects to your order system, reads status in real time, and gives customers one clear update quickly. No one is waiting around for a support agent to start at the top of a queue.
2. Can I return this?
Returns and refunds are high frequency because policies are often unclear under pressure. With 34% — Source: eDesk, on Shopify data (opens in a new tab) of product returns caused by a customer misunderstanding the return policy, this question repeats through the day.
Why customers ask
Return policies vary wildly between stores. Customers want reassurance about deadlines, conditions, and whether they will have to pay for return shipping.
The support burden
Return inquiries often require agents to look up orders, check eligibility, and walk customers through multi-step processes, taking 5-10 minutes — Source: Lorikeet (opens in a new tab) of combined hold, lookup and communication time per ticket.
The automation fix
An AI chatbot checks policy conditions instantly, confirms what applies, and can trigger return-label steps if your setup allows it.
3. Do you have this in my size?
Sizing and availability questions show buying intent. If your answer is late, the conversion usually moves away from your store.
Why customers ask
Product pages often display confusing size charts or do not clearly show which variants are in stock. Customers need confirmation before committing to a purchase.
The support burden
Pre-sale questions are high-volume but low-complexity. Handle time runs 6-10 minutes — Source: Fairview (opens in a new tab) per ticket, and even best-in-class teams need 3-5 minutes — Source: Fairview (opens in a new tab), because agents have to check the inventory system before they can answer.
The automation fix
A product-aware AI chatbot has immediate catalog access, so it can answer sizing and availability from live data. It can also suggest alternatives when the exact variant is unavailable.
4. Can I change my order?
These requests are common after checkout and often time-sensitive: the window before fulfillment is still open can be short.
Why customers ask
When there is no self-service option to modify an order, customers have to contact support and hope the change window is still open.
The support burden
Modification requests require agents to access order systems, check fulfillment status, and coordinate with warehouse teams. If the agent is slow, the window closes and the customer gets frustrated.
The automation fix
With an order-aware chatbot, customers get immediate confirmation of change windows. If a modification is still possible, the assistant can assist right away. If not, it sets expectations clearly.
5. What’s the difference between product A and B?
Most shoppers compare prices across multiple retailers before buying. If product pages do not surface those differences quickly, support does it for them.
Why customers ask
Product descriptions often use marketing language that obscures practical differences. What actually helps is a straightforward, honest comparison tailored to their needs.
The support burden
Comparison questions require context and confidence. Agents often have to gather specs across multiple products before giving a clear recommendation.
The automation fix
A product-aware AI chatbot reads from your catalog data, so it can put two products side by side without an agent looking up the specs first. How good the comparison is depends on how complete your product data is.
Manual support vs. AI automation: a side-by-side view
| Metric | Manual support | AI chatbot |
|---|---|---|
| Response time | 4-24 hours average | Under 5 seconds |
| Cost per interaction | $2.70 - $12.00 — Source: Matrixflows (opens in a new tab) (≈€2.50-€11.00) | $0.50 - $2.37 — Source: Matrixflows (opens in a new tab) (≈€0.45-€2.20) |
| Availability | Business hours only | 24/7/365 |
| Consistency | Varies by agent | Same answer every time, as good as the source data |
| Scalability | Linear cost increase | Extra volume adds little cost |
| Product knowledge | Requires training | Reads from the imported catalog |
| Languages | Depends on team hiring | Multi-language by default |
Sources: Matrixflows, LiveChatAI. EUR figures are approximate USD conversions.
Common questions about chatbot automation
Will a chatbot replace my entire support team?
What happens when the chatbot cannot answer a question?
How long does it take to set up?
Is it GDPR-compliant for European webshops?
What kind of ROI can I expect?
What to do with this after reading
The five questions above are not going away. The win comes from how you structure your operations around them. The first week after publishing this should be simple:
- Audit your ticket tags for these top categories.
- Map one ownership model for each question.
- Set one response SLA per category and let the chatbot own what is scripted.
When your team stops re-answering the same thing from scratch, they gain three things: more time, more consistency, and more room to solve higher-value customer problems.
Identify your top 5
Audit your support inbox. Tag tickets by category for one week. In most webshops these five question types make up a large share of the tickets.
Automate the predictable
Deploy a product-aware AI chatbot that connects to your catalog and order system. Let it handle the repetitive queries 24/7.
Elevate your team
Free your human agents for the work that matters: complex issues, relationship building, and strategic customer engagement.
Stop answering the same questions, start solving bigger ones
An automated setup handles these repetitive conversations so your team can stay focused on what only humans do best: nuance, negotiation, and relationship moments. Start with one category this week and expand every month.
No credit card · Set up in minutes