Site Launch Workshop / GUIDE
Design a contact page people can use
Explain what to send, who receives it and what happens next.
Reduce uncertainty
Tell visitors the purpose of the contact route before they start. A correction request and a quote inquiry need different information. Ask for the minimum needed to respond, and explain any fields whose purpose is unclear. Do not collect sensitive documents through a generic contact form.
Keep labels visible
Use an associated label for every control. State requirements in text and give examples where a format matters. When an error occurs, explain which field needs attention and retain the other entered values. W3C guidance explains why labels help screen-reader, speech-input and pointer users.
Provide an alternative
Show an email address alongside a mail link. A mail link can fail when the device has no default email application. For a published phone number, state relevant hours and time zone only when those details are known. Avoid promising an immediate response unless someone can reliably provide it.
Explain the next step
A useful confirmation states that the message was submitted and describes the actual process. It should not promise a booking or purchase that has not occurred. Test both the visible confirmation and inbox delivery. A successful browser screen with a lost email is still a failed contact workflow.
Review what is recorded
Keep personal message contents out of analytics URLs and event parameters. Treat spam filtering, retention and access as operational choices that need an owner. On this publication, corrections use a direct email link; calculator inputs are processed locally and are not submitted as contact requests.
Primary references
Checked November 12, 2026. Consult the current original guidance for context.
Prepared with AI assistance. Examples are constructed for explanation, not reported client results. Corrections are welcome.