Retail returns that read the order first

A returns inbox fills with photos, order numbers that do not match, and "the box never arrived" written three ways. The agent who answers from a policy page will approve a label for an order that is still out for delivery, or refuse one that the system already marked eligible.

An order and returns agent helps a retail desk when it reads the order, the shipment, and the return window before it writes anything back. It is a poor fit when the customer is really asking for a goodwill refund.

What the agent can close

Start with facts the commerce system already has:

• Whether the order exists and which SKUs shipped
• Whether the return window on that order is still open
• Whether a prepaid label is already allowed for that reason code
• Where the return should land if the warehouse rule is already on the SKU

If the reason is "not as described" and the policy already routes that to review, the agent opens a ticket with the order and the photos. It does not invent a restocking fee.

What stays with a person

Keep the exceptions on a named queue:

• Exchanges that change the price
• Claims that the carrier already closed
• Wholesale or marketplace orders with a different contract
• Anything that sounds like a safety complaint

The write-back

The useful output is not a chatbot transcript. It is a return created in the same tool the warehouse scans, or a ticket the desk can open without retyping the order number. If the agent cannot write there, the customer will call again tomorrow.