AI Phone Handling for E-Commerce Shops: Orders, Returns and Refunds
How online retailers can handle phone calls: cut avoidable order-status calls, route returns and complaints to people and keep card payments off the phone.
A web shop invites customers to avoid the phone. Yet the phone rings. People call when something has gone wrong, when they are unsure whether to buy, or when they simply prefer to talk. These calls tend to be higher in emotion than in volume: a late parcel before a birthday, a wrong item, a refund that has not arrived.

This guide is for small online retailers deciding how to handle phone calls without building a full call centre. It looks at the main call types, how to reduce them, what automation can reasonably do, and what must stay with people. It connects with Self-Service That Reduces Calls Without Frustrating Callers and Omnichannel Support: Phone, LINE and Email Together. For the broader map, see AI Phone Handling by Industry.
What e-commerce callers want
| Group | Typical question | Can it be self-service? |
|---|---|---|
| Order status | Where is my parcel? When will it arrive? | Largely, with tracking links and messages |
| Returns and refunds | How do I send this back? Where is my refund? | Partly, with a clear policy page and status |
| Product questions | Will this fit? Is it in stock? What is the difference? | Partly, with good product pages |
| Account and payment | Why was my payment declined? I cannot log in | Rarely; often needs a person and care |
| Complaints | Damaged, wrong or missing item | No; needs a person |
Log your own calls for a few weeks. Many shops find that order status is the largest single group and that a good tracking message would remove most of it.
Cut avoidable calls first
The best phone call is the one customers never need to make. Look at your calls and ask what information was missing earlier in the journey.
Where to remove calls
- Order confirmationState clearly what happens next and when the parcel is likely to arrive.
- Shipping updatesSend updates when the order is packed, dispatched and delayed.
- Returns pageExplain the process in steps, with a form and a timeline.
- Product pagesAnswer the questions that cause calls: sizes, compatibility, delivery times.
- Help pagesKeep a short list of answers to the top ten questions where customers can find them.
A well-organised knowledge base serves customers, agents and any automated assistant. Building a Knowledge Base for Support and AI describes how to write one.
Handling order-status calls
Status calls are repetitive and rarely need judgment, which makes them a natural candidate for automation. The key is accurate data.
An order-status call
- IdentifyAsk for the order number or the email used, and verify who the caller is.
- Look upFind the order in your system.
- ExplainTell the caller the status and expected date in plain words.
- OfferSend the tracking details through your usual channel, or offer a callback if there is a problem.
- EscalateIf the parcel is late or lost, hand to a person with the order details.
Returns, refunds and complaints
These calls decide whether a customer buys again. They need empathy and authority to decide.
- Make the returns policy short, clear and findable, and say it the same way everywhere.
- Give a person the power to make exceptions within defined limits.
- Take down the facts once: order number, issue, preferred outcome, photos if relevant.
- Tell customers what happens next and when. A refund timeline you cannot keep is worse than none.
Division of work
| Automation can | Staff should | |
|---|---|---|
| Returns | Explain the process and collect order details | Approve returns and exceptions |
| Refunds | Say where to check the status | Authorise and resolve disputes |
| Damaged items | Take photos and details through a link | Decide on replacement or refund |
| Payment issues | Direct the customer to a safe route | Investigate with the payment provider |
Payments and security
Never ask a caller to read card numbers to an automated assistant, and do not let call recordings or summaries store them. Phone systems like Call do not take payments; customers should pay through your checkout or payment provider. If someone volunteers card details, a person should know how to handle them.
Product questions before buying
Pre-sale callers are the most valuable of all, because a good answer can win an order. They ask whether something fits, how it differs from another product, or when it will arrive. These calls often reveal gaps in your product pages.
- Give them a quick route to someone who knows the products, even if only during certain hours.
- Write down the question and the answer after each call, then add the answer to the product page.
- Offer to follow up with a link to the right page, sent through your usual channel.
- Never pressure a hesitant buyer; a helpful answer is a better sales technique.
If a question is about safety, compatibility or legal requirements, the answer should be checked by someone responsible for the product before it is repeated by anyone, human or automated.
Peak periods
Sales, holidays and product launches bring many orders and many questions at once. Prepare in advance.
- Add a short message at the start of the menu with delivery cut-off dates and returns information.
- Increase the number of people who return callbacks.
- Prepare ready-made replies for the commonest questions.
- Check that tracking messages are switching on correctly.
- After the peak, review what caused the most calls and fix it at the source.
Handling Seasonal Call Peaks provides a longer planning checklist.
A phone menu for a web shop
- Track an order
- Returns and refunds
- Questions before buying
- Problems with an account or payment
- Speak with someone
Keep the route to a person visible. Customers who call about a late parcel are already irritated, and a menu that blocks them makes it worse. Let a business-hours rule decide whether the person option goes to the team or to a voicemail and callback request. See Routing Calls by Business Hours, Holidays and Closures.
Measuring
- Calls by reason, and how many could have been avoided.
- Time to first response and time to resolution.
- Repeat contacts about the same order.
- Share of calls handled without a person, alongside customer satisfaction.
Doing it in Call
In Call, you can build a menu that sends order-status, returns and pre-sale questions to separate queues, with opening hours and a closed greeting. An AI agent can answer common questions from knowledge sources you provide, such as delivery and returns policies, and can hand callers to a person. If you connect your own systems through the Call API and webhooks, a developer can let the agent look things up, but that requires setup. Voicemail and callback requests create a list for staff, the shared inbox keeps email and messages beside calls, and help desk tickets track problems that take longer to solve. See Working the Shared Inbox in Call and Using Help Desk Tickets and Templates in Call.
Frequently asked questions
Can an AI answer order-status calls?
Only reliably if it is connected to your order data. Otherwise it should take the order number and arrange a callback rather than guess.
How do I reduce order-status calls?
Send clear confirmation and dispatch messages, include tracking links and keep a short help page. Many calls disappear when customers are informed early.
Should an assistant process refunds?
No. A person should authorise refunds and exceptions. Automation can explain the process and collect the details.
Can customers pay by phone?
Call does not take payments. Direct customers to your checkout or payment provider and never ask them to read out card numbers to an assistant.
What menu options suit a web shop?
Track an order, returns and refunds, questions before buying, account or payment problems and speak with someone.
How should I prepare for sales periods?
Add a short message with delivery cut-offs and returns information, plan extra callback capacity and review the biggest causes of calls afterwards.