By Siddharth Gangal What sales email preview text actually is
Sales email preview text is the short snippet of copy that appears next to the subject line in the inbox preview, before the recipient opens the email. It lives in the HTML preheader of the message or in the preview text field of the sequencer, and it is usually 35 to 90 characters of visible copy depending on the inbox client. Preview text is the second most valuable surface in cold email after the subject line, and it is the one most reps ship empty.
Direct answer. Sales email preview text is the inbox snippet that pairs with the subject line to decide whether a buyer opens the message. Treat the subject and preview text as one continuous sentence split across two lines. Run the 6-Step Preview Text Pairing Loop and lift cold email opens by 11 to 19% over an empty preheader (Gangly customer benchmark, 2026).
Sales email preview text. The inbox snippet, usually 35 to 90 characters, that renders next to the subject line of a sales email before the recipient opens it. It is set explicitly via the preheader or the sequencer preview field and pairs with the subject line as one continuous hook in the inbox of every prospect on the cold email sequence.
The rest of this guide ships the framework, the length rules, the pairing patterns, the testing protocol, and the examples by sales motion. It assumes you already run a working first sequence and care about open rate as the primary leading indicator. If subject lines are still the bottleneck, start with the cold email subject lines guide before tuning the preview text.
Why preview text moves open rates more than reps think
Preview text moves open rates because the inbox triage happens in seconds. The Litmus State of Email Engagement (2025) reports that 47% of B2B opens are decided in under three seconds, from a scan of three elements: the sender name, the subject line, and the preview text. The subject line and sender name are the first two inputs; the preview text is the tiebreaker. Reps who ignore it ship every cold email with the tiebreaker blank.
11-19%
open-rate lift from a paired preview text
Reps using a signal-tied preview text vs. an empty preheader (Gangly customer benchmark, 2026).
35-90ch
visible preview text across major clients
Apple Mail shows 90 chars on iPhone; Gmail mobile clips at 35 to 40 (Litmus Email Client Market Share, 2026).
24%
of cold emails ship with no preview text at all
Audit of 4,200 outbound sequences across Gangly customer accounts (Gangly product telemetry, Q2 2026).
47%
of B2B opens decided in under 3 seconds
Inbox scan time from subject + sender + preheader (Litmus 2025 State of Email Engagement).
The economics are simple. A cold sequence sent to 1,000 prospects at a 28% open rate produces 280 opens. The same sequence with a paired preview text at a 35% open rate produces 350 opens — 70 more buyers triaging the message in their head, on the same volume, on the same domain reputation. The lift compounds across the cadence because open rates on touch 2 and touch 3 are conditioned on the engagement signal from touch 1 (Gong State of Sales Engagement, 2025).
The Bridge Group outbound benchmark report tracks open rates by industry segment: industrial averages 22 to 28%, B2B SaaS averages 30 to 38%, financial services averages 18 to 24% (Bridge Group Outbound Benchmarks, 2025). Reps inside each segment who pair the preview text consistently land in the top quartile of their band; reps who ship empty preheaders land in the bottom quartile. The preview text is not a tiebreaker between great teams. It is the difference between an average open rate and a top-quartile open rate inside the same segment.
The anatomy of a high-performing preview text
A high-performing preview text does three things in 35 to 50 characters: it continues the subject line, it names a number or a noun, and it earns the open. Continuation prevents repetition. A number or noun gives the buyer a concrete fact to weigh. Earning the open means the preview text raises the question the email body answers, not the answer itself.
Preheader. The hidden HTML element near the top of the email body that inbox clients read to render the preview text snippet. In sequencers like Outreach, Salesloft, Apollo, Instantly, and Smartlead, the preheader is exposed as the "preview text" field, so reps rarely touch the raw HTML. Set this field on every send.
| Element | Purpose | Character budget | Example |
|---|---|---|---|
| Continuation | Picks up where the subject ended; reads as one sentence with the subject | First 12 to 18 chars | "How three peers cut..." |
| Specific noun or number | Anchors the message in a concrete fact the buyer can weigh | Chars 18 to 35 | "...30-day ramp by 60%" |
| Open question | Raises the question the body answers, never the answer itself | Chars 35 to 60 | "Worth a look?" |
| Tail context | Optional; gives Apple Mail readers extra context on the iPhone 90-char window | Chars 60 to 90 | "Two slots Thursday." |
The strongest preview texts use only the first three elements. Tail context is optional and exists because Apple Mail on iPhone shows up to 90 characters and Outlook on desktop shows 50 to 75. Most readers never see it. Optimize for the first 35 characters and treat the rest as a bonus surface, not a primary one.
Common trap. Reps stuff the preview text with the call to action ("Open to a 15-min chat?"). The CTA belongs in the body, not the inbox. The preview text earns the open; the body earns the meeting. Conflating the two trains the buyer to ignore the inbox scan.
The 6-Step Preview Text Pairing Loop
The 6-Step Preview Text Pairing Loop is the named framework Gangly customers use to ship a paired preview text on every cold send. It runs as a closed loop: a draft email enters at Step 1, exits at Step 6, and the rendered subject + preview text combination is the gate that decides whether the message ships. Skip any step and the open rate falls back to the bottom-quartile band.
- 1
Pull the matching signal
Open the prospect record and find the freshest buying signal in the last 14 days. Funding round, hiring spike, leadership change, pricing-page visit, competitor post. The preview text is built from this signal, not from a template library. If there is no signal, the preview text reverts to a value-tied teaser, never a recycled benefit statement.
- 2
Draft the subject line first
Write the subject line before the preview text. Subject lines work alone in many clients; preview text rides on top. Lock the subject to 4 to 7 words, then layer the preview text underneath so the two read as one complete sentence in the inbox preview.
- 3
Pair the preview text as a continuation
The preview text continues the subject. If the subject names the signal, the preview text names the outcome. If the subject names the role, the preview text names the question. The goal is one sentence split across two lines, not two separate hooks fighting for attention.
- 4
Front-load the value in the first 35 characters
Mobile clients clip at 35 to 40 characters. Anything past that disappears on a phone. Put the keyword, the named entity, or the number inside that first window. Save the throwaway connectors (a, the, this, here) for the second half.
- 5
Strip the auto-pull text
Most email tools fall back to the first line of the body when the preview text is empty. That fallback is almost always a greeting ("Hi [First name],"). Set the preview text explicitly in the sequencer so the fallback never ships. A blank preview text field is a publish blocker.
- 6
Audit it in three clients before sending
Send a render test to Gmail desktop, Gmail mobile, and Apple Mail. Read the subject + preview text combination in each. If any one reads as two disjoint phrases or clips a critical word, rewrite. Inbox preview is the only render that matters.
The loop is opinionated on two points. First, the preview text is never written alone — it is written as a continuation of the subject line. Second, the render test is a publish blocker, not a nice-to-have. Hold both points and the loop consistently lands a paired preview text on 96% of sends (Gangly product telemetry, Q2 2026). Drop either point and the field reverts to the auto-pulled greeting fallback within a week.
Fast tip. Build the render test into the sequencer as a pre-send check, not a manual habit. A single render check that runs against three saved inbox profiles takes 8 seconds per email and catches 70% of preview-text misfires before the buyer sees them.
Preview text length rules across inbox clients
Preview text length rules vary by inbox client, and the variance is wide enough that a 90-character preview text reads great on iPhone Apple Mail and gets clipped at "How three peers cut a..." on Gmail mobile. The Litmus client market share data is the source of truth for the budget. The table below is the version Gangly customers use as the working reference.
| Inbox client | Visible preview text | Share of B2B opens | Optimization priority |
|---|---|---|---|
| Apple Mail (iPhone) | Up to 90 characters | 34% | High; tail context lands here |
| Gmail (mobile) | 35 to 40 characters | 22% | Critical; must-read window |
| Gmail (desktop) | 75 to 90 characters | 14% | Medium |
| Outlook (desktop) | 50 to 75 characters | 11% | Medium |
| Apple Mail (Mac) | 110 to 140 characters | 9% | Low; tail context safe |
| Outlook (mobile) | 30 to 45 characters | 5% | Critical; must-read window |
| Other clients | Varies | 5% | Low |
The math points to a clear rule: every preview text must land its core message inside the first 35 characters because 27% of B2B opens happen on Gmail mobile or Outlook mobile (Litmus Email Client Market Share, 2026). The next 35 characters are bonus surface for Apple Mail on iPhone. Beyond 90 characters is wasted budget — write the body instead.
Email deliverability. The set of factors that decide whether a cold email lands in the primary inbox, the Promotions tab, or the spam folder. Open rate, paired preheader text, and authenticated sending domain all feed the engagement score that inbox providers use to grade future sends. See the email deliverability glossary for the full chain.
Subject line and preview text pairing patterns
Subject line and preview text pairing patterns fall into four working shapes. Each shape pairs the two surfaces as one sentence: the subject names the hook and the preview text either completes it, counters it, qualifies it, or quantifies it. The four shapes below cover roughly 90% of high-performing B2B cold opens.
| Pattern | Subject (4-7 words) | Preview text (35-50 chars) | When to use |
|---|---|---|---|
| Continuation | "Series B + 30-day ramp" | "How three peers cut hiring drag" | Funding or growth signals |
| Counter | "Outbound is broken at scale" | "Three fixes that work in 30 days" | Pain-led openers; trigger curiosity |
| Qualifier | "New VP of Sales + 90 days" | "Day-one playbook, 30-min ramp" | Leadership changes; first-90-day context |
| Quantifier | "Saw [Company] on pricing" | "Two questions usually decide it" | Engagement signals; high intent |
The continuation pattern is the highest-volume shape in B2B because most signals are growth-tied. The counter pattern works on second-touch retargeting where the buyer has already ignored a continuation. The qualifier pattern is the right fit for leadership-change signals where the preview text earns the open by naming the timeline the new VP cares about. The quantifier pattern is reserved for high-intent signals where the buyer is already researching.
Verdict. If you can only run one pattern across the sequence, run the continuation. It is the lowest-risk, highest-volume shape and it teaches the rep to write subject and preview as one sentence. Add the other three patterns once the continuation is consistent at the 30%+ open-rate band.
Preview text mistakes that kill open rates
Preview text mistakes show up in the data fast — a 30-day drop in open rate, an unexpected lift in unsubscribe rate, or a flat reply rate across a rewritten sequence. The five mistakes below cover roughly every preview text failure pattern Gangly customers see in inbound audits.
- 1
Shipping the field empty
Empty preview text falls back to the first line of the body, which is almost always a greeting. The inbox preview reads "Hi [First name], hope this finds you well," which signals automation and lowers opens by 9 to 14%.
- 2
Repeating the subject line
A preview text that paraphrases the subject burns the second surface. The two should function as one sentence, not two attempts at the same hook. Repetition reads as templated.
- 3
Front-loading filler words
Preview text that starts with "Just wanted to share..." or "Quick note about..." wastes the must-read 35-character window. The keyword, noun, or number must land inside chars 1 to 35.
- 4
Stuffing the CTA into the preview
"Open to a 15-minute chat Thursday at 2pm?" belongs in the body. Putting it in the preview text trains the buyer to skip past the open and treat the inbox scan as a calendar invite.
- 5
Hard-coding [First name] or [Company] without testing
A broken merge token in the preview text — "Hi [First name]" rendered literally — is a deliverability landmine. Run the render test on every variant, every time.
Spam compliance. Preview text must not include deceptive claims, fake "RE:" prefixes, or false urgency markers. The FTC CAN-SPAM Act compliance guide treats the preheader as part of the deceptive header rules. Honest, signal-tied preview text passes; "Your account has been flagged" does not.
Testing and measuring preview text performance
Testing preview text performance requires a clean A/B setup because the variable is small and easily masked by other inputs. The protocol below is the one Gangly customers use to isolate the preview text contribution from the subject line, the sending domain, and the day-of-week effect.
Test design
Hold the subject line constant. Vary only the preview text. Run two cohorts of 500 sends each, randomized by prospect ID inside the same campaign. Send both cohorts on the same day, in the same hour, from the same domain. Compare open rates after 72 hours. A statistically significant lift requires at least 100 opens per cohort, which sets the minimum sample at 350 sends per arm at a 30% open rate.
Metrics that matter
Pros
- ✓ Open rate by cohort, measured at 72 hours
- ✓ Reply rate downstream — checks that opens convert
- ✓ Unsubscribe rate — flags overpromised previews
- ✓ Spam complaint rate — caps deliverability damage
Anti-metrics
- ✗ Click-through rate: preview text does not move CTR
- ✗ Meeting-booked rate: too far downstream to attribute
- ✗ Revenue per touch: confounded by deal size and stage
- ✗ Open rate measured under 48 hours: too noisy
Open rate is the only direct measure of preview text contribution. Reply rate is a useful downstream check: a preview text that lifts opens but tanks replies is overpromising. Unsubscribe and spam complaint rates are the safety guardrails — a lift in either signals that the preview text is misleading buyers into opening, not earning the open. Read the four metrics together, never in isolation. Track them inside the same dashboard as your cold email metrics.
Fast tip. Reset the test cadence once a quarter. Inbox provider algorithms shift, mobile-share of opens drifts, and the winning preview text from Q1 is usually not the winning text in Q4. A 90-day re-test cycle keeps the rule current.
Preview text examples by sales motion
Preview text examples by sales motion cover the four most common B2B contexts: signal-led outbound, account-based selling, founder-led sales, and inbound follow-up. Each example uses the continuation pattern as the base shape and a real signal as the pairing fuel. Treat these as starting points, not templates to reuse verbatim.
Motion 1: Signal-led outbound (funding round)
Subject: Series B + 30-day ramp
Preview text: How three peers cut hiring drag in 30 days.
The subject names the signal and the timeline. The preview text continues the sentence by naming the peers and the outcome. Open rate in pilots: 38% versus a 27% control with empty preview text on the same list.
Motion 2: Account-based selling (new leadership)
Subject: New VP of Sales at [Company]
Preview text: Day-one playbook, 30-minute ramp.
The subject names the role change and the company. The preview text earns the open by naming the playbook and the ramp time. Pair with a signal-based outreach motion for best results.
Motion 3: Founder-led sales (cold introduction)
Subject: Built this for teams like yours
Preview text: 90 seconds on why it works.
The subject signals founder intent. The preview text earns the open by quantifying the read time. Founders sending under their own name lift opens by an additional 6 to 9% (Gong State of Sales Engagement, 2025).
Motion 4: Inbound follow-up (pricing-page visit)
Subject: Saw [Company] on pricing
Preview text: Two questions usually decide it.
The subject acknowledges the signal. The preview text earns the open by promising the buyer that the body answers two specific questions. This pattern lifts inbound-follow-up opens to the 50%+ band in pilots.
Fast tip. Always render the subject + preview text combination in the inbox preview before scaling. Reading it on paper is not the same as reading it on a Gmail mobile preview at 35 characters.
How Gangly fits
Gangly treats sales email preview text as a first-class field on every cold send, not as an afterthought tucked under the subject line. The signal that fires on the prospect record fuels both the subject line draft and the preview text continuation in one motion, and a render check against three saved inbox profiles runs before any send leaves the queue. Reps using the Gangly preview text workflow ship a paired preheader on 96% of cold sends versus an industry baseline of 64% (Gangly product telemetry, Q2 2026), and open rates lift by 11 to 19% inside 60 days.
- Outreach Writer : Drafts the subject line and the paired preview text from the freshest signal on the prospect record, then renders the combination in three inbox profiles before the send is queued.
- Signal Detection : Surfaces the buying signals — funding rounds, leadership changes, pricing-page visits — that fuel the preview text continuation, so the field is never written from a blank slate.
- Workflow Sequencer : Blocks the send if the preview text field is empty, runs the render test as a pre-send gate, and surfaces open-rate lift by cohort in the weekly review.
- Sales Workflow : Ties the preview text result back to the rest of the cadence so the engagement signal from touch 1 informs the angle on touch 2.
If you want to see the connected workflow on your own pipeline, run a 20-minute live demo or start the free trial and ship the first sequence with a paired preview text inside an hour.