Reply: Feature Request, Suggestion or Feedback

Purpose: thank customers for ideas and feedback, set honest expectations, and make sure the idea reaches the client.

Use it when: a customer suggests a feature, product, improvement, or shares general feedback (good or bad).

Goal: the customer feels heard, and the feedback is logged where the client will see it.

Version: v1.0

Before you send

Check if the feature already exists (many "requests" are how-to questions)
Check if it is already on a known list or roadmap the client has shared for support use
Note the exact request in the customer's words for the feedback log

The flow

1. Thank them specifically

You: Hi (CUSTOMER FIRST NAME), Thanks for taking the time to suggest (FEATURE IN THEIR WORDS). It's clear you've thought about how it would help with (THEIR USE CASE).

Why it works: repeating their idea shows you read and understood it.

2. Honest expectation

You: I've added it to our product feedback list, where the team reviews ideas every (FREQUENCY, if known). I can't promise if or when it'll be built, but every request is read, and requests from customers using the product every day carry real weight.

Why it works: honest, no false promise, still meaningful.

3. Something useful now (if possible)

You: In the meantime, (WORKAROUND OR CLOSEST FEATURE) may help: (SHORT STEPS OR LINK). Best, (YOUR NAME)

If the feature already exists

You: Good news: you can already do this. Here's how: (STEPS). It's a little hidden, so thanks for asking. I've also passed on that it's hard to find.

Use the Product or How-To reply format.

If it is positive feedback or a compliment

You: Thank you, (CUSTOMER FIRST NAME). That's lovely to hear, and I've shared it with the team. (If they mention a person:) I've made sure (NAME) sees it too.

Log it. Clients love seeing compliments in the weekly report.

If it is negative feedback with no request

You: Thanks for being honest about (ISSUE). I've passed your comments to the team so they can look at it. If there's anything I can fix for you today, just reply here.

If there is a fixable problem hidden in the feedback, treat it as a support ticket.

Objections and tricky replies

Customer says	You reply
"When will it be ready?"	"I don't have a date, and I don't want to guess. If it's released, it'll be announced in (CHANNEL)."
"I'll cancel if you don't add it."	"I understand it matters to you, and I've noted that clearly for the team. If you decide to cancel, I can help you with that too."
"Competitor X has this."	"Thanks, that's useful context, and I've included it with your request." (Never criticize competitors.)

After you send

Feedback log entry:

(DATE) · (CUSTOMER NAME OR ID) · Request: (EXACT WORDS) · Use case: (WHY) · Plan: (PLAN) · Ticket: (TICKET REFERENCE)

Tags: feature request or feedback, product area. Status: Solved.

Coach's note: count requests, not just log them. "23 customers asked for a dark mode this month" is a number the client can act on. One line each in the log makes that count possible.