35 Prompts for UX Microcopy and In-App Text
Tallybox files roughly 90,000 personal returns in the last three weeks of March, and every support ticket that starts with “the button said” costs a human reply that costs the team a filing slot. Last season 2,400 users abandoned the deductions step because a greyed-out button gave no reason why it was disabled, and nobody could explain the refund timing in one sentence. The 35 prompts below rewrite the small text that causes most of that drag: buttons, empty states, errors, permission prompts and receipts. For the voice decisions behind them, use the tone of voice decision table, and clean up the output with our editing and proofreading prompts.
Buttons, Links and Field Labels
A button is the shortest copy you will ever write, and the one users read most.
1. Primary button labels for the final submit action.
Write five button label options for submitting a personal tax return in Tallybox, replacing "Submit". Each label under 4 words, must say what happens next, and must not sound final when a review step remains. Context: [paste].2. The save-and-exit button.
Write three button labels for saving a partly finished Tallybox return and leaving. Each must make clear the draft is saved, not submitted. Under 4 words, calm tone, no jargon. Context: [paste].3. The disabled-button reason, shown on tap.
A button in Tallybox is disabled until a required field is filled. Write the helper text explaining why, under 14 words, naming the exact field to fix. Friendly, never blaming the user. Field: [paste].4. Link text for “why we ask this”.
Write the link text and the 40-word panel behind it for a Tallybox field about a taxpayer ID. Explain in plain words why the number is needed and how it is stored. No policy language, no all caps. Field: [paste].5. Field label for the tax ID number.
Write the field label and one helper line for the tax identification number in Tallybox. Avoid the phrase "SSN or TIN" as a label; spell out what the user should type. Under 15 words total. Context: [paste].6. Placeholder text for an income field.
Write placeholder text for an income amount field in Tallybox. Show the format, for example no currency symbol and no commas, and make clear it is yearly. Under 10 words. Context: [paste].7. Toggle label for direct deposit.
Write the on and off labels plus one helper line for the direct deposit toggle in Tallybox. Explain what happens in each state, and what the user needs to have ready. Under 25 words. Context: [paste].8. Helper text under a confusing field.
Users keep mistyping this Tallybox field. Write helper text that prevents the error before it happens: name the format, give one example, and say where to find the number. Under 20 words. Field: [paste].Empty States, Loading and Progress
An empty screen is a chance to teach the next action instead of showing nothing.
9. Empty state for no documents uploaded.
Write an empty state for the Tallybox documents screen before anything is uploaded. Include a headline under 6 words, one sentence on what to add, and a clear button label. Encouraging, not scolding. Context: [paste].10. Empty state for no deductions added.
Write an empty state for the deductions step when a user has added nothing. Mention two common examples, for example work-from-home or charity, and reassure them they can skip and return. Under 45 words. Context: [paste].11. Loading message during a long calculation.
Write a loading message for a Tallybox calculation that can take 20 seconds. Give the user something truthful about what is happening and a fallback if it fails. Under 20 words, no fake percentage. Context: [paste].12. Progress label for the five-step flow.
Write the step labels for a five-step Tallybox flow so the user always knows where they are and what is left. One to three words per label, plus one line on how the steps are named in the progress bar. Context: [paste].13. Skeleton text for a slow list of entries.
Write placeholder language for a Tallybox list that loads slowly. Describe what a good skeleton state says to the user and give the one line of text to show, under 12 words. Context: [paste].14. Zero-results state in search.
Write a zero-results state for the Tallybox help search. Restate the likely intent, suggest a broader term, and offer a way to contact support. Under 40 words, one link, no dead end. Query: [paste].15. Success state after a step completes.
Write the success message after a Tallybox user completes a step. Confirm what was saved, name what comes next, and keep it under 15 words. Warm but not celebratory, since tax filing is not a game. Context: [paste].Error Messages and Validation Copy
An error should say what went wrong, why, and the exact fix, in that order.
16. Error when a required field is empty.
Write an inline error for an empty required field in Tallybox. State the field name, what to enter, and how to get the value. Under 15 words, no "invalid" and no error codes. Field: [paste].17. Error when an ID fails its checksum.
Write an error for a Tallybox ID number that failed validation. Explain the most likely cause, point to the exact digits to recheck, and say what to do if it keeps failing. Under 30 words. Value: [paste].18. Error when a figure is out of range.
Write an error for an amount in Tallybox that is above the allowed limit. Give the accepted range, restate what the user typed, and suggest the common fix, such as entering a monthly figure instead of yearly. Under 30 words. Context: [paste].19. Error when the session times out.
Write a timeout message for Tallybox. Reassure the user that their answers are saved, say exactly what to do to continue, and put the action first. Under 25 words, no security lecture. Context: [paste].20. Error when an upload fails.
Write an upload failure message for a Tallybox document scan. Name the three likely causes, for example file size, format or connection, and give one retry step. Under 30 words, reassuring tone. Context: [paste].21. Error when two entries do not match.
Write an error for two Tallybox values that should match but do not. Point to both fields, explain the mismatch in plain words, and tell the user which one to check first. Under 30 words. Fields: [paste].22. A non-blocking warning for an unusual refund.
Write a warning, not an error, for a Tallybox refund that looks unusually high. Say it is not a problem yet, what usually causes it, and that a human may review it. Under 35 words, no alarm. Context: [paste].Onboarding, Permission and Consent Prompts
Ask once, explain plainly, and never block a task behind a permission you do not need yet.
23. Welcome screen copy.
Write a Tallybox welcome screen: a headline under 8 words, one sentence on what the app does, and two button labels for starting or resuming a return. Under 45 words total. Context: [paste].24. Permission prompt for connecting a bank account.
Write a pre-permission explanation before Tallybox asks to connect a bank. State the benefit, what data is read, and that the user can enter figures by hand instead. Under 40 words, no pressure. Context: [paste].25. Camera permission for document scanning.
Write the rationale Tallybox shows before requesting camera access. Explain that it is only for photographing tax documents, that images stay on the device unless uploaded, and that typing is still an option. Under 35 words. Context: [paste].26. Notification permission rationale.
Write the reason Tallybox gives before asking to send notifications. Name the two notification types, such as deadline reminders and status updates, and confirm they can be turned off anytime. Under 30 words. Context: [paste].27. Consent for sharing data with a preparer.
Write a consent screen for sharing a Tallybox return with an accountant. Explain exactly what is shared, for how long, and how to revoke access. Plain language, under 60 words, with a clear yes and no. Context: [paste].28. The privacy one-liner at signup.
Write a single privacy line for the Tallybox signup screen. Say in plain words what is done with the email address and link to the full policy. Under 20 words, no legal phrasing. Context: [paste].29. Biometric login opt-in.
Write the opt-in copy for Face ID or fingerprint login in Tallybox. Explain the convenience, confirm the data stays on the device, and make clear it is optional. Under 30 words, calm and factual. Context: [paste].Notifications, Receipts and Post-Submit Text
After the deadline the user is stressed. Short, factual text is the kindest kind.
30. Push notification when a return is accepted.
Write a short push notification for a Tallybox return that was accepted by the tax office. Confirm the status, state the next likely step, and stay under 20 words. Sober tone, no confetti language. Context: [paste].31. Email receipt after submission.
Write a submission receipt email for Tallybox. Include the confirmation reference, the submission time, a one-line summary of what was filed, and how to download the copy. Under 130 words. Context: [paste].32. Reminder when a draft is left open.
Write a reminder for a Tallybox user who has an unfinished return two days before the deadline. Name the step they stopped at, keep it under 30 words, and give one direct link back. No guilt. Context: [paste].33. Text for a rejected return.
Write the message for a Tallybox return the tax office rejected. Explain in plain words what the rejection means, whether it is usually easy to fix, and the next step, without alarm. Under 60 words. Reason: [paste].34. Refund timing message, in one sentence.
Rewrite this Tallybox refund timing text as one clear sentence. Say when the money leaves, how it arrives, and what affects the timing. No dates we cannot control. Text: [paste].35. The “start next year’s return” nudge.
Write a nudge for a Tallybox user who just filed, inviting them to start next year's return or set a reminder. Under 30 words, no upselling, and make declining easy. Context: [paste].Bonus: Shipping Microcopy Before a March Rush
Name the fix, not the failure. Every error should end with the exact action, because “invalid entry” costs a support ticket and “check the last four digits” does not. Test the button text on the screen it sits on. Short labels pass review and fail on a 360px phone. One idea per string. If a message needs a comma splice, split it. Write the empty state before the feature ships, since the first user sees nothing else. Keep a single glossary so the same concept is never “refund” in one place and “rebate” in another. To decide how much personality each screen can carry, use the funnel stage copy picker as a second check.
Sources & Notes
Prompts were tested with a GPT-4o class model through 2025 and are model-agnostic. Tallybox, the 90,000 returns and the 2,400 abandoned filings are fictional; use your own product, screens and support data. Microcopy prompts generate options, not compliance. Every line about tax, refunds, deadlines or data handling must be checked against current law and your privacy policy by someone accountable, and any string that promises a timing or an amount should be removed rather than softened.
