AI Prompts for ChatGPT for UX Writing

Help me define the voice and tone guidelines for [PRODUCT NAME], a [DESCRIBE PRODUCT] for [DESCRIBE USERS]. Our brand personality is: [LIST 3-5 ADJECTIVES, E.G., FRIENDLY, DIRECT, EXPERT, APPROACHABLE]. Write a voice and tone guide that includes: (1) Voice characteristics (3-4 principles with a "we are / we are not" format for each), (2) Tone variations (how voice shifts in different contexts: celebration, error, onboarding, security warnings), (3) 5 dos and 5 don'ts specific to this product, (4) A vocabulary guide (preferred terms, terms to avoid, and any product-specific terminology). Format for a content style guide.

Evaluate whether this product copy matches the voice I described: Voice: [DESCRIBE YOUR PRODUCT VOICE IN 3 ADJECTIVES]. Copy to evaluate: [PASTE COPY FROM BUTTONS, TOOLTIPS, ERROR MESSAGES, ONBOARDING]. For each piece of copy, rate alignment with the voice (1-5), identify what is off (too formal, too casual, unclear, wordy), and rewrite it to better match the voice. Be specific about which word or phrase breaks the voice and why.

Analyze the UX writing voice of these 3 competitors in [PRODUCT CATEGORY]: [COMPETITOR 1, COMPETITOR 2, COMPETITOR 3]. Based on typical product copy in this space, describe: each competitor's apparent voice personality, the vocabulary they favor, how they handle errors and friction points, and where the white space is for differentiation. Suggest 3 specific voice choices our product can make to stand out while still feeling appropriate for this product category.

Write 5 UX content principles for [PRODUCT NAME]. Each principle should be: one short memorable phrase (3-6 words) that captures a core writing guideline, followed by a 2-sentence explanation of what it means in practice, and a concrete before/after example showing bad copy and improved copy that follows the principle. These principles should guide the entire team in making consistent writing decisions across all product surfaces.

Audit this product copy for inclusive language issues: [PASTE COPY]. Check for: gendered language or assumptions, ableist terms or metaphors, overly technical terms that exclude non-expert users, cultural idioms that do not translate, and any language that implicitly assumes a specific demographic. For each issue, provide: the problematic phrase, why it is an issue, and 2-3 alternative options that are clearer and more inclusive. Do not change the meaning or personality of the copy in the process.

Write 8 alternative button labels for [DESCRIBE THE ACTION: E.G., "THE BUTTON THAT SUBMITS A PAYMENT," "THE CTA TO START A FREE TRIAL," "THE BUTTON TO DELETE AN ACCOUNT"]. Include: 3 action-forward options (verb-first, specific), 2 outcome-focused options (what happens after clicking), 2 value-focused options (what the user gets), and 1 conversational option. Note the word count of each and flag any that might be too long for a typical button width. Recommend which 2-3 to A/B test and explain why.

Write clear labels, placeholder text, and help text for these form fields: [LIST THE FIELDS IN YOUR FORM, E.G., EMAIL, COMPANY NAME, PHONE NUMBER, BILLING ADDRESS, CREDIT CARD]. For each field, provide: (1) the field label (clear noun, not a question), (2) placeholder text (example of expected format, not a repeat of the label), (3) help text that appears below (explains why we need this and what we do with it, under 20 words), and (4) inline validation success message (positive confirmation after the user fills in correctly).

Rewrite these navigation items to be clearer and more user-focused: [LIST CURRENT NAVIGATION LABELS]. For each item, write: (1) the current label, (2) what the section actually contains or does, (3) 3 alternative label options, and (4) your recommended label with a brief explanation. Navigation labels should describe what users will find, not what features are called internally. Prioritize clarity over cleverness. If any label could be misunderstood or map to more than one meaning, flag it.

Write empty state copy for these product screens: [LIST THE EMPTY STATES YOU NEED: E.G., NO SEARCH RESULTS, NEW USER DASHBOARD WITH NO DATA, NO NOTIFICATIONS, EMPTY INBOX]. For each empty state, write: (1) a headline (1 sentence, friendly, explains why it is empty), (2) a supporting line (1 sentence, tells the user what to do to populate this section), and (3) a CTA button label. Empty states are opportunities to guide, not just inform. Match the copy to this product's voice: [DESCRIBE].

Write tooltip copy for these product features that users find confusing: [LIST 5-8 FEATURES OR SETTINGS WITH A BRIEF DESCRIPTION OF WHAT THEY DO]. For each tooltip, write: a 1-2 sentence explanation of what the feature does (not what it is named), what the user can expect to happen when they use it, and when they should or should not use it. Tooltips should answer the user's "what is this?" and "should I use this?" in under 40 words. Do not repeat the label name in the tooltip.

Rewrite these error messages to be clearer, more helpful, and less alarming: [LIST YOUR CURRENT ERROR MESSAGES]. For each message, the rewrite should: explain what went wrong in plain language (no technical codes), tell the user what to do to fix it, use a calm and helpful tone, avoid blame language ("you entered the wrong..."), and fit in under 50 words. Also write the error message title (displayed as a header) and the CTA button text for the primary recovery action.

Write inline validation error messages for these form fields: [LIST FIELDS: E.G., EMAIL, PASSWORD, CREDIT CARD NUMBER, DATE, FILE UPLOAD]. For each field, write: (1) the error message when the field is left empty, (2) the error message when the format is wrong (e.g., invalid email format), (3) the error message when the input fails a business rule (e.g., email already in use, password too weak), and (4) the success message when the input is valid. All messages should be specific about what is wrong and how to fix it, not just that something is wrong.

Write copy for these error pages: (1) 404 Page Not Found, (2) 500 Server Error, (3) Maintenance/Downtime page. For each, write: a headline that does not just state the error code, a 1-2 sentence explanation in human terms, 2-3 links or actions to help the user find what they need or recover, and an optional friendly or on-brand detail (for 404 only). The 500 and maintenance pages should: be honest without alarming, give a realistic time estimate if possible, and provide a support contact or status page link. Product voice: [DESCRIBE].

Write error messages for these permission and access scenarios in a [SAAS/APP] product: (1) User tries to access a feature on a lower plan (upgrade prompt), (2) User tries to perform an action they do not have permission for in their role, (3) User tries to access content that has been deleted, (4) User's session has expired and they need to log back in, (5) User hits a rate limit or usage cap. Each message should: explain what happened, why, and what the user can do. Include a CTA for each. Match voice: [DESCRIBE].

Write confirmation dialog copy for these irreversible or high-stakes actions: [LIST ACTIONS: E.G., DELETE ACCOUNT, CANCEL SUBSCRIPTION, PERMANENTLY DELETE FILE, REMOVE TEAM MEMBER, ARCHIVE PROJECT]. For each dialog, write: (1) dialog title, (2) warning body (what will be lost and that it cannot be undone, under 40 words), (3) primary destructive action button label (specific, never just "OK"), (4) cancel button label, and (5) any additional safety mechanism copy (checkbox confirmation, typing to confirm). Copy must be clear enough that no user accidentally clicks the destructive action thinking it does something else.

Write welcome screen copy for a new user's first experience with [PRODUCT NAME]. They signed up to accomplish: [DESCRIBE PRIMARY USER GOAL]. The welcome screen should: address them by first name if possible, confirm what the product does for them in one sentence, set an expectation for what they will be able to do after completing setup, and include a CTA to start the onboarding flow. Keep it under 80 words including the CTA. Warm and encouraging but not over-the-top. No clichés like "You're all set!" or "Welcome aboard!"

Write the items for an onboarding checklist for [PRODUCT NAME]. The top 5 setup steps a new user should complete are: [LIST STEPS]. For each checklist item, write: (1) the task title (verb-first, under 5 words), (2) a one-sentence description of what this does and why it matters, (3) the CTA button label, and (4) the completion state message (what appears after they complete this step). The checklist should feel like a guide, not a to-do list. Each item should feel achievable and the benefit should be clear.

Write the copy for a first-run tooltip tour of [PRODUCT NAME]. The tour has [X] steps and covers these features: [LIST FEATURES IN ORDER]. For each tooltip, write: (1) tooltip title (optional, max 5 words), (2) body copy (what this feature does and why they care about it, under 35 words), (3) CTA/next button label, and (4) position note (which UI element is being pointed to). The tour should tell a story of how the user will do their work, not just describe each feature. Step 1 should set the overall narrative, and the final step should celebrate that they are ready to start.

Write the copy for a paywall modal that appears when a [FREE/TRIAL] user tries to access a paid feature: [DESCRIBE THE FEATURE]. The modal should: name the specific feature they tried to access, explain what they can do with it (benefit, not feature description), show 2-3 other paid features they are also missing, include a clear upgrade CTA, and include a softer "Maybe later" escape. Under 120 words total. Do not use fear-based language. Write in the product voice: [DESCRIBE]. The goal is to make upgrading feel like the obvious and exciting next step.

Write success and completion messages for these key moments in [PRODUCT NAME]: (1) User completes onboarding setup, (2) User sends/publishes/submits their first [CORE ACTION], (3) User reaches a usage milestone (e.g., 10th project, 100th task), (4) User successfully connects an integration, (5) User's first collaboration invitation is accepted. For each, write: a celebration headline (1 line, specific to the achievement, never "Congratulations!"), a supporting line (what they can do now or what just got better), and an optional next-step CTA. Match voice: [DESCRIBE].