An in-app empty state is the most under-used persuasion surface in your product. It is the screen a user sees before they have created anything — the blank project list, the zero-row table, the "no data yet" dashboard — and most teams treat it as a placeholder to apologize for. But the empty state is not dead space; it is the exact moment a new user is deciding whether the work of filling it is worth doing. They signed up, they got in, and now they are staring at nothing, weighing effort against a payoff they can't yet see. Whatever you put on that screen is arguing for the effort, and most empty states lose the argument because they explain the mechanics — "Click here to add your first item" — without ever answering the quieter question: will this be worth my time? A testimonial is the one element on the screen that answers it in a voice the user doesn't assume you engineered.
This is the same reason testimonials matter everywhere, aimed at the activation gap specifically: proof lands hardest when a real customer says it, and on a blank screen where the user has no results of their own to look at, an outside voice showing the result is the only evidence available.
Why an empty state needs a voice that isn't yours
An empty state is a pure onboarding surface, and everything on it is written by the company that wants the user to keep going. The instructional copy tells the user how to start; it does nothing for the doubt that actually stalls activation: is the outcome on the other side of this work good enough to justify starting? A user who isn't sure abandons — not because the product is hard, but because the payoff is invisible.
A testimonial changes whose voice describes that payoff. When a named customer says "once we imported our data, the weekly report that used to take an afternoon built itself," the empty state stops being your instruction and becomes someone else's result. That shift is exactly the difference between a testimonial and a review: a review is a public rating of the product overall, but on an empty state you want a testimonial that describes a concrete outcome — a specific result a real person got after doing the very thing you're asking this user to do now. The user isn't looking for a star count; they're looking for a picture of what the screen looks like once it's full, told by someone who filled it.
Where the testimonial fits inside the empty state
An empty state has a natural three-part layout, and the testimonial has one right place in it:
- Below the primary action, not above it. Keep the headline and the "create your first ___" button at the top, where the user's eye lands first, and place the testimonial directly beneath. The user reads what to do, sees the button, and then — in the space where hesitation lives — meets a customer confirming the payoff. The proof sits exactly where the doubt peaks, not before the user knows what they're being asked to do.
- Match the quote to the first action. If the empty state is asking the user to import contacts, show a testimonial about what the product did with those contacts, not a generic "great tool" line. A quote that names the outcome of the exact step the user is about to take converts far better than praise about something they haven't reached yet.
- One quote, never a gallery. An empty state is not a testimonials page. One credible, specific voice beats three generic ones, because extra quotes turn an onboarding nudge into a marketing wall — the same restraint that works in an in-app upgrade prompt, where one clear voice beats a stack.
What makes a quote convert in this specific context
The user in an empty state has one fear: putting in effort and getting nothing worth having. So the quote that converts is the one that proves payoff, not satisfaction. "Love this app" verifies nothing and could sit on any screen. "After we connected our store, the dashboard flagged three abandoned-cart patterns we'd been missing for months" verifies that the work the user is hesitating over leads somewhere concrete, told by someone who already crossed the same blank screen.
The most persuasive version names the effort and the result, because the empty state is where those two things are furthest apart in the user's mind. A quote that says "the setup took ten minutes and it's saved us hours every week since" collapses the gap: it acknowledges the cost the user is weighing and puts a real payoff on the other side of it, in a voice the user has no reason to distrust.
The mistake that makes an empty-state testimonial backfire
The failure mode is decoration. A testimonial dropped onto an empty state to make the blank screen feel less empty — unmatched to the action, generic in its wording, floating in a corner — reads as marketing filler and actually deepens the user's suspicion that the payoff is being oversold. If the quote doesn't describe the outcome of the specific first step, it isn't proof; it's noise on a screen that already has too little signal.
Use the empty state's one testimonial to do one job: show the user, in a customer's own words, what the screen looks like once the work is done. Get that right and the blank screen stops being a reason to leave and becomes a preview of the reason to stay.