The Screen After Your Signup Button Decides Whether They Come Back
The Screen After Your Signup Button Decides Whether They Come Back
Most SaaS teams spend three weeks arguing about the signup button and four minutes writing the screen that comes after it. That screen — the verification interstitial, the "check your inbox" page — is where intent is highest and confidence is lowest. Someone just handed you their work email. They are one badly written sentence away from closing the tab.
This post is about that one screen. Not the form, not the email template, not the landing page. Just the interstitial, and the copy on it.
Why the verification screen leaks signups
The interstitial fails in four predictable ways, and each one maps to a heuristic you already know:
- Clarity. It says "check your email" and stops. It doesn't say who the email is from, when it will arrive, which address it went to, or how long the link lasts. The user is now guessing.
- Trust. No sender name, no explanation of why verification is required. It reads like a system message from a company that might be harvesting the address. That's the exact moment people start checking whether they typed their email correctly.
- Friction. No resend, no "wrong address" path, no way back to the form. The only two options are wait and leave, and leaving is easier.
- Feedback. They click resend. Nothing visibly happens. They click it four more times. Your rate limiter eats the fifth, and now they're locked out of a flow they were already unsure about.
There's also a copy anti-pattern worth naming: leading with "Don't forget to check your spam folder!" Putting spam in someone's head before they've even opened their inbox primes them to distrust the delivery. Save that line for the resend confirmation state, where it's actually useful.
The four jobs this screen has to do
A good interstitial does exactly four things, in this order:
- Confirm the action landed. One line: we got it, here's what happens next. Feedback, not celebration. "Success!" is about you, not them.
- Tell them precisely what to look for. Sender address, the email address it went to, and a realistic arrival window. This is clarity doing the work of a support ticket.
- Give one obvious primary action and two escape hatches. The primary action should be a real action (open the inbox), not a passive instruction. The escape hatches are resend and "wrong address."
- Remove the reason they're nervous. Why do you need this? How long is the link good for? Are you going to email them forever? One short line of trust copy kills the doubt.
Notice what's not on that list: brand voice, illustrations, a progress bar. Hierarchy beats decoration here.
Before and after: rewriting a real interstitial
Here's a typical version. It's not unusual — that's the problem.
Before
Success! Please check your email to verify your account. [Resend]
Now the rewrite. Same product, same engineering, same 20 minutes of work.
After
One click left — confirm maya@acme.co We sent a link from Acme (hello@acme.co). It usually lands in under a minute, and it's good for 24 hours.
[Open Gmail]
Resend link · Wrong address? Change it
Clicking resend again: "Sent. Nothing after two minutes? Check spam, then reply to that email — a human will verify you."
Why this version works, line by line:
- The headline names the address. A typo gets caught here, in five seconds, instead of turning into a support ticket three days later. This alone is worth shipping.
- The body names the sender. "hello@acme.co" turns a stranger in the inbox into a known quantity. Trust, cheaply.
- "Under a minute" and "24 hours" replace silence with a clock. People tolerate waiting when they know how long the wait is.
- The primary button does something. "Open Gmail" is a next step. "Resend" as the biggest button on the page is an invitation to spam your own send rate.
- Two escape hatches, both small. Resend and "wrong address" are present but subordinate. Hierarchy: one thing matters, two things are there if needed.
- The resend state has copy. Feedback after an action is not optional. Without it, resend is a button that teaches people to click it five times.
The email is part of the screen
The interstitial and the email land in the same mental moment. If the screen says "Acme" and the inbox shows a bare address with a subject line reading "Verify your email," you've split the experience in half.
Before: From no-reply@acme.co · Subject: Verify your email · No preheader.
After: From Acme <hello@acme.co> · Subject: Your Acme workspace is one click away · Preheader: Sent to maya@acme.co. Link expires in 24 hours.
The subject line should describe the outcome, not the mechanism. Nobody wants to verify an email address. They want the workspace.
The playbook: fix this screen in one sitting
Work top to bottom. P0 requires no engineering and no design review.
P0 — ship today, ~20 minutes of copy
- Replace the "Success!" headline with a sentence that names the email address.
- Add the sending address to the body copy.
- State the link expiry.
- Rename "Resend" to "Resend link" and add the cooldown/confirmation text underneath.
- Delete "check your spam folder" from the main state.
P1 — this week, small engineering lift
- Deep-link the primary button to Gmail or Outlook based on the address domain, with a plain "Open your email app" fallback.
- Add "Wrong address? Change it" that returns to the form with the field prefilled.
- Add a visible success state to the resend button.
- Rewrite the subject line, preheader, and sender display name to match the screen.
P2 — next sprint
- Clicking the verification link should log the user in and drop them inside the product, not onto a "Verified!" dead-end page that asks them to log in again.
- Carry intent through: if they signed up to accept an invite or open a template, the interstitial should say so.
- Add a human fallback (reply-to address, or a support link) for people who never receive the mail.
- Instrument the screen: submit → verified completion, median time to verify, resend clicks per signup, "wrong address" clicks.
One caution on measurement: don't A/B test the whole screen at once. At small-team volumes you won't reach significance on a few-point delta, and you'll ship nothing while waiting. Fix the obvious things first, then test the headline against the sender-name line if you must pick one.
A high "wrong address" click rate is a signal too — but it's usually a problem in the form upstream, not the interstitial. If that number is ugly, run a free audit on your signup flow and it'll tell you which step is actually leaking before you rewrite copy that isn't the problem.
What to look at after you ship it
Give it a week, then check three numbers:
- Verification completion rate (submitted → verified). The one that matters.
- Median time to verify. If it drops, the screen is doing its job of pushing people into the inbox faster.
- Resend clicks per signup. Should fall. If it doesn't, the email is the problem, not the copy.
If you want a wider teardown of the surrounding flow, the FlowAudit blog covers the trial-end screen and paywall copy the same way — one step, one rewrite, no heuristic checklists pretending to be advice.
You don't need a consultant to fix a two-line screen. You need to stop treating it as a system message and start treating it as the last piece of copy in your signup flow. Start a free FlowAudit at /signup and you'll get a prioritized P0/P1/P2 fix list for your own flow — including the interstitial — in a few minutes.