Feedback Request Email Templates You Can Copy
A feedback request works when it asks one thing, at the right moment, of the right person. This guide gives you copyable templates for five feedback goals, explains when each one fits, and shows what sending them from a CRM costs.
The short answer
For a sales or account team that already tracks customers as contacts, Close is the most direct pick for sending feedback requests, because replies and context stay on the contact record. The Essentials plan costs $49 per user per month, or $35 per user per month billed annually, and includes email, built-in forms and a centralized inbox. If you need bulk sends and automated workflows, which most feedback programs eventually require, the Growth plan is the one to budget for: $109 per user per month, or $99 per user per month billed annually. A solo operator can start on the Solo plan at $19 per month, or $9 per month billed annually.
Close offers a 14-day free trial with no credit card required. No ongoing free plan is listed on its pricing page, so plan for a paid subscription once the trial ends.
What a feedback request has to do
Most weak feedback emails fail for the same reasons. They ask several questions at once, they arrive before the customer has used the product, or they ask for a favor with no stated purpose. A good request does four things. It names one goal, it fires after an event the sender can measure, it makes the ask in the first two lines, and it tells the reader how long the response will take.
Keep the goals separate. A rating request, a churn question and a feature idea are three emails, not one email with three sections. When you bundle them, the reader has to decide which part to answer, and most readers answer none of it. Separate goals also make the replies easier to sort, because each template has a single purpose you can tag.
The templates below use square brackets for fields you replace before sending. Keep the bracketed fields that refer to the customer's own situation, such as the feature they used or the ticket they raised. Generic copy that could go to anyone reads as a mass mailing, and the customer treats it as one.
Five feedback requests and their templates
Net Promoter Score (NPS)
NPS asks one question: how likely the customer is to recommend you to a colleague, on a scale from 0 to 10. Send it after the customer has had enough time to form a view, typically once they have been active for a few weeks or have completed a major milestone. Keep the question as the first line of the body so the reader can answer by replying directly.
Subject: One question about your last few weeks with [Product]
Hi [first name], one quick question: on a scale from 0 to 10, how likely are you to recommend [Product] to a colleague?
Reply with a number. If you have a minute, add one sentence about what drove your score. Both are useful, and you can skip the second part.
Thanks, [name], [role]
Product review request
A review request belongs after the customer has achieved something specific with the product, not on a fixed calendar date. Name the outcome in the email, because a customer who sees "the export feature you set up in March" can write a useful review, while a customer who sees "how are we doing?" usually cannot. Link directly to the review page so the reader is one click from the form.
Subject: Would you share two sentences about [Product]?
Hi [first name], you have used [Product] since [month], and you set up [specific workflow] in [month]. If that has helped your team, would you write a short review?
Two or three sentences is plenty. Here is the review page: [link]
Thanks either way for the time you have put into this. [name]
Customer satisfaction after support (CSAT)
A CSAT request measures one interaction, so it should go out soon after the ticket closes, usually within 24 hours while the customer still remembers the exchange. Ask about that specific interaction. A question about overall satisfaction with the company belongs in a different email, sent on a different schedule.
Subject: How did we do on your question about [topic]?
Hi [first name], we closed your request about [topic] on [date]. Was the answer clear and useful?
Reply yes or no. If something was missing or slow, add a line and we will look into it.
[name], [support team]
Cancellation or downgrade feedback
This email goes out at the moment of cancellation or downgrade, and its tone decides whether the customer ever comes back. Keep it short, do not argue with the decision, and offer one multiple-choice question with a free-text option. The goal is the reason, not a win-back pitch in the same message. A separate win-back email can follow later, if the customer has not replied or asked to be left alone.
Subject: Before your account closes: one question
Hi [first name], we are sorry to see you go. Which of these was the main reason?
a) Price b) A feature we lack c) Switched to another tool d) Something else
A single reply is enough, and a note on the detail is welcome. We read every reply.
[name]
Feature idea collection
A feature request email works best when it is tied to a real decision, such as an upcoming roadmap review or a planned change to the product. Ask one open question and say what you will do with the answers. Customers answer more usefully when they know their idea will be read, and they stop answering when the request sounds like a survey for its own sake.
Subject: What should we build next for [use case]?
Hi [first name], we are planning the next quarter, and you know [use case] better than most people. What is the one thing that would save you the most time?
Reply in a sentence or two. We read each reply and share the common themes in the next product update.
[name]
Where to send them from
The templates above work from any email sender, but the sending tool determines what happens after the reply. You need a place where the response lands against the right customer, where you can route it to an owner, and where you can stop sending to someone who has already answered. The table below compares the three common approaches. Prices appear only for Close, because this page only lists verified pricing for that tool.
| Approach | Best for | Starting price on this page | Key limitation |
|---|---|---|---|
| CRM with bulk email and workflows (Close) | Teams sending feedback to contacts they already manage | From $9 per user per month, billed annually (Solo) | Priced per user; calling and SMS usage is billed at cost on top |
| Dedicated survey or feedback platform | Longer surveys and research questions with analysis | Not priced on this page | Often a separate system from your customer records |
| Your existing email sender with a form link | Small lists and one-question asks | Not priced on this page | You build the reply routing, suppression and reporting yourself |
Close
Close is a sales CRM with email, calling, SMS, built-in forms and a shared inbox. For feedback requests, the advantage is that the message, the reply and the account history sit on one contact record. A support or success manager who receives a low score can see the account's recent activity without switching tools, and a churn reply can be routed to the account owner in the same place.
The strengths for this audience are clear. The Essentials plan includes email, forms, team collaboration and a centralized inbox with a task list, so a small team can send single-question asks and act on replies without extra software. The Growth plan adds automated workflows and bulk email, which is what you need to trigger a review request after a milestone or a CSAT email after a closed ticket across many contacts.
The limitations matter as much. Close is built around sales and account work, not survey research. If your main job is detailed questionnaires with statistical analysis, a dedicated survey platform fits better, and Close should handle the follow-up rather than the research. Pricing is per user, so the cost grows with the size of the team that needs access, not the size of your customer list. Before you commit, confirm on the Close pricing page that the specific features you plan to use are in the plan you choose.
Close's pricing page is at close.com/pricing.
Dedicated survey tools and plain email senders
A dedicated survey or feedback platform suits research projects, longer instruments and anything that needs response analysis built in. The cost of that fit is a second system: replies live in a survey tool, customers live in a CRM or billing system, and somebody has to connect them. If you use a separate survey tool, pass only the customer identifier and the trigger into it, and bring the response back as a single field on the customer record.
A plain email sender with a link to a form is the cheapest route for a small list and a single question. It does the job if you keep the lists clean and the replies manageable. The drawback is that everything after the send is manual: you route replies yourself, you suppress people who have already answered yourself, and you build the reporting yourself. This route is fine for a founder sending to a few hundred customers. It stops working once several people need to act on the replies.
What Close costs for a feedback program
Close prices per user per month, with monthly and annual billing. The table below shows the cost for one, three and five users on the plans most feedback programs use. Figures are list prices before any calling or SMS usage, which Close passes through at cost. Annual totals are the monthly annual rate multiplied by 12.
| Team size | Plan | Billed monthly | Billed annually (per month) | Annual total when billed annually |
|---|---|---|---|---|
| 1 user | Solo | $19 | $9 | $108 |
| 1 user | Essentials | $49 | $35 | $420 |
| 1 user | Growth | $109 | $99 | $1,188 |
| 3 users | Essentials | $147 | $105 | $1,260 |
| 3 users | Growth | $327 | $297 | $3,564 |
| 5 users | Essentials | $245 | $175 | $2,100 |
| 5 users | Growth | $545 | $495 | $5,940 |
Read the table with the workflow in mind. A team that only sends single asks by hand can often stay on Essentials. A team that wants a review request to fire automatically after an onboarding milestone, or a CSAT email to go out whenever a ticket closes, needs Growth, because automated workflows and bulk email sit in that tier. The Scale plan, at $149 per user per month or $139 billed annually, adds role-based access, lead visibility rules and unlimited call recording retention. Choose it only if your feedback program has to control who sees which accounts.
Close also allocates AI credits per user each month: 500 on Solo, 1,000 on Essentials, 1,500 on Growth and 2,000 on Scale. Use the credits for drafting and summarizing, and keep the templates in this guide as the base copy so the message stays specific to the goal.
How to choose
Start from the question you need answered, not the tool you already have. If the feedback is about the customer relationship and you need the reply on the contact record, the decision is simple. If the feedback is research with a sample and analysis, the decision points elsewhere. The table below turns the common cases into a direct choice.
| If you need | Pick | Because |
|---|---|---|
| Feedback sent to contacts you already manage in a sales or account process | Close, Essentials or Growth | Replies and context stay on the contact record and can be routed to an owner |
| Bulk sends or automated triggers from the CRM | Close, Growth | Bulk email and automated workflows are in this tier |
| Access limits by role, or control over which accounts each person sees | Close, Scale | Role-based access and lead visibility rules are in this tier |
| A one-off survey to a list, with analysis | A dedicated survey platform | Built for question design and response analysis |
| One question to a small list, sent by a founder | Your existing email sender with a form link | Low cost and low setup, as long as the volume stays manageable by hand |
| A solo operator working one customer list | Close, Solo | The core CRM is priced for one operator at $19 per month, or $9 billed annually |
Setup checklist before the first send
Most feedback programs fail in setup, not in copy. The checklist below is the order that avoids the usual mistakes: sending to the wrong people, sending twice, and collecting replies nobody reads. Work through it once for each feedback goal.
| Step | What to set | Done when |
|---|---|---|
| 1. Name the goal | One goal per template: rating, review, support quality, churn reason or feature idea | Each template has one goal and one ask |
| 2. Define the trigger | An event or status you can measure, such as ticket closed, milestone reached or cancellation recorded | The trigger fires without someone checking a spreadsheet |
| 3. Set a suppression rule | Exclude contacts who have already answered this goal, and those on an open support issue | A contact cannot receive the same request twice in your chosen window |
| 4. Route replies to an owner | One person or queue per goal, such as support for CSAT and account owners for churn | Every reply has a named owner who sees it |
| 5. Tag the response | A short tag for the goal and the outcome, such as promoter, detractor, or reason for leaving | You can count responses by goal without reading each one |
| 6. Test on yourself | Send the email to an internal address first, through the exact trigger you plan to use | The bracketed fields fill in correctly and the link opens the right page |
| 7. Set a review date | A calendar reminder to review replies and adjust the template | The first review date is on the calendar before the send goes live |
Timing feedback requests
Timing matters more than copy for most feedback goals. A request that lands before the customer has used the product reads as careless, and a request that lands long after an event loses the detail that made it useful. Tie each template to a trigger you can measure rather than to a fixed date on the calendar.
- After delivery or first use: the review request fires once the customer has reached a specific outcome, not on the day of delivery.
- After a support ticket closes: the CSAT request goes out within 24 hours, while the interaction is still fresh.
- After onboarding or a milestone: the NPS request fits after the customer has completed setup and used the product for a while.
- On cancellation or downgrade: the churn question goes out at the moment of the change, in a short message that does not argue.
- On a fixed cadence: the broader relationship survey, if you run one, goes out quarterly or twice a year, and only to contacts who have not received another feedback request recently.
Limit the total number of feedback emails each customer receives. A customer who gets a CSAT email, an NPS email and a review request in the same month is likely to ignore all three. Put a suppression window on the whole program, not just on each template.
Closing the loop
The reply is not the end of the feedback process. Customers who answer expect the answer to matter, and most will notice if nothing changes. Closing the loop is a set of small, specific actions that you can repeat with every program.
- Thank responders: a short reply that names what they said, not a generic thank-you.
- Follow up on low scores: an account owner or support lead contacts the customer personally, within a set number of days you choose.
- Report back on themes: a short note in the next product update or newsletter naming the requests you acted on.
- Record the decision: when you decide not to act on a request, log the reason so the same idea does not come back unanswered.
Incentives and response bias
Small thank-yous are common and usually acceptable. Larger rewards tend to attract people who are there for the reward, and that shifts your sample. A prize draw in particular can pull in respondents who would not otherwise answer, which makes the results harder to read. If you offer an incentive, state the terms plainly and keep a sample of customers who receive the same request without it, so you can compare the two groups.
Check any reward you promise against its current terms on your own offer page before you publish the email. A promise that has expired, or that the customer cannot claim, damages trust more than having no incentive at all.
A 30-day rollout
A rollout that spreads the work over a month is more likely to stick than one that launches five templates at once. The plan below assumes one person owns the program and a CRM or sender is already in place.
- Days 1 to 3: choose the first feedback goal, decide the trigger and write the owner's name on every reply.
- Days 4 to 8: build the two templates you need first, usually a one-question email and a two-question check-in, then review them against the checklist above.
- Days 9 to 14: test the triggers with internal addresses and confirm the suppression rule works.
- Days 15 to 22: send to a small group, read a sample of replies and sort them into actionable and not actionable.
- Days 23 to 30: cut the template down to one ask, add the next goal only if the first one produces replies someone acts on, and document what changed.
Feedback request templates FAQ
Which tool should I pick for feedback requests?
If your feedback goes to customers you already track as contacts, and the reply needs to land on that record, Close is the most direct option in this guide. Essentials covers single asks and a shared inbox, and Growth is needed for bulk sends and automated workflows. If your main work is survey research with analysis, a dedicated survey platform fits better.
What does Close cost for a team of three?
On Essentials, three users cost $147 per month billed monthly, or $105 per month billed annually, which is $1,260 a year. On Growth, three users cost $327 per month billed monthly, or $297 per month billed annually, which is $3,564 a year. Calling and SMS usage is billed at cost on top of these figures.
Is there a free plan for Close?
Close offers a 14-day free trial with no credit card required. No ongoing free plan is listed on its pricing page at the time of writing, so budget for a paid plan once the trial ends. Check the pricing page directly before you start, because plan details can change.
When is the best time to send a feedback request?
Send each request after a measurable event that the customer has experienced. For a review, that means after they have reached a specific outcome. For a CSAT request, that means within 24 hours of a closed ticket. For a cancellation question, that means at the moment of the change. A request that arrives before the customer has used the product reads as tone-deaf and does not produce useful answers.
How many questions should a feedback email contain?
One is the normal target: a single clear ask and an optional free-text field. If the subject needs more structure, link to a short second-stage survey instead of stacking questions in the email. Each extra inline question makes the email look like work, and most teams act on only a fraction of the answers they collect.
Should I offer incentives, and do they bias responses?
Small thank-yous are usually acceptable. Larger rewards can attract respondents who are there for the reward, which shifts the sample toward people who want something. If you use an incentive, keep a comparison group that receives the same request without it, and confirm the terms on your own offer page before the email goes out.
Do I need a dedicated survey tool?
Not for single-question feedback. A CRM or a plain email sender with a form link handles most one-question asks, provided you can route replies to an owner and suppress people who have already answered. You need a dedicated survey tool when the instrument is long, the sample needs weighting, or the results must be analyzed in detail.