Open rates roll in. A few clicks too. But the inbox stays the same — issue 5, issue 10, replies hover at one or two. Sometimes zero.
You start wondering if your writing is the problem.
It's not. No reply is the default.
Reply rates run 1–3%, by design
The benchmark numbers:
- Cold email reply rate (2026): 3.43%. Down from 8.5% in 2019, and dropping every year. It's a cold email benchmark — not a direct measure of newsletter replies — but it's roughly the ceiling on "% of recipients who hit reply."
- Top quartile sits at 5.5%. That's what "good" looks like on the same scale.
- Newsletter reply rates have no public stats. Newsletter platform Buttondown puts it directly: "public statistics on good or average response rates are rare, as by default they're not tracked."
So if 100 people read and 1–3 reply, that's average — and that's only when you've explicitly asked for one. Just publishing and getting a single reply is already doing well.
A publisher five issues in put it this way on r/Newsletters:
So why? Three structural reasons. None of them about you.
1. Hitting reply exposes who they are
When someone clicks reply, their email address goes through. Their name, their domain, their company — all of it.
To send a one-line reaction, a reader has to attach their full identity. The kind of "lol nice" they'd throw into a chat becomes a letter the moment it's an email.
That's not unwillingness. The cost is just too high.
2. Email is a heavy format
Email is correspondence. There's an unspoken expectation: "Hi NAME, just wanted to say…" — opening, body, sign-off.
For a reader trying to send a one-liner, matching that format costs more than the reaction is worth. So they think about replying for a moment, then close the tab.
The data backs this up. Inbox Collective reports that welcome emails with one clear question can hit a 20% reply rate. Compare that to the 1–3% baseline and the gap is huge. The difference isn't the writer's talent. It's the cost of replying. The lighter the ask, the more replies you get.
3. The reply infrastructure itself is broken
This one is almost absurd, but real.
A Substack publisher ran a self-test — sent 4 replies from their own Gmail to their own Substack newsletter. The result:
3 out of 4 didn't arrive — or arrived very late. It's a single creator's test, so don't generalize too far. But if their own emails struggle, what's happening to a casual reader's reply? Some of those replies aren't missing. They're stuck.
Substack and Beehiiv have built-in comments, but they require an account. Most casual readers won't sign up to leave one line.
So: replies are a cost problem, not a willingness problem
A quiet reader isn't disengaged. To send a one-line reaction, they have to:
- Expose their identity
- Match an email format
- Hope it actually reaches the publisher
All three have to clear before the reply lands. Miss any one, and that one-line reaction just disappears.
Reviving the reply channel means lowering all three at once — a channel where:
- The reader stays anonymous
- No login is required
- It lands directly under the post
That's why Joey exists. A link at the end of your newsletter, reader clicks → one line → done. Anonymously, no sign-up, straight to your dashboard.
It's why publishers who used to get one or two replies start seeing lighter, more frequent reactions on each issue.
Replies aren't sparse because your writing is weak. The channel is just heavy.
