The Words Around the Boxes: Auditing the Microcopy on Your Enquiry Form

Most enquiry forms don't fail at the boxes. They fail in the gaps between them.

You can have a clean, three-field form and still watch people drift away at the label, the help text, the error message, or the suspicious silence after they press send. In the UK, where we are culturally primed to avoid hassle, embarrassment and being sold to, those tiny bits of copy are doing more work than the design ever will. They are the difference between a form that feels like a conversation and one that feels like a customs declaration.

Here's how to audit yours, field by field.

Labels: say what you need, not what your CRM calls it

Labels are the first place goodwill leaks. If your field says 'Forename' and theirs says 'Name', you've introduced a tiny moment of doubt. If it says 'Organisation' and they're a sole trader, they pause. If it says 'Nature of enquiry' and they don't yet know what kind of enquiry it is, they leave.

The fix is almost always shorter and plainer. 'Your name' beats 'Forename'. 'Where you work (optional)' beats 'Organisation'. If a field isn't essential to replying, mark it optional and mean it — don't hide it behind an asterisk and a scolding note at the top.

Before: 'Please complete all mandatory fields marked with an asterisk.'

After: 'Only your name and email are required. Everything else just helps us reply properly.'

Help text: the quiet reassurance

Help text is where you answer the question they're too polite to ask. It's also where most forms go silent at exactly the wrong moment.

A budget field is the classic. Left bare, it reads like a trap. With a line underneath, it becomes a shortcut.

Before: 'Budget'

After: 'Budget (optional). A rough range is fine — it helps us tell you what's realistic before anyone books a call.'

Same field, same data, entirely different risk profile. That's the job.

Error messages: don't scold the customer

Error copy is where British politeness meets bad software. 'Error: invalid input' is technically true and emotionally useless. 'You must enter a valid email address' sounds like a form telling you off.

The test is simple: would you say it out loud to someone standing at your desk? If not, rewrite it.

Before: 'Error: invalid input.'

After: 'That email looks like it's missing an @ — mind checking it?'

Before: 'Submission failed.'

After: 'Something went wrong at our end. Your answers are still here — try the button again, or email us at hello@ and we'll pick it up.'

The privacy line: cut the wallpaper

'We take your privacy seriously' is the copywriting equivalent of a firm handshake and no eye contact. It tells the reader nothing, and UK buyers have seen it on every cookie banner since 2018.

What they actually want to know is: who sees this, what will you do with it, and will you ring them on a Sunday. Answer in one plain sentence, then link to the full privacy notice for the people who want it.

Before: 'We may share your data with selected third parties for marketing purposes.'

After: 'Your details stay with us. We'll only use them to reply to this enquiry. Full privacy notice here.'

That second version is shorter, warmer and considerably less alarming. It also does the legal job, which is the point.

The button: a verb, not a verdict

'Submit' is what you do to a tax return. It is not what you do when you're asking a question. Buttons should name the next step in the customer's language.

Before: 'Submit'

After: 'Send my enquiry' or 'Ask us a question'

Small change, but it turns a compliance action into a human one. The same logic applies to the bit underneath: 'We aim to reply within one working day' is worth more than any amount of 'We value your enquiry.'

After they press send: the bit everyone forgets

Most forms end with 'Thank you for your submission.' It's the copy equivalent of a door closing. The reader has just done something slightly brave — they've admitted they might need help — and the form replies like a parking meter.

Before: 'Thank you for your submission. A member of the team will be in touch.'

After: 'Got it — thanks. You'll hear from us within one working day. If it's urgent, email hello@ and we'll come back faster. Check your junk folder just in case.'

That version answers the three questions every submitter has: did it work, when will I hear, and what do I do now.

A quick before-and-after

Here's the whole thing stitched together.

Before: 'Contact us. Please complete all mandatory fields. We take your privacy seriously. A member of the team will respond in due course. Submit.'

After: 'Tell us what you need. Two minutes, and a real person will reply within one working day. Your details stay with us — full privacy notice here. Send my enquiry.'

Same form. Same fields. But one reads like a conversation and the other reads like a council form.

The audit checklist

Print this off and go through your form line by line.

• Does every label use the word the customer would use?
• Is anything marked required that doesn't actually need to be?
• Does each tricky field have one line of help text underneath it?
• Do your error messages sound like a person, not a system?
• Have you replaced 'we take your privacy seriously' with a plain sentence?
• Does the button say what happens next?
• Does the confirmation page tell them what happens next, and when?
• Read the whole form out loud. Anywhere you'd feel awkward saying it to a customer, rewrite it.

Forms are conversations with a submit button. The sooner the words around the boxes sound like you, the sooner the enquiries start arriving.