Spaces

Confirmation messages for support requests and returns

This tool writes messages that confirm what a customer asked for, such as a return or an address change, and what happens next. It is for support teams who want fewer where-is-my-answer chats.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

After a customer asks for something, the next worry is whether anyone heard them. A short confirmation closes that gap. It says what you have done, what the customer should expect and when. It prevents the follow-up message that starts with, did you get my request?

Type what the customer should do or expect after you confirm. Then pick the message that matches the request, copy it and send it. Only confirm things a person has really done or checked, and keep any promise about money or dates to what you can keep.

Return request received

Thank you, we have your return request at [business]. [next step]. It usually takes [timeframe]. If anything changes, we will tell you right here in the chat.

Refund request logged

We have logged your refund request at [business], and a team member will check it. Once it is confirmed, [next step]. Timing is usually [timeframe], and we will message you when it moves.

Address change done

Good news, your new address is saved with [business]. For the record, [next step]. If the parcel has already left us, it can take [timeframe] to catch up, and we will keep you posted.

Callback booked

You are on our list for a call from [business]. Here is what to expect: [next step]. We aim to reach you within [timeframe]. Reply here if your number or the best time changes.

Confirm only what is true

A confirmation is a small promise, so it must be accurate. If a refund still needs a person to check it, say it is logged, not that it is done. Customers forgive a wait much more easily than a broken promise.

Where you can, repeat the key detail back: the order number, the new address, the date. It lets the customer spot a mistake early, while it is still cheap to fix.

  • Say what you did, then what comes next.
  • Give a time range, not an exact hour you cannot hold.
  • Hand refund and money decisions to a person to confirm.

FAQ

When should I send a confirmation?

As soon as you have received or completed the request. A quick confirmation takes pressure off the customer, and it prevents the repeat message asking whether anyone saw their first one.

Can an AI agent confirm a refund?

It can say a request is logged and a person will review it. The decision and the amount should come from a person on your team, since money matters need human checking.

Should a confirmation include a time?

Yes, a realistic range. Say two to three working days, not tomorrow, unless you are sure. Customers plan around what you tell them, so be careful to keep the promise.

More free tools for customer support teams

Read the guide: Answer support messages with an AI agent.