Build contact forms that help people finish

A contact form is a conversation with someone who is deciding whether your organization can help. Asking for unnecessary details or hiding useful feedback can end that conversation early. A good form collects enough context for a meaningful response and explains what will happen after submission.

Ask only what the next step needs

Start with a name, reply address, and a clear description of the inquiry. Add a service selector only if it helps route or interpret the message, and offer an option for visitors who are unsure. Mark optional fields in their labels. Explain how the information will be used rather than asking for broad consent unrelated to the inquiry.

Make errors understandable and recoverable

Use persistent labels, sensible input types, and accessible error messages. Keep entered values when validation fails. An error summary should help users find the affected field, while inline feedback explains how to fix it. Test the experience with a keyboard and with browser zoom, not only with a mouse at a desktop width.

Protect the workflow without creating unnecessary friction

Use appropriate spam controls and server-side validation. Keep notifications directed to a trusted internal recipient, and avoid reflecting arbitrary message content to unverified email addresses. After a successful submission, show a specific confirmation and explain the next step. Do not claim that email was delivered unless that status is actually known.

A practical next step

Ask a colleague to submit the form using only a keyboard, first with missing information and then successfully. Observe whether they can identify errors, recover their work, and understand what happens next.