Name the exact requested replacement
A product name alone may omit size, color, model or bundle. Confirm the variant the customer wants and distinguish a replacement request from an already reserved unit. Use the approved exchange process to decide what information the receiving team needs. If inventory is not connected, a support assistant cannot establish availability by reading a product description.
Separate availability from reservation
Even a recent stock view may not mean an item has been reserved for this customer. Explain what the source actually confirms and route any stock commitment to the authorized process. Keep price differences, delivery estimates and approval conditions separate. A friendly message should not merge several pending steps into 'your exchange is ready.'
Fictional worked example
Fictional case: a customer wants a blue medium shirt instead of a blue small. The catalog lists both sizes, but the helpdesk has no stock result. The reply can confirm the requested variant and send it for availability review. It should not say medium is available or reserved. Once the authorized team confirms, the next message can describe the verified outcome.
Action checklist
- Capture the exact product variant requested.
- Identify the applicable exchange workflow and responsible team.
- Distinguish catalog listing, available stock and reservation.
- Do not promise a replacement or delivery date before verification.