Skip to main content
All posts

Newsletters

How to get newsletter feedback without "hit reply"

By 7 min read

Most newsletters end with some version of "Hit reply and tell me what you think". A few readers do, and their replies are often the best part of the week. But they come from the same handful of people, and you never hear from the thousands who opened the issue, read half of it and moved on.

This post covers the ways to get newsletter feedback that ask less of the reader, where each one works, and what it can and can't tell you.

The short answer

"Hit reply" only hears from your most committed readers. Add ways to answer that take one click: a poll or rating links in the email, a short question at the end of the web version of each issue, and a standing feedback link in the footer. Email clients don't run embedded surveys, so anything more than a click happens on the web. In-email clicks are tied to the subscriber; a question on the web page can be anonymous.

Why "hit reply" is not enough

  • It takes effort. Writing an email, even a short one, is a much bigger ask than a click.
  • It feels personal. Many readers don't want to write to a person they don't know, especially to say something critical.
  • It hears from the extremes. Replies come mostly from fans and from readers who are annoyed.
  • It is hard to count. Twelve thoughtful replies don't tell you whether the issue worked for most readers.

Keep the invitation to reply. Just don't make it the only way to answer.

One-click feedback inside the email

The simplest feedback in an email is a set of links, each one a vote. "Was this issue useful? Yes / No" or "Rate this issue: Great / OK / Not for me". Each link goes to a thank-you page, and your email platform counts the clicks.

Some platforms build this in. In Ghost, the "Ask your readers for feedback" setting lets readers react at the bottom of each newsletter, and shows the reactions in each post's analytics. beehiiv has polls that subscribers vote on from the email, with results in the post's analytics.

  • Clicks are tied to the subscriber. Email links carry a code that tells the platform who clicked. Ghost, for example, shows each member's feedback on their profile. That is useful if you want to follow up, but readers are less likely to be blunt when their answer has their name on it.
  • Some clicks aren't people. Security filters at some companies open links in incoming email to check them, which can record a vote nobody cast.
  • One click is all you get. You learn that a reader didn't like the issue, not why.

Why the survey itself can't go in the email

You might want the full survey inside the email: a question, then a follow-up, then a comment box. Email clients don't allow it. Most of them strip out scripts, forms and iframes, which is what embedded surveys are made of.

So an embedded survey, from any tool, only appears on the web. Newsletter platforms that publish each issue as a web page leave the embed out of the email and show it on that page. Anything beyond a single click has to happen there.

Ask on the web version of each issue

Most newsletter platforms publish every issue as a web page too. Put a short question at the end of that page, and link to it from the email: "Tell me what you thought of this issue" next to your reply line.

This has three advantages over clicks in the email:

  • You can ask a follow-up. "Was this issue useful?" then "What would you like more of?" with a few options, then an optional comment.
  • Answers can be anonymous. A survey on the web page doesn't need to know who the reader is, so readers can be more candid.
  • It reaches non-subscribers too. Issues that get shared or found through search collect feedback from people who might subscribe.

The catch is the extra click. Fewer readers go to the web page than open the email, so expect fewer answers, but each one tells you more.

What to ask, and where

What you want to knowWhere to askHow often
Did this issue work?One-click links or a poll in the emailEvery issue
Why, and what to changeA question on the web versionEvery issue
Frequency, length, sectionsA feedback page linked from the footerAlways there, mentioned a few times a year
Detailed opinions"Hit reply" or a short call with a few readersWhen you plan a big change

Example

Example: a weekly newsletter on Ghost

Say you write a weekly newsletter about home cooking on Ghost, with a recipe, a technique and a few links each week. Replies come from about the same ten people, who all love the technique section.

You turn on Ghost's feedback option in the newsletter footer, and add a line under your sign-off: "Got a minute? Tell me what you thought of this issue", linking to the issue's web page. That page ends with "Was this issue useful?", then "Which part did you use?" with the options "The recipe", "The technique", "The links" and "None of it".

After six issues, the footer reactions are mostly positive, which matches the replies. The web answers say something new: "The links" is picked far less often than the other two, and two comments say they are too long to get through. You cut the links to three and move them to the end. Your ten regular repliers never mention the change.

Where Asklet fits

Asklet works on the web version of your newsletter. On beehiiv, you add the snippet to a post with an HTML Snippet block; on Ghost, with an HTML card or once in your theme for every post. Like any embedded survey, it doesn't appear in the email itself. Platforms that don't allow iframes on their pages, such as Substack, can't host it.

Readers answer anonymously, without signing in, and the answers come back per issue, by the path of each web page. Because it doesn't know who the reader is, you can't follow up with them or split answers by subscriber. Use your email platform's own polls for that.

Your next steps

  1. Keep "hit reply", and add one-click links

    A two-option vote at the end of each issue, or your platform's own poll or feedback option.

  2. Add a short question to the web version

    One quick question, one follow-up, and an optional comment, the same on every issue.

  3. Link to it from the email

    Next to your reply line, with a plain invitation to tell you what they thought.

  4. Put a feedback link in the footer

    For questions about the newsletter as a whole, mentioned in the body a few times a year.

  5. Read the answers before you plan the next month

    Look for the section or format that keeps coming up, and change one thing at a time.

Try these steps on your own site. Asklet adds the questions to every page with one snippet. Free plan, no card needed. Compare the plans.

Start free

Common questions

Can I put a survey inside a newsletter email?

Only as links. Email clients remove the scripts, forms and iframes that embedded surveys need. You can add one-click links or your platform's poll, and link to a web page for anything longer.

Is in-email newsletter feedback anonymous?

Usually not. Email links carry a code that tells your platform which subscriber clicked, so a vote is tied to the reader. A question on a web page can be anonymous, because the page doesn't know who the reader is.

Does Asklet work in beehiiv and Ghost emails?

No. Asklet appears on the web version of your posts, not in the email. On beehiiv you add it with an HTML Snippet block, and on Ghost with an HTML card or a theme edit.

How often should I ask for newsletter feedback?

Ask about the issue every time, in one click, so it becomes a habit. Ask about the newsletter as a whole through a standing link, and mention it a few times a year.

Sources

More from the blog

Get your first answers today.

Set-up takes a few minutes, and the free plan covers one website or app.

Start free

Free plan, no card needed.

en