Email templates for telling a customer their feedback shipped

The email that tells a customer their feedback shipped has 4 parts: their own words quoted back, one line on what was built, where to find it and a question that invites a reply. It is short, it is personal, and it goes to the people who asked rather than to everyone. Three templates follow, with subject lines, for the 3 situations that come up.

The reason to send it is simple. A customer who gave feedback and heard nothing learns that feedback disappears. A customer who hears back with their own words quoted learns the opposite, and usually replies. That reply is the next round of feedback. This is what closing the loop means in practice.

Template 1: One customer, one request

Use when a specific person asked for a specific thing and it shipped.

Subject: You asked for this. It's live.

Hi [First name],

A while back you told us:

  "[Their words, verbatim, one or two sentences]"

That's now built. [One sentence on what changed, in their terms.]
You'll find it at [where: a screen name or a link].

Did this solve it for you? Reply and tell me either way. A
"not quite" is as useful as a yes.

[Your name]
[Company]

Template 2: Several customers asked for the same thing

Use when a priority had many voices behind it. Each recipient still gets their own quote.

Subject: The [feature] you asked about shipped this week

Hi [First name],

You were one of [N] people who told us [the problem, in one line].
Your words were:

  "[Their words, verbatim]"

It shipped on [date]. [One sentence on what is different now.]
[Where to find it.]

If it doesn't do what you needed, reply and say so. It's the
fastest way to get the next version right.

[Your name]

Template 3: It shipped differently from what they asked

Use when the request was heard but the build took another route. Say so.

Subject: About the [feature] you asked for

Hi [First name],

You asked for [their request, in their words]. We built something
close but not identical: [what shipped and why the difference].

For what you described, "[their words]", the way to do it now is
[the steps or the screen].

If that doesn't cover it, reply and tell me what's missing.

[Your name]

Subject lines that get opened

• You asked for this. It's live.
• The thing you mentioned about [X] is fixed
• Your feedback shipped
• About [feature], the one you asked for

Avoid "Product update" and "What's new". Those are release-note subjects, and the customer you are writing to has already learned to skip them.

When to send it

The day it ships, or the day after. Not with the monthly newsletter. The message's power comes from being about one thing and arriving while the customer still remembers asking.

What makes it work

• Their words, verbatim. Not a paraphrase. The quote is the proof you listened.
• One thing. One request, one change. Two changes is a release note.
• A question at the end. "Did this solve it?" turns a broadcast into a conversation.
• A person's name. From a founder or a PM, not from noreply.

Doing this without the afternoon of admin

The hard part is never the writing. It is finding who asked, finding their words, and sending 23 separate emails.

Annsa does this from the spec. When a spec is marked Shipped, Share Back lists every eligible customer with their email, name where known, and their original quote. Add a note of up to 300 characters or use the default, uncheck anyone you want to skip, and approve once. The email goes out under your company name and logo, quotes the customer back, and ends with "Did this solve it for you?" and two buttons, Yes and Not yet, with the answer recorded against the spec. A yes is the outcome. A not-yet is the start of V2.

Eligibility today is customers who submitted through an Annsa survey and have an email on file; feedback that arrived by CSV, API or transcript does not carry contact details, so those customers are not in the list. For them, the templates above are the fallback.