How to write hooks that earn the second sentence

Most Instagram hooks fail because they spend the first line on context instead of tension. On the feed, only the first 125 characters of a caption show before the 'more' cutoff, so a line that opens with a windup ('So I've been thinking lately about...') burns that visible space before any reason to keep reading appears. Hooks that earn the second sentence front-load a specific stakes, a curiosity gap, or a concrete number ('I lost 4,000 followers in one week'). They also avoid generic openers that the brain has learned to skip. A strong first line creates an open loop the reader needs closed, names a specific person or problem, and fits inside that 125-character preview window so the payoff is visible the moment someone stops scrolling.

A LinkedIn hook and a TikTok hook target different attention mechanics. LinkedIn truncates posts at roughly the first 2-3 lines (about 140-210 characters on desktop) behind a 'see more' link, so the hook is read silently and must promise a professional payoff, often a contrarian claim or a specific outcome. TikTok hooks are spoken or shown as on-screen text in the first 1-3 seconds, competing against an instant swipe, so they front-load motion, a bold visual statement, or a question the viewer answers in their head. LinkedIn rewards a single sharp line plus a deliberate line break before the fold; TikTok rewards a hook that pairs verbal and visual tension immediately. Same goal, second-sentence pull, but one is read and one is watched.

A few hook structures travel well across platforms because they exploit attention rather than a single feed layout. The curiosity gap names an outcome but withholds the how ('This one edit doubled my reach'). The pattern interrupt opens with an unexpected admission or contrarian take ('Stop posting daily'). The specific-number hook trades vague claims for hard figures ('3 words killed my email open rate'). The named-stakes hook calls out exactly who should care ('If you've ever deleted a post out of fear, read this'). Each works because it opens a loop the reader must close. The reliable test is the same everywhere: does the first sentence make the second sentence feel mandatory? If the opener could be deleted without loss, it isn't a hook yet.

LinkedIn's post box — used for feed posts, comments, your headline and your About section — is plain text with no formatting toolbar and no markdown, so there's no bold button. The workaround the whole creator economy uses is Unicode bold: type your line, convert it to bold Unicode characters (𝗯𝗼𝗹𝗱) in a generator, then paste it back and the emphasis sticks, because the style is baked into the characters themselves. Bold only the hook — the part that shows before the “…see more” cut-off — to earn the click, and keep the rest plain so the post stays skimmable. Two caveats matter: Unicode text isn't read by LinkedIn's search and is announced poorly by screen readers, so never bold the keywords, names or hashtags you want found or read aloud. For true rich text (headings, lists), use LinkedIn's separate 'Write article' editor instead.

Instagram's native composer collapses the line breaks you type, which is why captions paste in as one dense block — it's worst when you post from the web or through some schedulers. The reliable fix is to compose the caption with the spacing you want and paste it back with the breaks preserved, rather than relying on invisible-character hacks (blank Unicode characters can break Instagram's search and are read poorly by screen readers). Write the caption with your intended breaks, generate the spaced version, and paste it into the caption field. Put your strongest hook on line one, since that's the part that shows before the 'more' cut-off in the feed. Keep paragraphs short — two or three lines — so the caption stays skimmable on a phone, where almost everyone reads it.

Yes — WhatsApp is the exception among messaging and social apps because it has its own built-in markup that it renders for everyone. Wrap text in *asterisks* for bold, _underscores_ for italic, ~tildes~ for strikethrough, and triple backticks for monospace; the symbols disappear and the styling shows. So you usually don't need Unicode characters on WhatsApp at all. Reach for a Unicode formatter only when you want a style WhatsApp's markdown doesn't cover — small caps or script for a Status, say — or when you're writing one message to post across several apps that don't share WhatsApp's syntax (Instagram, X and Threads strip these symbols and show them literally). For everyday bold and italic inside WhatsApp itself, the native markup is the better and more accessible choice.