How to Write Substack Notes Hooks That Get Read

Someone is three Notes into their feed, thumb already moving, when yours shows up. You have about as long as it takes to read one sentence to give them a reason to stop. Most Notes don't get that reason written into the first line, and it shows in how little of the Note ever gets read.

How do you write a Substack Notes hook that actually gets read instead of scrolled past? Part of the answer is technique, drawn from what tends to work in short-form writing generally. Part of it is measured directly from a sample of 20,000 recent Notes: multi-line Notes averaged about 11% more reactions and 28% more restacks than single-line Notes, and Notes of 150 to 300 characters beat Notes under 50 characters by roughly a third on reactions. We've kept technique and measurement separate below, since a lot of hook advice online blurs "here's a trick" with "here's what the data says," and those are different kinds of claims.

One number worth having before you start: WriteStack has close to 100 verified reviews from Substack writers across multiple platforms. The other tools in this category have none that we could find anywhere. The hook advice below is free. The part where you draft ten versions, schedule them across a week, and find out which one actually sent people somewhere is the part a tool does.

Table of Contents

• What a Hook Has to Do in the First Line
• What the Data Actually Shows About Length
• Why "Ask a Question" Isn't the Guaranteed Win It Sounds Like
• Five Hook Techniques Worth Testing
• Hooks That Promise and Don't Pay Off
• A Simple Process for Writing a Hook
• What Happens to a Hook After You Post It
• What Changes After Thirty Hooks

What a Hook Has to Do in the First Line

People scan rather than read on the web. Research from the Nielsen Norman Group found that 79% of test users scanned any new page they came across, and only 16% read word by word, with the first few words of a line carrying most of the weight for whether someone keeps going. Notes compress that further: there's no headline, no image doing the work, just the first line sitting in a fast-moving feed next to dozens of other first lines.

A hook's job is narrow. It has to earn the second sentence, not summarize the whole Note. If the first line is trying to make the entire point, there's nothing left to pull someone into the second line, and the Note reads as finished before it started.

Practical rule: Write the first line last. Draft the Note, find the sentence in it that would make you stop scrolling, and move that one to the top.

A hook doesn't have to be dramatic. It has to be specific enough to stand out from the surrounding text in the feed, which is a lower bar than most writers assume, since most Notes open with a generic statement that could apply to almost anyone's account.

Specificity is also the part that's hardest to produce on demand at 11pm, which is where the drafting tool you use starts to matter. Most AI writing tools generate a hook from a prompt, which is why the output arrives sounding like a LinkedIn post and takes three rounds of editing to sound like you. WriteStack's Notes generator drafts from Notes and posts you have already published, so the opening line comes back in your own phrasing and rhythm instead of a generic voice you then have to sand down. If a draft misses anyway, you switch models rather than living with one fixed voice. Start a free 7-day trial and draft ten hooks in the time it takes to force one.

What the Data Actually Shows About Length

This part is measured, not theorized. Across a sample of 20,000 recent Notes, we grouped Notes by character length and looked at average reactions per group.

Length	Sample size	Average reactions
Under 50 characters	4,643	8.5
50-149 characters	5,539	10.0
150-300 characters	4,443	11.7
Over 300 characters	5,375	9.6

Notes in the 150 to 300 character range averaged roughly a third more reactions than Notes under 50 characters. In a separate comparison from the same sample, multi-line Notes (more than one paragraph break) averaged about 11% more reactions and 28% more restacks than single-line Notes. Both patterns point the same direction: a Note with enough room for a hook and one supporting line tends to outperform a bare one-liner, and a Note that's all one dense block tends to underperform one broken into a hook plus a short follow-up.

The restack gap is the one worth staring at. An 11% lift on reactions is a nicer-looking Note. A 28% lift on restacks is your Note appearing in front of someone else's subscribers, which is the only mechanism on Notes that reaches people who have never heard of you. Line breaks are close to free, and that is what they buy.

Practical rule: If your usual Note is under 50 characters, add one more sentence of context before you post it, then check what that does to your own restack rate over the next two weeks.

That last part matters, because this is a pattern in aggregate data, not a promise about any individual Note. A single short Note from an account with an engaged following can still outperform a longer one from a newer account. Length is one input among several, not a formula that overrides everything else about who's reading and what they already expect from you. Which means the only version of this finding that's worth anything to you is the version measured on your own account, and Substack's own stats page won't run that comparison. WriteStack will, against your full Notes history and against other publications your size.

Why "Ask a Question" Isn't the Guaranteed Win It Sounds Like

"Open with a question" is one of the most repeated pieces of hook advice for short-form writing, on the theory that an unanswered question creates a small itch to keep reading. We checked it against the same sample: Notes with a question mark in the first 60 characters had a median of 1 reaction, compared to a median of 2 reactions for Notes without one, in a comparison of 894 question-led Notes against 17,712 that weren't.

That doesn't mean questions are a bad hook. It means the technique isn't automatically better just because it's a question, and a lot of hook advice treats "ask a question" as close to guaranteed when the data behind that specific sample doesn't back it up. A well-aimed question can still work. A generic one tacked onto the front of a Note for the sake of following a formula is competing with the same feed as everything else, and formula alone doesn't win that.

Practical rule: If you open with a question, make sure it's one you'd actually want someone to answer in the replies, not a rhetorical one you're about to answer yourself in the next sentence.

It's worth sitting with why this might be true rather than just noting it. A question in the first line asks the reader to do something before they've decided whether you've earned their attention, and most scrolls don't survive that ask. A specific statement gives them something immediately, without asking for anything first. That's a plausible explanation, not a confirmed mechanism, since the sample doesn't tell us why, only what happened.

Five Hook Techniques Worth Testing

These are techniques, not findings. They come from what tends to work across short-form writing generally, and they're worth testing against your own Notes rather than trusting as proven.

The specific detail. A hook that names a number, a timeframe, or a concrete fact tends to read as more credible than a vague claim. "I lost 40 subscribers in a week" pulls harder than "I've had a rough week for growth," because the specific version gives the reader something to picture.

The unfinished thought. Open mid-idea, as if the reader walked into the middle of something you were already thinking about. This works because it borrows urgency from feeling overheard rather than announced.

The small confession. Admitting something you got wrong, or something you're still unsure about, tends to read as more honest than a polished takeaway, and honesty is a rarer texture in a feed full of confident statements.

The direct address. Speaking straight to the reader, "you," rather than describing a general situation, narrows the hook to feel like it's meant for the person reading it specifically.

The reframe. Naming something the reader has probably assumed, then pointing at a detail that complicates it, gives the hook a reason to keep reading without relying on shock or exaggeration.

Practical rule: Pick one technique per Note, not three stacked together. A hook trying to be specific, unfinished, and a confession all at once usually reads as trying too hard.

Start with the specific detail. It's the one on this list the length data supports directly, since a hook carrying a real number is almost always going to land in that 150 to 300 character band rather than the thin sub-50 range, and it's the easiest to check afterward because you can point at the number and ask whether it was the thing that stopped people. The other four take longer to evaluate and are better run as a rotation across several weeks.

Running that rotation by hand is where most writers quit. Five techniques across a week is thirty-five Notes a month, each one needing a draft, a slot, and a record of which technique it used. WriteStack's tagging and queue view is built for exactly that shape of work: draft the batch in one sitting, tag each Note by the technique it's testing, drop the whole set into the week, and read the results by tag instead of by memory. The alternative is a spreadsheet you'll stop updating by week three.

Hooks That Promise and Don't Pay Off

A hook that oversells what the Note actually delivers costs more than it earns. If the first line promises a secret and the Note delivers a common observation, the reader notices, and they notice on your next Note too. That's the difference between a hook and clickbait: a hook earns the read that follows it, and clickbait borrows attention it doesn't pay back.

This matters more on Substack specifically than on platforms built for one-off scrolling, since your Notes are tied to a publication readers can subscribe to or leave. A hook that overpromises once might still get a click. A pattern of it costs the thing that actually grows a Substack, which is someone deciding your name is worth following.

Practical rule: Before posting, check that the last line of the Note delivers on whatever the first line promised. If it doesn't, rewrite one of the two.

There's a simple test for this before you post: read only the first line and guess what you'd expect the rest to say. Then read the whole Note. If the gap between what you expected and what you got feels like a letdown, a reader will feel that too, and they'll remember it the next time your name shows up in their feed.

A Simple Process for Writing a Hook

1. Write the whole Note first, without worrying about the opening line.
2. Find the sentence in the draft that's doing the most interesting work, even if it's buried in the middle.
3. Move that sentence to the top and rewrite it as a standalone opener.
4. Check its length. If it's under 50 characters and reads as thin on its own, add one clause of context.
5. Read it as if you were mid-scroll and had never seen the rest of the Note. If it doesn't earn a second look on its own, it isn't the hook yet.

Practical rule: If you can't find a strong opening line anywhere in your draft, look for a missing point rather than a missing hook. A Note without a clear point rarely produces a strong opener no matter how long you search for one.

This process takes longer the first few times and gets faster once you've done it on ten or fifteen Notes. The skill that improves with repetition is spotting which sentence in a draft is the strong one, and that skill builds faster from practice than from memorizing a list of techniques.

Repetition is the constraint, though. You get good at hooks by writing a lot of them and watching what happens, which means the bottleneck isn't the technique list, it's how many hooks you can get into the feed and evaluate before you lose interest. Here is what that loop costs on each of the three ways people run it.

Running a hook test	By hand	Substack native	WriteStack
Drafts hook variations from your own published Notes	No	No	Yes, in your existing voice
Switch AI models when a draft misses	No	No	Yes
Link clicks per link, across your full Notes history	No	No	Yes
Benchmark your reactions against publications your size	No	No	Yes
Trend direction month over month	No	No	Yes
Schedule Substack chat posts	No	No	Yes, and no other tool does
See a full week of scheduled hooks at once	No	Drafts list only	Queue and calendar view
Tag Notes by which technique they're testing	Spreadsheet	No	Built in
Verified reviews from Substack writers	Not applicable	Not applicable	~100 across platforms

Start your free trial and put a week of hook variations into the queue tonight.

What Happens to a Hook After You Post It

Most hook advice ends at the moment you hit publish, which is roughly half the job. The other half is finding out which hooks did anything, and that turns out to be a harder question than the feed makes it look.

Reactions are the number Substack hands you, and reactions measure approval. A hook that gets forty likes and a hook that sends forty people to your archive are doing different jobs, and the first one is much easier to write. If what you want from Notes is subscribers rather than applause, the hook you should be repeating is the second kind, and nothing in Substack's native stats will separate them for you.

The part people don't expect

WriteStack tracks which of the two links inside a Note got clicked, going back to your very first Note, so "that hook did well" becomes "that hook sent 40 people to the archive and the one above it sent 3." It benchmarks your reaction and restack rates against other publications your size, which turns "is this good" into a question with an answer instead of a guess against your own last week. And it schedules Substack chat posts, which no other tool in this category does at all. Open the dashboard on a Tuesday and see that the confession-style hook you almost deleted drove more clicks than the six clever ones above it, and that your restack rate is running well above typical for a publication your size. Not better than last week. Better than the field.

Trend direction is the piece that changes how you write over months rather than days. A single strong Note tells you almost nothing, because Notes performance is noisy enough that any one result could be timing or luck. A restack rate climbing month over month while you rotate through the five techniques above tells you which rotation is working. That's a comparison a per-account snapshot structurally cannot make, and it's the reason the analytics layer, rather than the queue, is the part of a tool that compounds.

The live inspiration feed does the same job from the other direction. WriteStack's updates continuously from live Notes data, so the hooks you're seeing on a Tuesday are hooks that are working on Substack that week rather than a list somebody wrote once and left up.

What Changes After Thirty Hooks

Track one week before you change anything. Write down every Note you posted, its first line, and what it got. Almost every writer who does this finds the same shape: two openers they're proud of, a run of Notes that opened with whatever came out first, and no idea which of them actually moved anyone.

Thirty hooks in, the change isn't that your first lines got cleverer. It's that you stopped guessing. You know your confessions outperform your questions on your account specifically, you know your Notes land better at 240 characters than at 40, and you know it from link clicks rather than from a feeling. The writing energy that was going into staring at a blank first line goes into the idea underneath it, because the opener is a draft you edit now instead of a wall you sit in front of.

A good hook doesn't fix a Note with nothing to say, and a flat opener doesn't ruin a Note with something worth reading. It decides how many people find out which one you wrote. For more on which formats hold up across a full posting week, see our guide on Substack Notes formats that work, and the complete guide to Substack Notes covers scheduling, posting rhythm, and format together.

Drafting in your own voice, model selection when a draft misses, link-click history per Note, and benchmarks against the field are what turn hook writing from a guessing game into a loop that improves. WriteStack ships all of them together, and close to 100 verified reviews from Substack writers back that up, against none we could find anywhere for the other tools in this category.

Start a free 7-day trial. Draft ten hooks tonight. Find out on Friday which one sent people somewhere.