Contact Form Template
Best use: Use this contact form when one public entry point must send a useful message to the right reply owner without collecting account secrets or unnecessary personal details.
Collect a useful message and a reliable way to reply without asking for unnecessary data.
A contact form that sorts before it sends
The topic choice creates the route. The message supplies only the context needed for a useful first reply.
Reply details
Route and message
Where a shared contact route works
Use this for a general first contact when the visitor may not know which team owns the question.
Adapt the routes before publishing
- Replace broad topic choices with your actual routes.
- State a realistic reply expectation.
- Set a maximum message length and test long valid text.
What decision the topic choice enables
This template helps a general website enquiry reach the right owner with enough context for a useful reply. The topic choice supports routing, while the message gives the receiving team the detail needed to respond without forcing the visitor through a specialist form.
If enquiries often reach the wrong person, use the form response workflow guide to define ownership and escalation before publishing.
Questions that create the reply record
The topic choice creates the route. The message supplies only the context needed for a useful first reply.
- Your nameLets the responder address the visitor naturally without collecting unrelated identity details.
- Email addressProvides one reliable reply channel and should be checked for basic format errors.
- What can we help with?Routes the enquiry to the correct owner before someone reads the full message.
- Your messageCaptures the question and relevant context in the visitor's own words.
From submission to a closed enquiry
The owner sees the topic, reply address, and message together instead of receiving an unclassified email.
Route the enquiry
Route the selected topic to a named inbox owner.
Prepare the reply
Acknowledge receipt without copying the full message into email.
Close the request
Close only after replying or recording why no reply is needed.
A realistic routed enquiry
Routing a general website enquiry. A small service business can route product questions, sales enquiries, and support requests from one entry point. The owner reviews the selected topic, sends the message to the responsible queue, and replies through the supplied email address.
Contact-form decisions
Answers about the choices, limits, and handoff shown on this page.
What fields should a contact form include?
Most general contact forms need a name, reply address, routing topic, and message. Add another field only when it changes who handles the enquiry or what happens next.
Should a contact form ask for a phone number?
Ask only when a phone call is part of the stated response process. Otherwise, an optional or omitted phone field reduces unnecessary collection.
Create a contact route with a named owner
Replace the example topics with real destinations, test each route, and publish the reply expectation beside the form.
