Why do returns turn into calls?

Customers call when a return goes quiet

Take one of those customers. She sent a pair of shoes back ten days ago and has heard nothing since the confirmation email. Polite, a little worried, she would like to know where her money is, and she is the third customer this morning to ask exactly that.

Very few customers call about a return to argue with your policy. They call because, once they asked to send something back, the store went quiet. A lot of returns management happens where the customer can't see it: in the warehouse, at the inspection bench, in the payment system. From the outside, a return that is moving and a return that is lost look the same, and a phone call is the only way they have to find out which one it is.

The good news is that these calls are predictable. A return has four quiet stretches, and each one produces the same question from one customer after another. Answer each one with a short message before the customer has a reason to wonder, and most of those calls are never made.

Where do calls about returns come from?

Seen from the customer's side, a return has five moments: Return requested, Back at warehouse (the returned parcel has reached you), Check done, Refund sent and Money in account. The calls come from the gaps between them, and customers describe each gap in almost the same words.

Right after Return requested, the question is "How do I send it?" The customer wants to know where the label is, when the courier comes and whether they need the original box. Once the parcel has left, the question becomes "Did you get it?", and it stays until the parcel is Back at warehouse. Then the item waits for the check, where your team inspects it before any refund, and customers ask "Was it accepted?" The last wait runs from Refund sent until Money in account. The money has left you but has not reached the customer's account yet, and that is when you hear "Where is my money?"

To see which of these waits fills your own line, take one month of calls about returns, from customers who had already asked to send something back, and sort each call by what the customer was waiting for. Listen to the calls, or read the transcripts if you record them. The reason codes your team picks at the end of a busy call won't help much, because "return inquiry" covers all four waits at once. Most calls fit one wait easily. A few won't, such as a question about the policy itself, an item missing from the parcel or a gift return, and those go in a pile of their own.

Imagine an online shoe and clothing store that did this for September. The numbers here are an example, not real data. That month the store handled 1,000 returns and took 620 calls about returns, and the team listened to every one. "Where is my money?" was the biggest group, with 230 calls, about 37% of the total. Then came "How do I send it?" with 140, "Did you get it?" with 120 and "Was it accepted?" with 90. The other 40 went in the pile of their own. All together, that is 62 calls per 100 returns. At the time, the store sent one email at Return requested with a label link, and nothing after that.

Before you write a single message, look at your return form. Many "How do I send it?" calls start there, when the form ends with "we will contact you" and leaves the customer with nothing to do but wait. Let customers start a return from the order in a few taps, pick the reason from a short list, and get the label or a pickup slot right away.

What should each message say?

Each of the four messages tells the customer three things: what just happened, what happens next, and when. Send them on the channel the customer used to order (email, SMS or WhatsApp), with the same words on each. Put an hour on every pickup and every deadline you set, because "Wednesday" on its own still leaves someone wondering whether they have to stay home all day.

For a shoe return, the four messages could read like this.

• The first goes out at Return requested and answers "How do I send it?" before anyone has to ask. "Hi [name], we have your return request for [product]. A courier will collect it on Wednesday between 10:00 and 13:00, so please have it packed. You do not need to print anything. We will write again when it reaches us."
• When the parcel is Back at warehouse, say so, and say when the check will be finished. "Your return of [product] reached our warehouse today. We check every return within two working days, so you will hear from us by Friday at 18:00."
• At Check done, the customer wants the result and the day the refund goes out. "Your [product] passed our check. Your refund of €79.90 goes to your card ending [1234] tomorrow." If the item fails the check, explain why in the same message, add the photo, and tell the customer what they can do next.
• At Refund sent, give the date by which the money should be there. "We sent €79.90 back to your card ending [1234] today. It should show in your account within 3 to 5 working days, so by [date]. If it is not there by then, reply to this message and we will look into it."

Apart from a failed check, where the customer has a decision to make, none of these messages waits for an answer. They inform, and a message that only informs has done its job once it is read. For WhatsApp, our post on which WhatsApp messages customers reply to covers when a message should ask for a reply.

Of the four, the date line in the refund message matters most. The shoe store's October numbers show why.

Why do refund calls keep coming?

From 1 October the shoe store sent four messages, one at each moment from Return requested to Refund sent. In October it handled 960 returns and took 250 calls about returns. The number of returns changes every month, so compare calls per 100 returns, not raw calls.

Calls per 100 returns fell from 62 to 26, and every wait got smaller. "Where is my money?" fell the least in proportion, from 230 to 105, so it became an even bigger share of what was left, 105 of the 250 calls in October, or about 42%. Other questions stayed at 40, as you would expect, because a message about where a return stands does not answer a question about the policy. Those questions belong to your return page and your team.

The refund calls kept coming for a plain reason. The store's October refund message said "We sent €79.90 back to your card ending [1234] today." and nothing about when the money would show. Its payment provider says refunds show in the customer's account in 3 to 5 working days, but nobody passed that on to the customer. When the team went through October's 105 "Where is my money?" calls, 88 had come in the first five working days, before anyone could say the money was late. The other 17 came on day 6 or 7. For those customers the money really was late, or it had gone to a card they had closed.

Think about those 88 customers. The store has told them the money is on its way back, their account still shows nothing, and a call is the quickest way to find out which of the two is right. The refund leaves you days before their bank shows it. That is why the refund message ends with a date and what to do if the money is not there by then. Customers who still call after that date are the ones you want on the phone, because for them something really has gone wrong.

Can a return become an exchange?

It can, if you offer it at the right moment. When the reason is size or fit, the exchange belongs inside the return request, before the customer gets a label. They have just told you the shoes are too small, so ask the obvious question. "Would you like them in a 42 instead? We can send the new pair today. The courier brings it on Thursday between 10:00 and 13:00 and takes this pair back at the same time."

Keep the refund one tap away, next to the offer. A customer who wants their money back and has to search for the button will call you about that too, and it won't be a friendly call.

What should you track each month?

Start with calls per 100 returns, split by the four waits. It shows you which quiet stretch still produces calls, and it stays comparable in a month when a sale doubles your returns.

Split "Where is my money?" once more, by the date your refund message gave. Calls before that date mean the message was not read, or not believed. Calls after it mean something in your process is late, and each of those deserves a closer look.

Second calls about the same return are worth counting too. When a customer calls twice, it often means the first answer did not say what happens next. For the calls that still come in, whoever answers should see the return's current moment and its dates on one screen. With that in front of them, most of these calls take a minute.

Where does DRING come in?

For an online store, DRING helps in two places. Notif sends a message on WhatsApp, SMS or email the moment your system fires an event, in this case Return requested, Back at warehouse, Check done and Refund sent. If a message goes unread, or is read but not answered where an answer was expected, an AI agent calls after the wait window you set for that event type. The call already knows what the message said.

For the calls that still come, DRING's support agent answers the line, finds the order and handles the return question on the call. Within the policy your team configures, it can issue a refund, generate a return label or update an address, and anything outside that policy goes to a person with a written summary, so the customer does not start over. The same agent works across phone, WhatsApp, SMS, email and web chat. 62 languages are available, 10 are live today, and yours is validated before launch.

Either way, we start with the reasons your customers call you most, mapped before any agent is written.