Skip to content
Putting technology to work.
Insights to guide decisions and action.

Search articles

Preventing drop-offs with microcopy: Refining button and form copy through client delivery

Table of contents · 9 items

On a newly redesigned website with clean visuals, inquiries still fail to pick up. Analytics show that users reach the form, yet midway through input or right in front of the submit button, they vanish. When we open these forms during consultations, the root cause is frequently the words. The submit button simply says "Submit," required fields are marked only with an asterisk, and errors display only "Input error." The visual design was outsourced, but the text was filled in internally like filling blanks in a template — and that hastily assembled copy is dropping users at the final hurdle.

In UX writing, these small pieces of on-screen text are called microcopy. Button labels, form help text, placeholders, error messages, empty states when data is absent, and closing lines on confirmation or completion screens: all are easily overlooked snippets of just a few words. Yet they are the exact words users see at the critical moment of deciding whether to proceed with an action. This article looks past layout structures and psychological triggers to focus strictly on the words themselves, using concrete examples to show what to rewrite and how to reduce drop-offs.

Why words alone can shift conversions

Microcopy works because it sits immediately before a user's decision. People rarely abandon forms out of laziness; they abandon them out of anxiety. Why is this field required? How will my submitted information be used? Will I receive sales calls if I submit? An error appeared, but what do I fix and how? When these small uncertainties accumulate, users close the tab, deciding to do it another time.

Microcopy is the tool that dispels those anxieties on the spot, one by one. It requires neither changing layouts nor implementing new features. Because it only involves rewriting existing text, modification costs are low and results are straightforward to verify. Before overhauling designs or site architectures, improving copy first often yields a higher return on investment. The broader picture of diagnosing underperforming sites is outlined in How to Fix Websites That Get No Inquiries (GH Media), and copy optimization is the quickest measure to tackle within it.

Button labels — describing what happens with a verb

Where copy changes produce the most immediate impact is button labels. On many sites, the final button on a form simply reads "Submit." While technically correct, "Submit" reflects system mechanics, not what the user gains. What users want to know is: "What happens for me if I press this button?"

Therefore, phrasing button labels as verbs describing the result the user receives lowers the psychological hurdle to clicking.

Poor phrasingImproved phrasingWhy it improves
SubmitRequest a free consultationCommunicates the post-click outcome and the reassurance of being free
RegisterGet MaterialsMakes it clear what the user will receive
ConfirmReview Entered DetailsClarifies what is being reviewed, reducing hesitation

Simply changing "Submit" to "Request Free Consultation" transforms the button from a chore into a beneficial action. What matters here is that the label does not exaggerate or hype. If a consultation carries a fee but is labeled "Free," it becomes deceptive design. Write honestly about the outcome based on facts. This boundary directly aligns with the mindset in Designing Honest Consent and Cancellation Flows That Avoid Dark Patterns (GH Media).

Form help text and placeholders — preemptively dispelling anxiety

Help text accompanying each form field is another primary arena for microcopy. Taking a phone number field as an example, displaying only "Phone Number (Required)" causes users to become defensive, wondering why a phone number is necessary and whether they will receive unsolicited sales calls. Adding a brief explanation of purpose and reassurance substantially reduces reluctance to input information.

For example, rewrite it like this:

  • Poor: Phone Number (Required)
  • Improved: Phone Number (Required). We request this to verify your response. We will not use it for sales calls.

Placeholders also require care. A frequent mistake is placing the field label itself, such as "Name" or "Email Address," inside the placeholder. Because this text disappears once typing begins, users lose track of what the field was for. Rather than using placeholders as substitutes for labels, it is safer to treat them as examples of the input format. Showing specific examples like "e.g., yamada@gleamhub.net" or "e.g., 03-1234-5678" ensures users know exactly what format to use without confusion.

Placing short notes such as "Takes about 3 minutes to complete" or "Your information will only be used to respond to your inquiry" at the top of the form or near the submit button is also effective. Knowing the required time makes it easier to decide whether to complete it now or later, and explicitly stating data handling eliminates worries about whether it is safe to submit. Comprehensive form optimization tactics are detailed in How to Approach Form Optimization (EFO) (GH Media).

Error messages — offering guidance rather than assigning blame

Error messages appear at the exact moment a user is most frustrated. Even so, many sites continue to display vague text such as "Input error" or "Invalid value," leaving users clueless about what to correct. The role of an error message is not to call out mistakes, but to show how to move forward.

A good error message satisfies three criteria: it explains specifically what went wrong, supplements why if necessary, and indicates how to fix it. Rewriting with this in mind produces the following:

Poor phrasingImproved phrasing
Input errorEmail address does not contain an "@". Example: yamada@gleamhub.net
Invalid valuePlease enter your phone number using numbers without hyphens
An error occurredConnection failed. Please press the submit button once more

When you explain that the email address is missing an "@", users can fix it themselves while looking at the screen. A message like "Input error" does not even clarify which field has a problem, causing users to abandon the form altogether.

Error copy is equally vital for users relying on assistive technology. Screen readers vocalize text and markup rather than visual styling. If an error is represented solely by an asterisk or a red border, no meaning is conveyed via audio. Writing errors in concrete words and marking them up correctly produces forms that are clear to everyone. This perspective is reiterated throughout our Practical Web Accessibility Guide (GH Media).

Empty states and confirmation screens — placing words in emptiness and endings

Words used when data is absent (empty states) and after an operation finishes (completion screens) are frequently overlooked. For instance, in a member portal, displaying only "No data" on an empty list leaves users wondering whether something is broken or if they missed a step. Rewriting this to "No projects registered yet. You can add your first project via 'Create New' in the upper right" turns the empty state into a guide for the next action.

The same applies to completion screens. Instead of ending with "Submission complete," writing "Thank you for contacting us. A team member will reply within two business days. A confirmation email has been sent automatically for your records" confirms that the message arrived and clarifies what happens next, allowing users to leave the screen with peace of mind. The silence immediately following submission is when user anxiety peaks.

Consistency in voice and tone, and rephrasing

Alongside polishing individual text snippets, maintaining a consistent voice and tone across the entire site is essential. If one page uses polite honorifics, another is casual, and form errors sound cold and bureaucratic, users subconsciously perceive the inconsistency, eroding trust in the site. Deciding whom you are speaking to and what personality you project, and applying that consistently from buttons to error messages, gives the site a cohesive core.

Another easily forgotten aspect is rephrasing technical jargon. Terms that creators take for granted may not make sense to users. "Incorrect email address or password" is clearer than "Authentication failed"; "Search" is clearer than "Execute query"; and "Send" is clearer than "Submit." Rephrasing words to match the reader's vocabulary makes the interface dramatically more approachable. Accurate phrasing influences the overall brand impression, which connects directly with our discussion in Preparing for the Risk of AI Search Misrepresenting Your Business (GH Media) regarding how accuracy in wording protects a brand.

Our process in client projects — starting with a copy audit

When we improve microcopy in our client projects, we always begin with a complete audit of all on-screen text. Consider a recent case supporting Company B, a regional building materials supplier. Company B had had their site redesigned by a web agency, yet form completion rates stagnated. While the visual design was polished, the copy remained straight from templates: buttons said "Submit," errors read "There is an error in your input," and the phone number field lacked any statement of purpose.

Leaving the design and structure untouched, we revised only the copy. We changed the button to "Request a Free Quote," updated error text to specific instructions per field, and added "We will use this to contact you regarding your quote. We will not place sales calls" to the phone field. At the top of the form, we specified the time required: "Takes about 1 minute to complete." Because this was purely a copy revision, implementation took only half a day. As a result, the percentage of users reaching the form who completed submission noticeably improved. It is an example of how copy adjustments alone can move business metrics without a major rebuild.

In our custom work, we avoid treating copy improvements as an intuitive art; we structure them into a process of auditing, verbalizing rewriting guidelines, and comparing before-and-after results. Our scope of delivery extends to documenting voice and tone guidelines so that tone remains consistent regardless of who maintains the site later.

Starting with a review of submit buttons and error copy

Microcopy improvements do not require rebuilding a site and can be started today. As a first step, try reading your site's submit button labels and form error messages out loud. If they still say "Submit" or "Input error," rewriting them to reflect what the user gains and specific guidance on how to fix issues will immediately reduce drop-offs.

If it is difficult to evaluate your site objectively or if you want help prioritizing where to begin, we can join you starting from an audit of your forms and error messages. Please feel free to reach out via our contact page.

Sources

Share this articleXFacebook
Kakeru Suzuki

Fascinated by the possibilities of technology, has had a deep interest in programming and digital art since student days

Turn this article's theme into your company's next step

Starting from what you want to achieve with your website.

We organize user goals, required features, and ongoing maintenance structures to determine the first steps in development and improvement.

  • Website objectives
  • Features and usability
  • Post-launch operations
Consult on web development and improvements

You can consult with us from the initial conceptual stage. Details from this article will be carried over to the inquiry form.

Receive the latest articles via email · Read the web production guide
Free download

Complete Guide to Web Production: Costs, Vendor Selection & Traffic Acquisition [2026 Edition]

We have compiled cost benchmarks, vendor selection criteria, and traffic acquisition strategies into a PDF.

The PDF and newsletter emails are currently in Japanese.

You will also be subscribed to our newsletter. You can unsubscribe at any time.