Rewrite empty state copy to accelerate user activation
Turn passive placeholder screens into clear, action-oriented entry points that guide users to their first completed task. Use it during product design and copy polish.
Prompt
Act as a senior product UX copywriter. Rewrite the provided empty state screen copy to turn passive UI into an action-driving onboarding step.
Rules:
- Keep copy concise: headline under 6 words, supporting body under 25 words, primary CTA under 4 words.
- Clarify the immediate payoff of taking action rather than merely describing that the screen is empty.
- Provide three distinct tonal variations for the screen: Clear & Direct, Benefit-Driven, and Guided/Action-Oriented.
- Avoid passive phrasing like 'Nothing to see here yet' or 'No items found'.
Output format for each variation:
- Headline
- Body Text
- Primary Button
- Optional Secondary Action
Screen context and current empty state copy are below:Example output
Paste the screen name, user goal, and current placeholder text into Claude, ChatGPT, or Gemini. Follow up by asking for microcopy for an accompanying empty state illustration or tooltip.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Classify onboarding drop-offs into cognitive and value friction
Audit user onboarding funnels by separating confusion from missing value motivation. Use it to prioritize growth experiments and UX redesigns.
Audit Your Signup-to-Activation Flow and Find the Steps to Cut First
Get a step-by-step friction audit of your onboarding flow, a before/after count of steps, fields and waits, and the three cuts worth A/B testing first.
Turn onboarding test notes into root causes
Extract recurring user drop-off triggers and identify root causes from raw usability notes. Use this to focus sprint priorities on true blockers.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Write a beta tester welcome and feedback guide
Generate a concise onboarding document for new beta testers. Use it to clarify software limitations, expected time commitment, and bug submission steps.
Tear Down Three Competitor Onboarding Flows into a Ranked Quick-Win Fix List
Get a step-by-step scorecard of three competitor onboarding flows on time-to-value, required inputs and drop-off risk, plus quick wins ranked by effort.