Creative ThinkingPremiumintermediate

UX Microcopy That Guides, Delights & Reduces Friction

Write every tiny text element in your product — buttons, tooltips, errors, empty states — so users never feel lost.

Copy & Paste this prompt

You are a UX writer who has worked at Slack, Stripe, and Notion. Write microcopy for the following product context.

Product: [YOUR PRODUCT/APP NAME]
Product Type: [SaaS / mobile app / e-commerce / marketplace / other]
Brand Voice: [CASUAL / PROFESSIONAL / PLAYFUL / TECHNICAL — or paste your voice guide]
User's Current Context: [WHAT THE USER IS TRYING TO DO]

Write microcopy for ALL of these touchpoints:

1. **Empty States** (3 variations)
   - First-time user (onboarding)
   - No results found (search)
   - Empty list/dashboard
   For each: headline, body text, CTA button text

2. **Error Messages** (5 types)
   - Form validation error
   - Server error (500)
   - Network/connectivity error
   - Permission denied
   - Rate limited / too many requests
   For each: title, description, action button, tone note

3. **Success Messages** (3 types)
   - Action completed
   - Item saved/created
   - Upgrade/purchase complete

4. **Confirmation Dialogs** (3 types)
   - Delete something
   - Cancel subscription
   - Leave page with unsaved changes
   For each: title, body, confirm button, cancel button

5. **Loading States**
   - Initial load
   - Processing action
   - Long-running task

6. **Tooltips & Helper Text** (5 examples)
   - Complex form field explanation
   - Feature discovery hint
   - Keyboard shortcut callout

7. **CTA Buttons** (10 alternatives)
   - Instead of generic "Submit", "OK", "Continue"
   - Context-specific, action-oriented

Rules:
- Every message must be under 25 words
- Never blame the user
- Always give a next step
- Match the product's voice consistently

#creative#design#microcopy#that#guides

Works with

chatgptclaudegemini

💡 Pro Tips

•Paste your actual brand voice guide for perfectly matched microcopy — generic requests get generic copy
•Test error messages by showing them without context — if someone can't understand what went wrong and what to do, rewrite
•The best CTAs describe what happens AFTER the click, not the click itself ('Start Free Trial' > 'Submit')

✨ Example Output

## UX Microcopy: TaskFlow (Project Management SaaS, Casual Voice)

### Empty States
**First-time dashboard:**
Title: "Your command center awaits"
Body: "Create your first project and watch the magic happen."
CTA: "Start a Project" (not "Get Started")

**No search results:**
Title: "Nothing here... yet"
Body: "Try different keywords or check your filters."
CTA: "Clear Filters"

### Error Messages
**Form validation:**
Title: "Almost there!"
Body: "This email doesn't look right — mind double-checking?"
Action: "Fix & Retry"

**Server error:**
Title: "Well, that's embarrassing"
Body: "Something broke on our end. We've been notified."
Action: "Try Again" | "Contact Support"

**Permission denied:**
Title: "This door's locked 🔒"
Body: "You'll need admin access for this. Ask your team owner."
Action: "Request Access"

### Confirmation: Delete
Title: "Delete 'Q2 Marketing Plan'?"
Body: "This removes the project and all its tasks. Team members will lose access."
Confirm: "Yes, Delete Project" (red)
Cancel: "Keep It"

### CTA Alternatives
❌ Submit → ✅ "Save Changes"
❌ OK → ✅ "Got It"
❌ Continue → ✅ "Next: Add Team Members"