Take an enquiry
For a business that sells by conversation: a charter, a commission, a project. The visitor can't buy on the page, so the page's job is to make asking easy and to say honestly what happens next.
When to use it
- Yes: the price or the answer depends on details only the visitor has, and a person will reply.
- No: something with a fixed price that can simply be bought, or a newsletter sign-up (one field).
How it works
- One way in, from everywhere. The same words lead to the same page: "Start an enquiry" at the end of an article, "Enquire about Sea Hare" on a yacht. A page about one thing carries that thing with it (
/enquire/?yacht=Sea+Hare), so nobody types what the site already knows. - Ask what helps you answer, and nothing to weed people out. Headland asks fifteen things and requires three: a name, an email address and how many adults. Everything else can be left, and "Not sure yet", "No preference" and "Prefer not to say" are real choices in the lists.
- Say why you're asking where it isn't obvious, under the field: "Optional, if you'd like a call"; "Their ages, in the notes below, help us choose the right crew".
- Say what happens next, beside the form, as numbered steps, and what the enquiry is not: "No booking or payment is taken on this website, and an enquiry doesn't commit you to anything."
- Promise a time you keep. "Within one working day", and whose working day: "We're a UK company, so we answer during UK working hours."
- Ask before using anything sensitive. If the notes may hold allergies, health or access needs, a tickbox asks to use them and share them with whoever needs them, with a link to the privacy policy.
- Send, and lose nothing. The button says "Sending…". If it fails the form keeps every word and the message gives another way: the email address. If it works, a short thank-you says when to expect a reply.
- Always offer the other way. An email address and a phone number sit beside the form for people who would rather not fill one in.
A question, or an enquiry
A business usually gets both: "how does this work?" and "I'd like to go ahead". They want different forms. The contact page holds both behind a switch (contact.alternate in the site's config), with the one most people come for first, and the enquiry has an address of its own that opens straight on it.
What it's built from
| Part | Does |
|---|---|
| Contact page | The page, both forms, the switch between them and the side panel, from the site's config and its settings files. |
| Form field | Label above, field, hint and error beneath. Two short fields may share a row; on a phone each has its own. |
| Date field | A start date from a large calendar, in the visitor's own date style, past days left out. |
| Button | One primary button, named for what it does: "Send enquiry". |
| Forms and validation | How mistakes and results are said. |
Do and don't
Do
- Let every optional question be skipped without a made-up answer
- Put the steps and the promise where they can be seen while filling in the form
- Count sends, with no personal details, so you know the form works
Don't
- Ask for a phone number as the price of a reply
- Add a puzzle to prove someone is human
- Call it a booking, or take any payment, if it is an enquiry
Accessibility
- Every field has a visible label above it; optional ones say so in words, and hints are tied to their field so a screen reader reads them with it.
- Name, email and phone are marked for the browser to fill in (
autocomplete). - The thank-you is announced politely (
role="status") and a failure at once (role="alert"). A field the service rejects is marked invalid, with its message under it. - It is an ordinary form, so it sends without JavaScript.
- No time limit, no captcha, nothing that needs a mouse.
Evidence
Where it's used
| Where | For |
|---|---|
| Headland Yachting, /enquire/ | The charter enquiry: fifteen questions, three of them required. Reached from every yacht page, destination and article. On its staging site until launch. |
| mediadreams.co.uk, /contact/ | The studio’s own enquiry form. Live. |
What we saw, and what changed
| When | What we saw | What changed |
|---|---|---|
| On Headland’s contact page the general question came first and the charter enquiry second. Planning a charter is what most people come for. | The enquiry’s tab comes first (contact.alternate.first, Somnia 1.28.0), and /enquire/ opens straight on it. | |
| In Somnia CMS the enquiry’s words were part of the contact page’s settings. | The enquiry page has a page of its own there. Its fields stay in code (1.53.0). |
From building and using it on real sites, each entry taken from the changelog or the build's own notes. This is observation by the studio and its clients, not research sessions with users.
What it rests on
- WCAG 2.2: Labels or Instructions: Every field has a visible label, and says when it is optional or what it is for.
What we don't know yet
- There is no summary of errors at the top of the form. A field the service rejects gets its message under it; a missing required field is caught by the browser’s own message, in the browser’s words.
- The Send button is disabled while sending. The Button page’s own guidance is to mark it busy and keep it focusable.
- How many people who start the enquiry finish it is not known: Headland is not live yet. The form counts a send, not a start.
- Not checked with a screen reader, or by anyone filling it in while we watch.