Start by finding the purchase
A customer may contact the business with a name, a message, or a payment screenshot. Find the actual order and associated transaction before deciding what can be refunded.
Confirm whether the payment is complete, waiting, or only authorized under the relevant setup. A cancellation of an unpaid request and a refund of collected funds are not the same operation.
Make the decision and amount explicit
If a refund is agreed, record whether it covers the entire order or only part of it. Explain what happens to delivery costs or other items under the applicable policy.
A clear amount prevents a second disagreement after the money moves. Keep the agreed decision in the order record so another colleague can answer the next enquiry without reconstructing the conversation.
Submitting a refund is not always its completion
Providers and payment methods can have different refund processes. A request accepted by one system may still need further processing before the customer sees the returned funds.
Use the actual supported status and timing for your setup. Avoid a universal promise that every refund is instant or follows the same route as a card payment.
Give staff a way to see a failure
A failed or incomplete refund should be visible to the team responsible for it. Record the provider reference and any supported error information, then assign a next action.
Do not repeatedly press a refund button because the customer has not yet seen the money. Check the existing request first. Repeated attempts can make reconciliation and communication harder.
Walk through a partial return before it becomes a support incident
Imagine a customer buying two items and returning only one. Staff need to know which order line is returned, what amount is refundable under the applicable policy, and which payment transaction should receive the refund. A note saying returned is not enough to establish that money has been sent back.
Prepare separate messages for receiving the request, approving it, and confirming the refund action. If the timing depends on a provider or payment method, explain that dependency accurately. The customer should know what has happened so far without the shop promising an arrival date it cannot control.
End with a usable confirmation
Tell the customer what amount was refunded, which order it relates to, and what to do if the result is not visible within the applicable timeframe. Keep the message concise and specific.
A refund is also part of the brand experience. The business may lose one sale but preserve a relationship when the process is honest, understandable, and followed through.
Treat the refund decision, submission, and completion as separate steps that both the customer and the business can follow.