7 microcopy changes that help more people finish your forms

Most form advice is about structure: fewer fields, one column, sensible order. All good. But once the structure is sorted, there’s a layer most teams never touch, which is the words. The label above the phone field. The text on the button. The error message that appears when someone types their postcode with a space in it.

These words are tiny, and they get written last, usually by whoever was building the form at 17:30 on a Thursday. Yet they’re the moment of decision. A visitor hovering over “Submit” is weighing up whether this is worth it, and every word in their eyeline is either helping or quietly getting in the way.

Here are seven changes we’d make to almost any enquiry form. None needs a developer for more than a few minutes.

1. Replace “Submit” with what actually happens next

“Submit” describes an action from the system’s point of view. Nobody wants to submit anything. They want a valuation, a quote, a callback, a viewing.

Write the button as the outcome:

• “Get my valuation”
• “Request a callback”
• “Book my test drive”
• “Send my question”

It’s a small change that does two jobs. It reminds the visitor why they started, and it sets an expectation. Which brings us to the next point.

2. Say what happens after they press the button

Uncertainty is a quiet form killer. Will someone ring me within the hour? Will I be added to a newsletter? Is this going into a void?

A single line under the button settles it: “We’ll call you back within one working day. No newsletter, no spam.” Or for an estate agency: “A local agent will contact you to arrange a convenient time.” Only promise what you’ll actually deliver, of course. If replies currently take three days, fix that first; our piece on speed to lead explains why it matters more than the copy.

3. Explain why you’re asking for the awkward fields

Phone number is the classic. People hesitate because they picture a pushy sales call at dinner time. If you need the number, say why, in plain words, right next to the field:

• “So the agent can confirm the viewing time.”
• “Only used if we need to check a detail of your quote.”

The same goes for budget, company size, or anything else that feels personal. A short reason turns “why do they want to know?” into “fair enough”. If you can’t write a convincing reason for a field, that’s a strong hint it shouldn’t be there at all.

4. Use labels that sound like a person asking

Compare “Requirements” with “What do you need help with?” Or “Timeframe” with “When are you hoping to get started?” The second version of each is longer, and it’s easier to answer, because it’s a question with an obvious shape. “Requirements” could mean anything; people stall on it because they’re not sure how much to write.

This is the principle behind conversational forms, where each step reads like a question from a helpful colleague. You don’t need to rebuild your form to borrow the idea. Rewrite each label as the question you’d ask across a desk. We go further into this in how to write a conversational form, and if you’d rather not hand-build one, Serviceform makes conversational forms that ask one question at a time and send the answers to your CRM as fields.

5. Write error messages that fix the problem

“Invalid input” is the worst sentence on the internet. It tells the visitor they’ve failed without telling them how to stop failing.

A good error message does three things: it says which field, says what’s wrong, and shows what right looks like.

• Instead of “Invalid phone number”: “Please include your area code, for example 020 7946 0000.”
• Instead of “Required field”: “We need your email to send the valuation.”

Better still, be forgiving before you’re helpful. Accept postcodes with or without spaces. Accept phone numbers with brackets and dashes. Strip the stray space someone pasted after their email address. Every error you prevent is one fewer moment where the visitor wonders whether this is worth the hassle.

6. Put reassurance where the doubt is, not in the footer

Most sites have a privacy policy, some trust badges and a line about data protection somewhere at the bottom of the page. That’s not where the doubt happens. The doubt happens at the email field, the phone field and the button.

Move the reassurance there, and keep it short:

• Next to email: “We’ll only use this to reply to you.”
• Under the button: “Takes about a minute. No obligation.”
• On a valuation form: “Free, and you’re under no obligation to sell.”

Valuation forms are a good place to see this done well, because the doubt is so specific: am I about to be pestered into listing my home? The Uprealer demo estate agency is a handy place to try a seller’s journey yourself and notice where you’d hesitate.

A long privacy paragraph above the form doesn’t reassure anyone; it just looks like small print. One honest sentence in the right place does more than a paragraph in the wrong one.

7. Make optional fields obviously optional (or remove them)

If a field is optional, label it “(optional)”. Asterisks on required fields are a convention many visitors don’t notice, and some assume every field is mandatory, so they abandon a form that was actually short.

Then ask yourself a harder question: if the field is optional, why is it there? Sometimes there’s a good reason, like an “Anything else we should know?” box that genuinely helps the salesperson. Often it’s a leftover from a previous version, or something the CRM happens to have a slot for. Optional fields still make the form look longer, and looking long is a cost even when nobody fills them in.

How to test these without a big project

You don’t need a formal A/B testing programme to start. A sensible approach:

1. Pick your highest-traffic form, usually the main contact or valuation form.
2. Make two or three of the changes above at once. Button text, a line of reassurance, and better error messages is a good bundle.
3. Compare completion over a few weeks against the same period before. Look at how many people started the form versus how many finished it, if your tools can show you that.
4. Read the actual enquiries. Are they better or worse quality? Clearer answers to friendlier labels is a common, welcome side effect.

If your traffic is low, don’t over-read small differences. A form getting 40 starts a month won’t give you a statistically meaningful answer for a while, and that’s fine. Many of these changes are simply better writing, and you don’t need a test to justify being clearer.

Before you close the tab

Microcopy is where your form either sounds like a helpful person or like a database asking for records. Rewrite the button as an outcome, say what happens next, give reasons for awkward fields, label things as questions, write errors that fix things, put reassurance at the point of doubt, and be honest about what’s optional. It’s an afternoon’s work, and it’s one of the few conversion improvements you can make with nothing more than a text editor and a bit of empathy.