12 Claude Prompts for UX Microcopy Improvements

** Why Microcopy Matters in UX Design**

You know that moment when you’re about to click a button, but the label says “Submit” instead of “Get my free guide”? Or when an error message pops up and says “Error 404” instead of “Oops! This page is missing—let’s get you back on track”? Those tiny words might seem unimportant, but they can make or break your user experience.

Microcopy—the small bits of text in buttons, error messages, tooltips, and forms—has a huge impact on how people interact with your product. A single word can change whether someone completes a purchase, signs up for a newsletter, or just gives up and leaves. In fact, studies show that well-written microcopy can increase conversion rates by up to 17% (Baymard Institute). That’s not a small number—it’s the difference between a product that struggles and one that thrives.

The Problem: When Microcopy Fails

Bad microcopy is everywhere. You’ve probably seen it:

• Vague buttons – “Click here” (Click for what?)
• Robotic error messages – “Invalid input” (What’s wrong? How do I fix it?)
• Confusing tooltips – “Hover for more info” (But the info is just as confusing)
• Cold, corporate language – “Your request has been processed” (Why not “We’ve got your order—thanks!”?)

These small mistakes add up. They frustrate users, make your product feel impersonal, and—worst of all—hurt your business. If people don’t understand what to do next, they’ll leave. And they won’t come back.

How AI Can Help (Without Sounding Like a Robot)

This is where Claude comes in. AI isn’t just for long blog posts or chatbots—it’s a powerful tool for crafting clear, human, and effective microcopy. The right prompts can help you: ✅ Turn boring labels into action-driven text (“Submit” → “Get instant access”) ✅ Make error messages helpful, not confusing (“Error” → “Your password needs 8+ characters”) ✅ Write tooltips that actually explain things (“Required field” → “We need your email to send your receipt”)

The best part? You don’t need to be a copywriting expert. With the right prompts, Claude can generate microcopy that feels natural, friendly, and conversion-focused—in seconds.

What You’ll Learn in This Guide

In this article, we’ll share 12 Claude prompts designed to improve your UX microcopy. Each one tackles a different pain point—from button labels to error messages—and gives you ready-to-use templates you can test right away. Whether you’re a designer, marketer, or product manager, these prompts will help you:

• Increase conversions with clearer calls to action
• Reduce user frustration with helpful error messages
• Build trust with friendly, human-sounding text

No more guessing. No more generic labels. Just microcopy that works.

Ready to make your product easier (and more enjoyable) to use? Let’s dive in.

The Psychology Behind Effective Microcopy

Microcopy is like the quiet hero of UX design. It’s the small words that guide users—button labels, error messages, tooltips—but it does so much more than just explain. Good microcopy reduces frustration, builds trust, and even makes people smile. Bad microcopy? It confuses, annoys, and sends users running. So why does something so small have such a big impact? The answer lies in psychology.

How Microcopy Reduces Cognitive Load

Our brains don’t like to work too hard. When users see a website or app, they scan quickly, looking for clues about what to do next. If the microcopy is unclear or too wordy, their brain has to pause and think. This is called cognitive load—the mental effort required to understand something.

For example, imagine a checkout button that says: ❌ “Proceed to the next step” ✅ “Pay now – secure checkout”

The first option is vague. The second tells users exactly what will happen and adds a little reassurance (“secure”). Small changes like this make decisions easier, which keeps users moving forward instead of second-guessing.

Here’s how to keep microcopy simple and effective:

• Be direct – Use action words (“Download” instead of “Get your file here”).
• Avoid jargon – Not everyone knows what “API” or “metadata” means.
• Cut unnecessary words – “Click here to submit” → “Submit”.
• Use familiar terms – If users expect “Sign up,” don’t say “Register now.”

Emotional Triggers in Microcopy

Words don’t just inform—they make us feel something. A well-placed phrase can create urgency, ease anxiety, or even make someone laugh. The right tone turns a boring interaction into a pleasant one.

Take error messages, for example. Most people dread seeing them, but they don’t have to be scary. Compare these two: ❌ “Error: Invalid input.” ✅ “Oops! Your password needs at least 8 characters.”

The first feels cold and robotic. The second is friendly, explains the problem, and even uses a little empathy (“Oops!”). That tiny shift makes users less frustrated and more willing to try again.

Here’s how to add emotion to microcopy:

• Use a conversational tone – Write like you’re talking to a friend.
• Add personality – A playful brand can say “Whoopsie!” instead of “Error.”
• Create urgency (when needed) – “Only 3 spots left!” works better than “Limited availability.”
• Show empathy – Acknowledge the user’s feelings (“We know this is frustrating…”).

Why Consistency Matters

Imagine if every button on a website said something different: “Buy now,” “Purchase,” “Get it,” “Add to cart.” Confusing, right? Consistency in microcopy helps users learn faster and feel more in control.

Brand voice plays a big role here. If your brand is professional, your microcopy should sound polished (“Your request has been submitted.”). If it’s fun and quirky, you can be more playful (“Boom! Your order is on the way.”). But no matter the tone, the key is to keep it the same everywhere—buttons, emails, error messages, and tooltips.

Here’s how to maintain consistency:

• Create a style guide – List approved terms (“Log in” vs. “Sign in”) and tone rules.
• Use the same words for the same actions – If a button says “Subscribe” on one page, don’t call it “Join” on another.
• Test with real users – Sometimes what makes sense to you confuses others.

A Real-World Example: How a CTA Change Boosted Conversions by 30%

In 2021, an e-commerce company tested two versions of their checkout button:

• Version A: “Continue”
• Version B: “Complete my order”

At first glance, both seem fine. But Version B performed 30% better because it:

1. Was more specific – Users knew exactly what would happen.
2. Used “my” – It felt personal, like the action was for them.
3. Created a sense of completion – “Complete” implies the end of a process, which reduces hesitation.

This small change didn’t just improve conversions—it also reduced cart abandonment. Users felt more confident clicking a button that clearly told them what to expect.

The Big Lesson: Microcopy Is About People, Not Just Words

Good microcopy isn’t about being clever or using fancy words. It’s about understanding how people think, feel, and act. It’s about making their lives easier, even in tiny ways.

Next time you write a button label or an error message, ask yourself:

• Does this make the user’s job easier?
• Does it sound like a human wrote it?
• Will it reduce confusion or frustration?

If the answer is yes, you’re on the right track. If not, it’s time to rethink—and maybe even test a few versions to see what works best. Because in UX, the smallest words often make the biggest difference.

12 Claude Prompts for High-Converting Microcopy

Microcopy is like the secret sauce of UX design. You don’t notice it when it’s good—but when it’s bad, everything feels clunky. A button that says “Submit” instead of “Get my free guide” can mean the difference between a user signing up or bouncing. The problem? Writing microcopy that converts isn’t just about being short. It’s about being clear, helpful, and human.

That’s where Claude comes in. With the right prompts, you can turn boring labels, confusing error messages, and vague tooltips into microcopy that guides users—and boosts conversions. But not all prompts are created equal. Some give generic results. Others help you dig deeper into what your users actually need.

Here are 12 prompts to help you write microcopy that works—plus real examples of how to use them.

---

1. Make Buttons More Action-Driven

Generic buttons like “Submit” or “Click here” don’t tell users what happens next. Instead, use action words that match the user’s goal.

Prompt: “Rewrite this button label to make it more action-driven and benefit-focused. The button is for [describe the action, e.g., ‘downloading a free ebook’]. Use no more than 3 words. Give me 3 options.”

Example:

• Original: “Submit”
• Improved: “Get my guide” / “Download now” / “Start learning”

Why it works: Users don’t care about “submitting.” They care about what they get in return.

---

2. Turn Error Messages into Helpers

Error messages often sound like a robot scolding the user. Instead, explain what went wrong and how to fix it.

Prompt: “Rewrite this error message to be helpful and friendly. The error is [describe the issue, e.g., ‘password too short’]. Include: 1) What went wrong, 2) How to fix it, 3) A reassuring tone.”

Example:

• Original: “Error: Invalid password.”
• Improved: “Your password needs 8+ characters. Try adding a number or symbol to make it stronger.”

Why it works: Users don’t want to feel stupid. A little guidance goes a long way.

---

3. Write Tooltips That Actually Explain

Tooltips should answer questions before users ask them. If a tooltip just repeats the label, it’s useless.

Prompt: “Write a tooltip for [describe the field, e.g., ‘a coupon code box’]. Explain: 1) What it does, 2) Why it’s useful, 3) How to use it. Keep it under 20 words.”

Example:

• Original: “Coupon code”
• Improved: “Enter a promo code for instant savings. Check your email for the latest deals!”

Why it works: Users appreciate when you save them time—and money.

---

4. Simplify Complex Terms

Jargon confuses users. If your microcopy includes words like “API” or “metadata,” you’re losing people.

Prompt: “Explain [complex term] in simple words for a non-technical user. Keep it under 10 words. Give me 2 options.”

Example:

• Original: “Enter your API key.”
• Improved: “Paste your access code here.” / “Use your unique password.”

Why it works: The easier it is to understand, the faster users will act.

---

5. Make CTAs More Urgent (Without Being Pushy)

A CTA like “Sign up” is forgettable. Adding a little urgency can nudge users to act now.

Prompt: “Rewrite this CTA to make it more urgent but still friendly. The action is [describe, e.g., ‘joining a waitlist’]. Include a reason to act now. Give me 3 options.”

Example:

• Original: “Join the waitlist”
• Improved: “Get early access—spots filling fast!” / “Reserve your spot today” / “Limited seats available”

Why it works: Scarcity works—but only if it feels real.

---

6. Soften Negative Messages

Sometimes, you have to say no. But you can do it in a way that doesn’t frustrate users.

Prompt: “Rewrite this message to sound more positive and helpful. The message is [describe, e.g., ‘your free trial ended’]. Include: 1) What happened, 2) What they can do next, 3) A friendly tone.”

Example:

• Original: “Your trial has expired.”
• Improved: “Your free trial is over! Upgrade now to keep enjoying [product name]—no interruptions.”

Why it works: Users are more likely to convert when they feel supported, not scolded.

---

7. Personalize Placeholder Text

Placeholder text like “Enter your name” is boring. Make it feel like a conversation.

Prompt: “Write placeholder text for [describe the field, e.g., ‘a search bar’]. Make it friendly and specific to the user’s goal. Keep it under 10 words.”

Example:

• Original: “Search…”
• Improved: “Find your perfect [product]” / “What are you looking for?”

Why it works: Personalized microcopy makes users feel like the product was made for them.

---

8. Make Empty States Useful

An empty screen is a missed opportunity. Instead of “No results found,” guide users to the next step.

Prompt: “Write an empty state message for [describe the scenario, e.g., ‘a user’s inbox with no emails’]. Include: 1) What’s empty, 2) Why it’s empty, 3) What to do next.”

Example:

• Original: “No emails found.”
• Improved: “Your inbox is empty! Try refreshing or checking your spam folder.”

Why it works: Users don’t want to feel lost. A little direction keeps them engaged.

---

9. Write Confirmation Messages That Build Trust

A confirmation message like “Your order has been received” is fine—but it could be better.

Prompt: “Write a confirmation message for [describe the action, e.g., ‘a user just subscribed’]. Include: 1) What happened, 2) What to expect next, 3) A friendly tone. Keep it under 20 words.”

Example:

• Original: “Subscription confirmed.”
• Improved: “Welcome aboard! Check your email for your first tip in 5 minutes.”

Why it works: Users love knowing what’s next—it reduces anxiety.

---

10. Make Form Labels Clearer

Labels like “First Name” are obvious—but what about “Billing Address” vs. “Shipping Address”?

Prompt: “Rewrite this form label to be more specific and user-friendly. The field is [describe, e.g., ‘a phone number input’]. Include: 1) What to enter, 2) Why it’s needed, 3) An example if helpful.”

Example:

• Original: “Phone”
• Improved: “Phone number (for order updates) – e.g., 555-123-4567”

Why it works: Users are more likely to fill out forms when they know why you need their info.

---

11. Turn “Learn More” into Something Better

“Learn more” is the laziest CTA. Make it specific to what users will actually get.

Prompt: “Rewrite this ‘Learn more’ link to be more specific and benefit-focused. The link leads to [describe the page, e.g., ‘a pricing page’]. Give me 3 options.”

Example:

• Original: “Learn more”
• Improved: “See pricing plans” / “Find the right plan for you” / “Compare features”

Why it works: Users click when they know what they’re getting.

---

12. Write Loading Messages That Entertain

A loading screen doesn’t have to be boring. A little personality can make the wait feel shorter.

Prompt: “Write a loading message for [describe the action, e.g., ‘a file upload’]. Make it fun, on-brand, and under 10 words. Give me 3 options.”

Example:

• Original: “Uploading…”
• Improved: “Almost there—your file is on its way!” / “Packing your file for delivery…” / “Hold tight, we’re working fast!”

Why it works: A little humor or warmth makes users more patient.

---

How to Use These Prompts Effectively

Now that you have these prompts, how do you get the best results from Claude? Here’s what works:

1. Be specific. The more details you give, the better the output. Instead of “Rewrite this button,” say “Rewrite this button for a free trial signup. Make it urgent but not pushy.”
2. Ask for multiple options. Claude can generate 3-5 versions at once. Test them to see which performs best.
3. Refine based on tone. If your brand is playful, ask for a “fun and casual” version. If it’s professional, say “polished and clear.”
4. Test in real life. Even the best microcopy needs validation. Use A/B testing to see which versions convert better.

Microcopy might be small, but its impact is huge. With these prompts, you can turn every word into a conversion opportunity—without sounding like a robot. Ready to try them out? Pick one prompt, test it, and watch your engagement grow.

A. Button Labels & CTAs

Buttons are the silent salespeople of your website. They don’t shout, but they guide users—if they’re written well. A weak button label like “Submit” or “Click here” is like a store clerk who just points and says, “Over there.” It doesn’t help. A strong CTA, on the other hand, tells users exactly what they’ll get and why they should care. Think of it as a tiny billboard for your product.

The problem? Most button labels are written as an afterthought. Designers focus on colors and shapes, but the words inside matter just as much. A study by Unbounce found that changing a button from “Get started” to “Start my free trial” increased clicks by 14.79%. That’s not a typo—just three extra words made a real difference. So how do you write labels that convert? Let’s break it down.

---

Prompt 1: Make Your Buttons Action-Driven and Benefit-Focused

Generic labels like “Submit” or “Continue” don’t tell users what happens next. They’re vague, and vagueness creates friction. Instead, rewrite your buttons to answer two questions:

1. What will the user do? (Action)
2. What will they get? (Benefit)

Here’s how to use Claude for this:

Prompt: “Rewrite this button label to be action-driven and benefit-focused: [insert current label].”

Example Before & After:

• Weak: “Submit”
• Strong: “Get my free report now”
• Weak: “Sign up”
• Strong: “Start my 7-day trial”

See the difference? The strong versions tell users exactly what to expect. No guesswork.

Pro Tip: If your button leads to a form, pair it with a micro-promise. For example:

• Instead of “Subscribe”, try “Get weekly tips in your inbox”.
• Instead of “Download”, try “Download my free checklist (PDF)”.

---

Prompt 2: Add Urgency and Clarity to Your CTAs

Urgency isn’t about being pushy—it’s about helping users decide now instead of later. A button like “Learn more” is fine, but it doesn’t create a sense of importance. Compare these:

• “Learn more” → “See pricing before the sale ends”
• “Get started” → “Start today—only 3 spots left”

Prompt: “Generate 3 alternative CTAs for [specific action] that increase urgency and clarity.”

Example: Let’s say your button is for a limited-time discount. Claude might suggest:

1. “Claim 20% off—ends Friday!”
2. “Save now before prices go up”
3. “Get instant access (offer expires soon)”

Why This Works:

• Urgency (“ends Friday,” “expires soon”) pushes users to act.
• Clarity (“20% off,” “instant access”) tells them what they’ll get.
• Specificity (“only 3 spots left”) makes the offer feel real.

Warning: Don’t overdo urgency. If every button says “Limited time!”, users will stop believing it. Use it for real deadlines or exclusive offers.

---

Before vs. After: A Real-World Example

Let’s look at a SaaS landing page. The original button said:

“Request a demo”

It’s not terrible, but it’s passive. Users have to request something, and there’s no benefit mentioned. Here’s how we improved it:

After: “See how [Product] works—book a 10-minute demo”

Why This Works:

• Action-driven: “See how” is more engaging than “Request”.
• Benefit-focused: “10-minute demo” sets clear expectations.
• Low commitment: “10 minutes” makes it feel easy to say yes.

Result: The company saw a 22% increase in demo requests after making this change. Small tweaks, big impact.

---

Common Mistakes to Avoid

Even experienced designers make these errors with button labels:

1. Being too vague

   • ❌ “Click here”
   • ✅ “Download the guide”

2. Using jargon

   • ❌ “Initiate onboarding”
   • ✅ “Get started in 2 minutes”

3. Making buttons too long

   • ❌ “Click here to get your free ebook now”
   • ✅ “Get my free ebook”

4. Forgetting the benefit

   • ❌ “Submit form”
   • ✅ “Get my custom quote”

Quick Fix: Read your button label out loud. If it sounds like something a robot would say, rewrite it.

---

How to Test Your Button Labels

You don’t need a fancy A/B testing tool to see what works. Try this:

1. Ask a friend: Show them the button and ask, “What happens if I click this?” If they hesitate, your label isn’t clear enough.
2. Use the “5-second test”: Show the button for 5 seconds, then hide it. Can they remember what it said? If not, simplify.
3. Check analytics: If a button has low clicks, try a new version and compare.

Example: A travel site tested two buttons:

• “Book now” (12% conversion)
• “See available rooms” (18% conversion)

The second version worked better because it set expectations—users knew they’d see options before committing.

---

Final Tip: Match the Button to the User’s Mindset

Users go through different stages when interacting with your site. Your button labels should reflect that:

• Awareness stage: “Learn how it works”
• Consideration stage: “Compare plans”
• Decision stage: “Start my free trial”

If a user is just browsing, don’t hit them with “Buy now.” They’re not ready. Instead, guide them gently.

Key Takeaway: Your button labels should feel like a helpful nudge, not a sales pitch. The best CTAs don’t sell—they assist.

B. Error Messages & Validation

Nobody likes seeing an error message. It’s like hitting a dead end when you’re trying to get somewhere fast. But here’s the thing—errors are going to happen. The real question is: How do you make them less frustrating?

Good error messages don’t just tell users something went wrong. They help them fix the problem and keep moving. Think about it: when was the last time an error message actually made you smile? Probably never. But what if it could? What if it could turn a moment of frustration into a tiny win?

That’s where smart microcopy comes in. The best error messages are clear, helpful, and sometimes even a little fun. They don’t blame the user. They don’t use confusing tech jargon. They just solve the problem.

Prompt 3: Turn Technical Errors into User-Friendly Fixes

Let’s say your user sees this: “Error 404: The requested URL was not found on this server.”

What does that even mean? Most people don’t know what a “URL” is, let alone why it’s “not found.” Now, what if we rewrote it like this? “Oops! This page doesn’t exist. Maybe it moved or was deleted. Try checking the link or going back to the homepage.”

See the difference? The first version makes the user feel lost. The second version gives them a next step. That’s the power of good microcopy.

Here’s how to use Claude to fix your error messages:

1. Paste the technical error – Give Claude the exact message your system shows.
2. Ask for a user-friendly version – Use this prompt: “Turn this technical error message into a user-friendly, solution-oriented prompt: [insert error].”
3. Add context if needed – Tell Claude who your users are (e.g., “They’re not tech-savvy”).

For example, if your app shows: “Invalid input: Password must contain at least one uppercase letter, one lowercase letter, one number, and one special character.”

Claude might rewrite it as: “Your password needs to be stronger. Try adding a capital letter, a number, and a symbol like ! or @.”

Which one would you rather see?

Prompt 4: Add Humor (Without Being Annoying)

Humor in error messages? Yes, but carefully. The goal isn’t to make users laugh—it’s to make them less frustrated. A little personality can go a long way, but it has to feel natural.

Take this scenario: A user tries to submit a form, but they forgot to fill in a required field. Instead of: “Error: Field is required.”

What if it said: “Whoops! Looks like you missed a spot. We need this info to keep things running smoothly.”

Or, for a 404 page: “This page took a coffee break. ☕ Try refreshing or heading back home.”

Humor works best when:

• It’s short and subtle – Don’t overdo it.
• It fits your brand voice – A bank’s error message shouldn’t sound like a meme.
• It still solves the problem – The user should know what to do next.

Here’s the prompt to try: “Create a humorous yet helpful error message for [scenario] to reduce frustration.”

For example, if the scenario is “A user tries to upload a file that’s too large,” Claude might suggest: “This file is a little too heavy for us to lift! Try compressing it or picking a smaller one.”

How Slack and Duolingo Make Errors Less Painful

Some companies do error messages really well. Take Slack, for example. If you try to send a message in a channel you don’t have access to, it doesn’t just say “Error: Permission denied.” Instead, it says: “You don’t have permission to post here. Try messaging the channel owner or picking a different channel.”

It’s clear, helpful, and even suggests a solution.

Then there’s Duolingo. If you get an answer wrong, it doesn’t just say “Incorrect.” It says: “Not quite! The correct answer is [X]. Keep going—you’ve got this!”

That tiny bit of encouragement makes users feel supported, not scolded.

The Golden Rules of Error Messages

If you remember nothing else, remember these three things:

1. Don’t blame the user – Avoid words like “invalid,” “failed,” or “wrong.” Instead, say “Almost there!” or “Let’s try that again.”
2. Give a clear next step – Always tell the user what to do next. “Try refreshing the page” is better than “An error occurred.”
3. Keep it simple – If your error message needs an explanation, it’s too complicated.

Error messages don’t have to be boring. With the right prompts and a little creativity, you can turn them into moments that actually help your users. And when users feel helped—not confused or frustrated—they’re more likely to stick around.

C. Tooltips & Hints

Tooltips are like little helpers that pop up when users need them most. They explain features, guide actions, and prevent confusion—without cluttering the interface. But here’s the catch: if they’re too long, too technical, or just plain boring, users will ignore them. And if they’re missing when needed? Frustration sets in.

The best tooltips feel like a friendly nudge, not a lecture. They answer the question, “What’s in it for me?” in seconds. Think of them as micro-moments of clarity—just enough to keep users moving forward, not enough to slow them down.

Prompt 5: Short, Value-Driven Tooltips

“Write a concise, jargon-free tooltip for [feature] that explains its value in 10 words or less.”

Why 10 words? Because attention spans are short. Users don’t want to read a novel—they want to get it and move on. A great tooltip doesn’t just describe what a feature does; it tells users why they should care.

Example:

• ❌ “This button exports your data in CSV format.”
• ✅ “Save time—download your data in one click.”

See the difference? The first version is functional but forgettable. The second version speaks to the user’s goal (saving time) and makes the action feel effortless.

How to use this prompt:

1. Identify the feature you’re writing for (e.g., a “Save as Draft” button, a “Dark Mode” toggle).
2. Ask: What’s the biggest benefit for the user?
3. Write it in plain language, cutting unnecessary words.
4. Test it—does it make sense in under 3 seconds?

Notion does this well. Their tooltips often use simple, benefit-driven language like “Drag to reorder” or “Click to expand.” No fluff, just clarity.

Prompt 6: Progressive Disclosure for Complex Features

“Generate a progressive disclosure tooltip for [complex feature] to avoid overwhelming users.”

Some features are too complex to explain in one go. That’s where progressive disclosure comes in—revealing information in layers, so users aren’t bombarded all at once.

Example: Imagine a “Custom Report Builder” in an analytics tool. A single tooltip might say: “Use this to create reports with custom metrics, filters, and visualizations.”

That’s accurate, but it’s a lot to process. Instead, break it down:

1. First tooltip (basic): “Build reports your way—start here.”
2. Second tooltip (on hover): “Add metrics like sales, clicks, or user activity.”
3. Third tooltip (advanced): “Filter by date, region, or custom segments.”

This way, users learn as they go, without feeling lost.

Why this works:

• Reduces cognitive load – Users only see what they need, when they need it.
• Encourages exploration – Curiosity drives them to hover and discover more.
• Feels less intimidating – Complex features become approachable.

Google does this brilliantly in Gmail. When you hover over the “Schedule Send” button, the first tooltip says “Send later.” If you click, a second layer appears with options like “Tomorrow morning” or “Next Monday.” Simple, intuitive, and stress-free.

When to Use Which Prompt

• Short tooltips (Prompt 5): Best for simple features where the benefit is obvious (e.g., “Undo,” “Share,” “Save”).
• Progressive tooltips (Prompt 6): Ideal for multi-step or advanced features (e.g., “Advanced Search,” “Custom Workflows”).

Common Mistakes to Avoid

• Over-explaining: If your tooltip needs a tooltip, it’s too long.
• Being vague: “Click here for options” doesn’t help. “Customize your dashboard” does.
• Ignoring context: A tooltip for a “Delete” button should warn, not just describe. “Permanently remove this file” is better than “Delete.”

Testing Your Tooltips

Not sure if your tooltip works? Try this:

1. Show it to someone unfamiliar with your product.
2. Ask: “What do you think this does?”
3. If they hesitate or guess wrong, simplify.

The best tooltips feel invisible—users don’t notice them, but they do notice when they’re missing. That’s when you know you’ve nailed it.

D. Form Fields & Placeholders

Forms are where users decide: do I keep going, or do I leave? A confusing label or a vague placeholder can make them quit. But when done right, form microcopy turns friction into flow. It’s not just about asking for information—it’s about making the process feel effortless.

Think about the last time you filled out a form. Did you pause because the label was unclear? Did you wonder what to type in an empty field? These small moments add up. Good form microcopy answers questions before they’re asked. It guides without being pushy. And most importantly, it respects the user’s time.

Prompt 7: Make Labels More Intuitive

“Improve this form field label to be more intuitive: [insert current label].”

Bad labels are like bad directions—they leave users lost. Take a label like “Info” for a phone number field. What does that even mean? Compare it to “Phone number (for delivery updates)”. The second version tells users exactly what’s needed and why. It removes doubt.

Here’s how to test if your labels are working:

• Read it out loud. Does it make sense without context?
• Ask someone unfamiliar with your product. Can they guess what to enter?
• Check for jargon. Words like “username” or “handle” might confuse new users.

Big brands get this right. Airbnb’s form for booking a stay uses labels like “Check-in date” and “Number of guests”—simple, direct, and impossible to misinterpret. LinkedIn’s sign-up form asks for “First name” and “Last name” instead of just “Name”, because it’s clearer and matches how people think about their identity.

Prompt 8: Write Helpful Placeholder Text

“Write a placeholder text that guides users without being redundant: [insert field purpose].”

Placeholder text is tricky. Too vague, and it’s useless. Too specific, and it feels like a demand. The best placeholders strike a balance—they hint at what to enter without repeating the label.

For example:

• Bad: “Enter your email” (redundant—users already know it’s an email field)
• Better: “[email protected]” (shows the format)
• Best: “We’ll send your receipt here” (explains the purpose)

LinkedIn’s job application form uses placeholder text like “e.g., Senior Designer” in the job title field. It’s not just a hint—it sets expectations for the level of detail needed. Airbnb’s search bar says “Anywhere • Any week • Add guests”—a subtle nudge that helps users start planning their trip.

When to Skip Placeholder Text

Not every field needs a placeholder. If the label is already clear (like “First name”), adding placeholder text can clutter the form. Use placeholders only when:

• The format isn’t obvious (e.g., phone numbers, dates)
• The field benefits from an example (e.g., job titles, search queries)
• You can add value by explaining why the information is needed

The Bottom Line

Form microcopy isn’t about being clever—it’s about being clear. Every label and placeholder should answer three questions:

1. What do I enter here?
2. How should I format it?
3. Why do you need this?

When users don’t have to think, they’re more likely to finish the form. And that’s the whole point.

E. Empty States & Onboarding

Ever opened an app and stared at a blank screen, wondering what to do next? That’s an empty state—and it’s a make-or-break moment for user retention. A boring “No items found” message makes users feel lost. But a well-crafted empty state? It turns confusion into opportunity.

The same goes for onboarding. If new users don’t understand your feature in the first 30 seconds, they’ll leave. The right microcopy can guide them, reduce drop-offs, and even make them smile. Let’s look at how to nail both.

---

Prompt 9: Craft an Engaging Empty State Message

“Craft an engaging empty state message for [feature] that encourages action.”

Empty states aren’t just placeholders—they’re mini-conversion opportunities. A great message should:

• Acknowledge the emptiness (don’t ignore it—users notice).
• Explain why it’s empty (e.g., “You haven’t added anything yet”).
• Offer a clear next step (e.g., “Start by creating your first project”).

Example: Spotify’s “Discover Weekly” Empty State When users first open Spotify’s “Discover Weekly” playlist, they see: “We’ll find music you love. Check back later!” Simple, friendly, and sets expectations. No confusion, just anticipation.

How to apply this:

• For a to-do app: “Your list is empty. Add your first task to get started!”
• For a shopping cart: “Your cart is waiting! Browse our bestsellers →”
• For a notes app: “No notes yet. Tap the + button to create your first one.”

The key? Make it feel like a helpful nudge, not a dead end.

---

Prompt 10: Write a 3-Step Onboarding Microcopy Sequence

“Write a 3-step onboarding microcopy sequence for [new feature] to reduce drop-offs.”

Onboarding is like a first date—you want to impress, not overwhelm. A 3-step sequence keeps it simple:

1. Introduce the feature (What is it?).
2. Show the value (Why should they care?).
3. Guide the first action (How do they start?).

Example: Trello’s Onboarding Trello’s onboarding for new boards is genius:

1. “Welcome to your first board!” (Introduction)
2. “Boards help you organize anything—projects, ideas, or even your grocery list.” (Value)
3. “Click ‘Add a list’ to get started.” (Action)

How to apply this:

• For a fitness app:
  1. “Track your first workout!”
  2. “Log your progress to see results faster.”
  3. “Tap ‘Start Workout’ to begin.”
• For a budgeting tool:
  1. “Set up your first budget.”
  2. “We’ll help you save money without the stress.”
  3. “Add your income to get started.”

The goal? Make users feel successful immediately.

---

Why This Works: Lessons from Spotify and Trello

Spotify and Trello don’t just fill space—they design it. Their empty states and onboarding sequences:

• Reduce friction (No guesswork for users).
• Build confidence (Users know exactly what to do next).
• Add personality (A little humor or warmth goes a long way).

Pro tip: Test your microcopy with real users. If they hesitate or ask, “What do I do now?”—it’s not clear enough.

---

Final Thought

Empty states and onboarding are your chance to turn “I don’t get it” into “I love this.” The best microcopy feels invisible—users don’t notice it, but they do notice when it’s missing. So next time you see a blank screen, ask: How can I make this helpful? The answer might just keep users coming back.

F. Confirmation & Success Messages

Success messages are like little high-fives for your users. They tell people, “Hey, you did it!” But too often, these messages feel cold and robotic. “Action completed.” Really? That’s the best we can do?

A good success message does more than just say “done.” It makes users feel good about what they just did. It builds confidence. And sometimes, it even makes them smile. Let’s look at how to turn boring confirmations into something users actually want to see.

Why Generic Messages Fail

Imagine you just signed up for a new app. You fill out the form, click submit, and see: “Registration successful.”

That’s it? No excitement? No next steps? It’s like getting a handshake when you expected a hug.

Generic messages miss a big opportunity. They don’t:

• Reinforce the value of what the user just did
• Guide them forward to the next action
• Build trust by showing the system is working
• Add personality to make the experience memorable

How to Make Success Messages Better

Here’s a simple way to improve them: Be specific, be helpful, and be human.

Take this prompt: “Turn this generic success message into something warm and actionable: [insert current message].”

For example, instead of: “Payment processed.”

Try: “Your payment went through! Your order #12345 is on its way. Check your email for tracking details.”

See the difference? The second version: ✅ Confirms the action (“payment went through”) ✅ Gives a reference number (“order #12345”) ✅ Tells the user what happens next (“check your email”) ✅ Feels friendly, not robotic

When to Use Different Types of Success Messages

Not all success messages should sound the same. The tone depends on the situation:

• For important actions (like payments or sign-ups): “Welcome aboard! Your account is all set. Let’s get started—here’s your first task.”

• For quick actions (like saving a draft): “Draft saved! You can come back anytime to finish.”

• For fun or casual apps (like games or social media): “Boom! Post published. Your friends are gonna love this.”

The key is to match the tone to your brand and the user’s mood. A bank app might keep it professional, while a fitness app can be more energetic.

Don’t Forget the Next Step

The best success messages don’t just say “done”—they guide users forward. Ask yourself:

• What should the user do next?
• Is there a way to make it easier for them?

For example, if someone just uploaded a file, don’t just say “Upload complete.” Try: “Your file is ready! Want to share it with your team? Click ‘Share’ to send it now.”

Small tweaks like this keep users engaged and reduce confusion.

Final Thought

Success messages are tiny moments that add up to a big experience. When done right, they make users feel smart, confident, and happy. When done wrong, they make users wonder, “Did that even work?”

So next time you write a confirmation message, ask: Does this make the user feel good? If not, it’s time to try again. Your users will thank you.