Open the inbox of almost any online store and the same messages repeat all day. Where's my order. Does this run small. Can I return it. What's shipping to my country. None of these are hard. All of them are constant, and every one is a customer who wants an answer before they'll relax or buy.
These questions are made for a chatbot, because the answers already live in your policies and product pages. Handing them off frees your team for the messages that need a person, and it gets the customer a faster reply than any inbox can.
The questions that flood every store
Before automating anything, it helps to see how lopsided the volume is. A typical store's support breaks down roughly like this:
| Question type | How common | Bot-friendly? |
|---|---|---|
| Where is my order / tracking | Very high | Mostly: timelines from policy, specific orders to a human |
| Shipping times and costs | High | Yes |
| Returns and refund policy | High | Yes |
| Sizing, fit, materials | High | Yes |
| Stock and restock dates | Medium | Yes, from what your pages say |
| Damaged or wrong item | Medium | Handoff to human |
| Payment or fraud dispute | Low | Handoff to human |
The pattern is clear. The loudest, most repetitive categories are exactly the ones software handles well, and the delicate ones are the minority.
"Where is my order" is the big one
If you automate one thing, make it the questions around order status. It's usually the single largest category, and much of it isn't really a lookup at all. A customer wants a date and some reassurance, not a conversation.
A chatbot with access to your order system can return a live status. SpideyChat doesn't connect to your store, so it answers from your shipping policy instead: when orders dispatch, how long delivery takes, where the tracking email comes from, and what to do if a parcel hasn't arrived. For a specific order it collects the order number and email and opens a ticket. Compare that to the old flow: the customer emails, waits, gets an auto-reply, and finally hears back the next morning with a timeline they could have had in five seconds. The bot doesn't just save your team time. For the routine version of the question, it gives the customer a better experience than a human reply could, because it's immediate.
Sizing, fit, and product details
Here's a category that quietly costs you twice. When a shopper can't find whether a jacket runs large or what a candle actually smells like, one of two things happens. They leave without buying, or they buy the wrong thing and return it. Both hurt.
A chatbot trained on your product pages, size charts, and materials can answer "will this fit a 15-inch laptop" or "is this fragrance strong" right when the person is deciding. That's a sale saved on the front end and a return avoided on the back end. Answering fit questions before purchase is one of the most underrated ways to bring your return rate down, and it happens automatically once the bot knows your catalog.
Returns, exchanges, and refunds
Policy questions are constant and, done right, safe to automate. How long is the return window, who pays return shipping, how do exchanges work, when does a refund land. These have written answers, and a bot can deliver them clearly and consistently, which beats a tired rep paraphrasing the policy differently each time.
The line to hold: the bot explains the policy, but it doesn't approve exceptions. "Can I return this 45 days late because it was a gift" is a judgment call. The bot should recognize that, collect the order details, and route it to a person rather than guessing yes or no.
Stock and the "is it coming back" question
Inventory questions are sneaky. A shopper who wants a sold-out item is a customer trying to give you money, and a slow or missing answer sends them elsewhere for good. "Is this coming back in size 9?" deserves a fast reply while they still care.
A chatbot connected to current stock data can tell someone what's available right now. A website assistant that reads your pages can tell them what the product page shows and what your restock policy says, and for out-of-stock items it can do something better than a shrug: it takes their email and the size they wanted so your team can follow up when it returns. That turns a dead end into a captured lead, and the customer feels looked after instead of ignored.
The one rule here is accuracy. A bot cheerfully saying "in stock" about something you sold out of yesterday creates the exact frustration you were trying to avoid, so the pages behind it have to stay current.
The ones to keep human
Some ecommerce messages should never be fully automated, because getting them wrong is expensive in trust:
- A damaged, defective, or wrong item arrived. The customer is already unhappy; they need a person and a fix, fast.
- A payment problem or suspected fraud. Sensitive and high-stakes.
- Any refund or exchange outside policy. Someone with authority should decide.
- A visibly frustrated customer. Even if the question is simple, the emotion isn't.
The goal isn't to keep these away from the bot entirely. It's to have the bot recognize them early and hand off cleanly, with the full chat and order info attached, so the customer doesn't start over.
Setting it up right
A short checklist to get an ecommerce bot working without creating new problems:
- Train it on your real content. Product pages, shipping page, return policy, FAQ. Guesses are dangerous in retail.
- Decide where order lookups go. SpideyChat doesn't connect to order data, so set it to collect the order number and pass specific orders to your team, and give it a clear page explaining how tracking works.
- Keep stock and shipping info current. A confident "in stock" on a sold-out item creates an angry customer.
- Write clear handoff rules. Define which messages go straight to a human, and make the "talk to a person" option easy to find.
- Match your brand voice. A homeware store and a skate shop shouldn't sound identical. The bot should sound like you.
- Read transcripts weekly. Real questions will reveal gaps in your product pages you didn't know existed.
A quick example: Harbor & Pine, a fictional outdoor gear store, set up a chatbot on delivery times, shipping, sizing, and returns. Overnight how-long-will-it-take questions, once a morning chore, now answer themselves, and the order-specific ones wait in the queue with the order number attached. Sizing questions on their boots get answered from the size chart the bot was trained on, and their return desk started seeing fewer "wrong size" packages come back. In SpideyChat they crawled the store, added a handful of Q&A for edge cases, and set damaged-item messages to route straight to a person.
The stores that get this right don't automate to save money and hope customers don't notice. They automate the boring majority so the whole experience gets faster, then spend their human time where it counts, on the problems a script has no business solving. Start with delivery and order questions, add sizing and returns, and keep the messy human moments human.