How to reply to customer feedback (with templates)

Reply within a working day, even when the answer is no

Customers judge a product by how quickly someone reads what they wrote. A short reply that says "got it, we are looking at this" beats a perfect answer three weeks later. Reply to every item that has a sender email. If an item has no email, there is nobody to reply to, so record your decision in the internal note and move on.

A reply does three jobs. It shows the message was read, it says what you did with it, and it asks for the one detail you need. Anything beyond that is optional.

Templates for a bug report

Lead with what you did, then ask for what you need. Do not promise a release date unless you control it.

Hi Ana, thanks for the report about the export button doing nothing on Safari. I can reproduce it on the current version, so it is now with the team. I will write again when the fix is live. If you remember the last thing you clicked before it failed, that helps us confirm the fix.

If you cannot reproduce it yet, say so and keep the door open. Section "When you can't reproduce it" in the follow-up guide covers the details: how to follow up on a bug report.

Templates for a feature idea

An idea is not a request for a reply on the spot. Acknowledge the idea, show you understood the problem behind it, and tell the customer where it stands.

Hi Ana, thanks for suggesting a monthly CSV export. We have added your idea to our list. Before we decide, I want to understand what you would do with the file. Is it for a monthly report, or for something else? Your answer helps us choose the right shape for it.

If you have already decided, use the same structure with a clear answer. For a no, see how to say no to a feature request.

Templates for praise

Praise is easy to answer badly. Skip the corporate thank you and name the thing they liked.

Thank you, Ana. Your note about the onboarding checklist made our week. We will keep building on that part. If you are comfortable with it, may we quote one line on our site? We will use your first name only if you say so.

Asking to quote someone is a separate step. Keep it out of the first reply if you are not sure they want it. The full process is in how to turn customer praise into testimonials.

Templates for an unclear message

Some messages say "it's broken" and nothing else. Do not guess and do not ask five questions. Ask one question that narrows the problem.

Hi Ana, thanks for writing in. I want to be sure I understand. When you say the page feels slow, is it the first load, or the wait after each click? Tell me which page you were on and I will take it from there.

One question works better than a list. People answer one question. A list of four gets one answer, if any.

Keep the tone plain and specific

Most reply problems come from tone, not content. A few habits fix most of them:

• Use the customer's words. If they wrote "the list jumps around", write "the list jumps around" back, not "we are aware of a layout issue".
• Say what you did. "I checked the page URL you sent and reproduced it" is more useful than "thanks for your patience".
• Skip stock phrases. Phrases like "we value your input" tell the customer nothing new.
• Sign with your first name. The reply comes from a person, so write it like one.
• Keep it short. Four to six sentences cover most replies.

Timing and follow-up

Send the first reply quickly, even if it only says you are looking. Then send a second message when something changes: a fix, a decision, or a question answered. If a customer does not answer your one question, do not chase them more than once. Note the item as waiting and move on.

Where the reply goes

Escuta Produto does not send emails to customers. Every reply goes from your own email address to the address saved on the feedback item. That address comes from the email field on the form, or from the email passed through the identify call of the widget. The widget documentation explains how identified users skip the email field. Use your normal mail client so replies land in the thread you already use with the customer.

When a customer replies with more anger

A reply sometimes makes things worse. If the customer answers with more anger, do not match it. Acknowledge the frustration in one sentence, answer the question they actually asked, and offer one concrete next step. Avoid repeating the apology in every message, because repeated apologies sound scripted. If the thread turns into a long argument, move it to a short call, then write the outcome back in the same thread so the record stays complete.

Replying from Escuta Produto

The inbox gives you the context you need before you write. Open an item and read the message, the page URL and the browser saved with it, and any metadata such as plan or app version. Copy the sender email, write the reply in your mail client, then set the status. Add an internal note with what you sent and when. The note is the record that stops two people from answering the same message twice, and it helps the next person who opens the item.

For the broader weekly routine that decides which items get a reply first, read how to triage customer feedback.