Before paying for a new contact form, decide what a visitor must send and what your team must receive. A form is useful only when a real enquiry reaches the right person and the visitor knows what happened. Put those outcomes in the brief you give each website supplier.
Use this checklist for a quote form, appointment request, or general enquiry. Keep each form focused on one next step. Ask suppliers to price any routing, spam control, or connection to another system separately.
Choose one purpose and the minimum fields
Write the form's purpose in one sentence: "A buyer requests a website quote," for example. Ask only for details needed to respond. A name, reply address, service need, and short project description may be enough for an initial quote discussion. Add a phone number only if your team needs it at this step.
Mark each required field and explain why a format matters. W3C's form instructions advise clear required-field and format guidance. A placeholder disappears when someone types, so it should not carry the only instruction.
Make the form usable on a phone and with a keyboard
Give every field a visible label that names its purpose. W3C's labeling guide explains how labels help people identify controls and can make them easier to select. Ask the supplier to test the form with a keyboard, on a phone, and with long answers.
When an answer is missing or invalid, show a specific message beside the field. Preserve the other answers so the visitor can correct one mistake. W3C's validation guide covers required fields and helpful correction.
Define what happens after someone presses send
Name the mailbox or system that receives each enquiry. State who monitors it, who covers absences, and how staff will find the original message. If the form also sends an automatic receipt, include the exact text and reply address in the brief.
Show a clear success message only after the enquiry is stored or delivered. Show a clear failure message if it is not. W3C's notification guidance calls for feedback that tells people whether submission succeeded and how to fix errors. Do not promise a response time that your team cannot meet.
Set spam and privacy rules before launch
Ask how the supplier will limit automated submissions and where form data will be stored. List who may read it and how long your team needs it. Check that any privacy notice matches the actual form, mail service, and storage. A spam filter can also block a real buyer, so include one test of a valid submission.
Give each supplier the same acceptance check
- Send one valid test from a phone and one from a desktop.
- Confirm both appear in the agreed inbox or system with every needed field.
- Submit a blank required field and a bad reply address; check the correction messages.
- Use a keyboard to reach, complete, and submit every field.
- Force a delivery failure in a safe test setting and check the visitor's message.
- Confirm the named staff member can find and answer the enquiry.
Ask each supplier which checks are included before launch and who repairs failures. A screenshot of a finished form does not prove the handoff works. CIT offers custom website development. Send CIT your form brief through the quote form to discuss a project scope.

