Resume video where viewers left off: pause screens, exit prompts and follow-ups that win VSL viewers back

To resume video where a viewer left off, the player remembers the deepest point each returning viewer reached and starts there, while first-time viewers always start at 0:00 so they hear the hook. Around that, a VSL needs three recovery tools: a pause screen that gives a reason to continue, one honest exit prompt, and follow-ups matched to how far each viewer watched.

What happens when a VSL viewer pauses or leaves?

A long VSL competes with notifications, meetings, kids and low-battery warnings. Viewers stop in four distinct ways, and lumping them together as "drop-off" hides the fact that each one has a different fix. Resume, the pause screen and the exit prompt are three of the player behaviors covered in the VSL player features guide; this page is about using them together. Here is each moment, with what the viewer sees, your lever and the number to watch:

Four ways a viewer stops, and the lever for each

1. 1Pauses, stays on the pageSees: the pause screen. Lever: a pause image with a reason to continue. Number to watch: retention after common pause points.
2. 2Leaves mid-videoSees: your exit prompt, if any. Lever: one honest prompt. Number to watch: pitch reach with vs without it.
3. 3Returns on the same browserSees: the video, picking up where they stopped. Lever: resume from the deepest point. Number to watch: share of returners who reach the pitch.
4. 4Returns from an email or adSees: the page again, maybe on another device. Lever: follow-ups by watch depth. Number to watch: incremental sales vs a holdout.

Not every pause is a choice. WebKit's 2016 video policy for iOS says autoplaying videos pause when they are scrolled out of the viewport (WebKit), and a web app can pause playback when its tab goes to the background, using the browser's Page Visibility API (MDN). So your pause screen is also seen by people who never pressed pause. Design it for someone who looked away for a moment and came back.

Should a VSL resume video where the viewer left off?

Yes for returning viewers, no for first-time viewers. The rule follows from what each one has already heard.

First-time viewers start at 0:00. The hook is the part of your script that earns the next ten minutes. With muted autoplay, a visitor who taps for sound at 0:09 has watched nine silent seconds. If playback simply continues, they hear the middle of a sentence instead of your opening line. Rewinding to 0:00 on that first tap gives them the hook as written. The VSL autoplay guide covers the unmute prompt in detail.

Returning viewers resume at the deepest point they reached. They heard the hook yesterday. Making them sit through the same six minutes again spends their patience on content they have already accepted. Use the deepest point, not the last position: if a viewer rewound to rewatch a section and then left, the last position replays material they have seen, while the deepest point picks up exactly where new content begins.

In RevvyScales both rules are built into the player: a first-time viewer who taps for sound restarts at 0:00, and a returning viewer, recognized by a viewer cookie, resumes from the deepest point they watched (player conversion features).

Three edge cases to plan for

Open each case to see what it needs:

Three kinds of return

After the pitchMid-argumentAnother device

They return after the pitch

Someone who saw the price and left may be coming back to look at the offer again. Check that the offer, guarantee and button are visible as soon as playback resumes past your pitch second, so they don't have to wait or rewind.

The on-page offer block is their rewind button: it lets them re-read the price without replaying the video. The CTA timing guide covers how to set the reveal.

They return mid-argument

A resume at 11:40 drops the viewer into the middle of a point, and if you hide the seek bar they can't scrub back for context. Write re-entry lines into the script: every few minutes, one sentence that recaps where the story is.

Before: "And that's reason two. Now, reason three."
After: "So it's not your effort, it's the timing of your meals. Here's the third thing that matters."

The recap costs four seconds and also catches first-time viewers whose attention drifted.

They return on another device

Resume depends on recognizing the same browser. A phone after a desktop visit, a private window, cleared cookies or a different browser all start fresh. Browser privacy features add limits too: Safari's tracking prevention deletes cookies created by JavaScript, and other script-writeable storage, after 7 days without user interaction on the site (WebKit).

Treat resume as a convenience for the near-term return, and never promise viewers they can pick up "anytime".

Test it yourself in five minutes

1. In a normal browser window with cleared site data, open the VSL, tap for sound and confirm the video jumps back to 0:00.
2. Watch for a few minutes, close the tab and reopen the link. Playback should continue near where you stopped.
3. Repeat, but leave after the pitch second. The offer should be visible as soon as the video resumes.
4. Open the link in a private window. It should behave like a first visit.

What should a VSL pause screen show?

By default, a paused web video simply holds the current frame. That frame is random: a half-blink, a hand mid-gesture, a slide caught between transitions. It tells the viewer nothing about why they should keep going.

A pause image replaces that frame with something you designed for the moment of doubt. In RevvyScales, pausing shows your pause image instead of a frozen frame, or a built-in pause screen when you haven't set one. Its job is narrow: remind the viewer why they started and make "continue" the obvious next tap.

What to put on it:

• One line that restates the promise of your headline in the viewer's own words, under eight words so it reads at a glance.
• The presenter looking into the camera, if your VSL has a presenter. It frames the pause as a conversation on hold rather than a video that ended.
• Clear space in the center and along the bottom for the player's controls and captions.
• Text sized for a phone. A 1280-pixel-wide image shown 390 pixels wide shrinks to about 30% of its size, so 80-pixel lettering becomes roughly 24 pixels on screen. Anything much smaller turns into texture.
• Nothing that is only true at some pause points. A static image can't know where the viewer stopped, so "the answer is next" will be wrong for most of them.

Three fictional templates to adapt:

Three fictional pause-image templates

Promise reminder

"Paused: the 4-minute routine for calmer mornings"

Use when: default for most VSLs.

Open question

"Does it work after 50? This video answers that."

Use when: the video truly answers it.

Presenter credential

"[Name], physical therapist for 14 years"

Use when: the credential is real and relevant.

What never goes on a pause screen: fake error messages ("Paused due to high demand"), countdown clocks, "this video comes down tonight" when it doesn't, or invented viewer counts. The FTC's 2022 staff report on dark patterns lists false activity messages and baseless countdown timers among design practices that trick or manipulate users (FTC). Beyond the legal exposure, a sale made under false pressure is a refund request waiting to happen.

Do exit-intent prompts work on a VSL page?

An exit-intent prompt appears when the page detects a visitor leaving. It can recover a viewer who was about to close the tab out of habit, and it can irritate everyone else. The difference is mostly wording and frequency.

Know the browser's limits first. The browser's built-in "leave site?" confirmation shows only a generic message the page can't change, appears only after the visitor has interacted with the page, and is not reliably fired on mobile (MDN). So the native dialog can't carry your message, and on phones your dependable recovery tools are resume and follow-ups rather than a last-second prompt.

The honest version:

• Show it once per visitor, never on every exit.
• Make it dismissible in one tap, with no trick buttons.
• Give one true, useful reason to stay, then let them go.

Fictional examples that pass the test:

• "Leaving? Come back soon in this browser and the video picks up where you left off."
• "Before you go: the part about why the routine works comes later in this video."
• "Want the link by email so you can finish tonight?" (only if you really send it)

Avoid the dishonest versions: a deadline that doesn't exist, a price that "doubles at midnight" when it doesn't, or a decline button like "No, I don't care about my health". The same FTC report calls that last pattern confirmshaming: using shame to steer people away from a choice.

In RevvyScales, the exit-intent gate asks a leaving viewer whether they're sure. Whatever tool you use, hold every exit message to the honest version above.

Judge it downstream. "How many people stayed" is a vanity number, because a prompt can hold people who then leave thirty seconds later. What matters is whether the people who stayed went on to reach the pitch and buy. If you can run versions of the page with different prompt wording, or with and without a prompt, split traffic between them and compare pitch reach and revenue per visitor over at least a full week. A prompt that moves neither number is friction, so soften it or drop it.

How do you win back viewers who left before the pitch?

Split them into two pools: people who gave you an email, and people who didn't.

Known viewers. A lead-capture gate asks sound-on viewers for an email at a second you choose. In RevvyScales it's an opt-in feature on the Growth plan and up: the gate can be skippable, leads export as CSV with buyer and watch-depth filters, and each capture fires a "Lead captured" webhook. Webhooks (also Growth and up) fire when a viewer watches 25%, 50% and 75%, reaches the pitch, completes the video or clicks the CTA, so Klaviyo, ActiveCampaign, Zapier or Make can tag each contact with the last milestone they reached (webhooks and CRM events).

Then match the follow-up to the milestone:

Follow-ups by watch depth

The last milestone a viewer reached, what it suggests and the follow-up angle

1. 1Lead captured, under 25%What it suggests: interrupted, or the hook missed. Follow-up angle: restate the promise, resend the link.
2. 225–50%What it suggests: interested, lost momentum. Follow-up angle: a short recap of the story so far.
3. 350–75%What it suggests: invested, close to the offer. Follow-up angle: what the rest of the video covers, accurately.
4. 4Pitch reached, no clickWhat it suggests: saw the price, has an objection. Follow-up angle: answer it: guarantee, FAQ, real proof.
5. 5CTA clicked, no orderWhat it suggests: checkout friction or second thoughts. Follow-up angle: leave it to your checkout's cart recovery, if it has one.
6. 6BoughtWhat it suggests: customer. Follow-up angle: exclude from every sequence above.

Buyers belong in your onboarding and upsell funnel, not in a "you missed something" email.

Choosing the gate second. An early gate asks more people but interrupts the story sooner; a late gate asks fewer, warmer viewers. A worked example: at 1:30, 4,800 viewers are still watching and 15% give an email, so you collect 720 leads. At 6:00, 3,000 are still watching and 22% opt in, so you collect 660, and nobody was interrupted during the opening of your story. Lead counts can't settle it. Put two copies of the VSL in a folder, identical except for the gate second, and compare revenue per visitor after two full weeks, counting sales from the follow-ups.

Keep it honest and legal. The gate should say exactly what the viewer gets, and you must deliver it. In the US, commercial email must follow CAN-SPAM: accurate header information, honest subject lines, disclosure that the message is an ad, a valid postal address, and an opt-out you honor within 10 business days (FTC guide). If you sell abroad, check local rules too. This is not legal advice.

Anonymous viewers. For visitors who never gave an email, retargeting through your ad pixels is the net. In RevvyScales you set your Meta, Google and TikTok pixels once on a folder or VSL. Build the audience from page visitors who didn't buy, and write the ad around the objection you hear most at the pitch, rather than pretending to know where each person stopped.

How do you measure viewer recovery?

Three numbers tell you whether recovery is working:

Three numbers that measure recovery

Return rate=viewers who came back within seven days ÷ viewers who left before the pitch (count the returns from email clicks or your CRM events)

Return-to-pitch rate=viewers who came back and reached the pitch ÷ viewers who came back

Incremental sales=sales from the recovery flow − the sales that would have happened anyway

The third number needs a holdout, because some people come back on their own. A worked example: 6,000 leads leave before the pitch in a month. You send the follow-up sequence to a random 5,400 and hold back 600. The sequence group buys at 2.5% (135 orders); the holdout buys at 1.0% (6 orders). Here is what that means for the sequence group:

What the follow-up sequence really earned

Worked example: 5,400 leads get the sequence, 600 are held back

Orders from the sequence group (2.5%)135

Would have bought anyway (the holdout rate, 1.0% of 5,400)−54

Orders the flow earned (1.5 points × 5,400)81

The sequence didn't earn 135 sales. It earned the difference: 1.5 points × 5,400 = 81 orders. At a $69 average order, that's about $5,600 you can actually credit to the flow. With a holdout of 100 instead of 600, the same rates would be too noisy to trust, so keep the holdout large or run it longer.

Then fix the source. Recovery is a patch for a leak, not a replacement for fixing it. If your second-by-second retention chart shows a cliff at 4:10, rewriting that section helps every future viewer, while a follow-up email only helps the people you can reach (how to read a retention graph).

A 20-minute pause-and-resume audit

Run it on your own page; the ticks stay in this browser:

A 20-minute pause-and-resume audit

• Tap for sound on a first visit: the video restarts at 0:00.
• Leave at minute three and come back: playback resumes near where you left.
• Leave after the pitch and come back: the offer is visible right away.
• Pause on a phone: you see a designed pause image, readable at arm's length, not a frozen frame.
• Read the pause image and exit prompt aloud: every sentence is true at every moment it can appear.
• Trigger the exit prompt twice in one visit and note how often it appears. Once per visit is the standard to aim for.
• Skim the script for re-entry lines every few minutes, especially if the seek bar is hidden.
• Check your email sequences: each watch-depth segment gets its own angle, and buyers are excluded.
• Confirm a holdout exists before you report recovery revenue to anyone.

0 of 9 done