Describe who should contact you, what your team needs to know, and when CAPTCHA should appear. Makeform turns that brief into a focused contact form with clear inquiry fields, spam-resistant submission steps, routing details, and a confirmation message you can edit before publishing.
Route genuine inquiries to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete starting prompt, adapt it to your website, or send it into the Makeform builder. The field structure is an example you can refine.
Audience
Prospective customers visiting a service-business website
Format
Compact inquiry form with service routing
Prompt size
407 chars
Example form structure
Compact inquiry form with service routing
Name and work email
Which service are you interested in?
How should we contact you?
Tell us what you need
CAPTCHA verification before submit
Suggested routing tags
Sales inquiry
Support request
General message
Ask only for details someone needs to answer the inquiry. A shorter form reduces abandonment while CAPTCHA handles the automated traffic at submission.
Step 1
Ask
collect the minimum details needed to respond
Step 2
Verify
place CAPTCHA at the submission boundary
Step 3
Route
send each genuine inquiry to its owner
Step 4
Review
monitor spam patterns and refine the form
Why protect the form
Publishing an email address makes it easy to contact you, but it also exposes the address and gives every message the same unstructured format. A protected form creates a deliberate submission boundary and keeps the details your team needs in consistent fields.
Place CAPTCHA directly before submit so automated scripts encounter a verification step while real visitors can complete the inquiry in the same flow. Keep failure and retry messages clear instead of silently discarding a message.
Use a topic dropdown and conditional questions to distinguish sales, support, partnership, press, and general messages. The visitor sees relevant questions, and the receiving team gets enough context to act.
Build notifications from structured fields rather than forwarding an anonymous block of text. Include the sender, topic, and concise summary, but keep sensitive or unnecessary data out of email alerts.
Built for real websites
A general contact page, sales page, support center, and community website should not ask identical questions. Begin with the closest workflow, then change field labels, required settings, and destinations.
A short name, reply address, topic, and message flow for visitors who may not know which department they need.
Project type, business context, timing, and budget ranges that help a sales owner prioritize and prepare a useful reply.
Account-safe identifiers, problem details, device context, and optional uploads routed by issue type without asking for credentials.
Plain-language topics, optional reply preferences, accessible verification, and distinct consent for unrelated newsletter messages.
Protected contact workflow
Generation gives you a structured starting point. Review the questions, verification experience, routing, and confirmation as one connected workflow before you embed it on a public page.
Tell Makeform why people contact you, which details each owner needs, and where different topics should go. Mention optional fields and information you never want visitors to submit.
Check labels, required fields, branching, verification placement, failure copy, and retry behavior. Preserve entered answers after a failed challenge so a real visitor does not have to rewrite the message.
Place the form on your contact page and test it at mobile and desktop widths. Submit valid, incomplete, and failed-verification cases; confirm keyboard focus and error messages lead to the right field.
Confirm every topic reaches its intended destination, then review repeated spam patterns. Adjust topic options, field validation, or verification settings without adding questions that burden every genuine visitor.
Choosing a contact method
The best approach balances accessibility, message quality, and resistance to automated submissions. CAPTCHA can reduce routine bot traffic, but clear fields, validation, monitoring, and an alternative way to reach you still matter.
Field guide
Good spam protection is not only a challenge widget. These six parts keep the form concise for genuine visitors, useful for the receiving team, and understandable when validation or verification fails.
Contact identity
Start with a name and one reply channel. Validate the email format, label phone as optional unless a call is necessary, and explain how the information will be used. Avoid collecting postal addresses, birth dates, or other details just because the field exists.
Topic & branching
A topic selection makes the form easier to route and can reveal only the follow-up fields that apply. Keep the list recognizable to visitors and include a general option instead of forcing every message into an internal department name.
Message quality
A blank box labeled Message produces vague requests. Ask for the goal, relevant context, what has already been tried, or the desired next step. Set a reasonable maximum length and provide upload fields only when the team is prepared to review files.
CAPTCHA & validation
Run CAPTCHA before the form accepts the submission, and keep field validation separate enough that visitors understand what failed. The error should identify the verification problem, offer a retry, preserve answers, and avoid implying a message arrived when it did not.
Routing & notification
Map each topic to an inbox, channel, or workflow and establish a fallback destination. Use subject lines that include the topic rather than untrusted message text. Test both the notification and stored submission so a routing mistake does not hide a genuine request.
Confirmation & access
A successful confirmation should say the message was received, identify the selected topic, and provide the next step without making a guarantee. Keep an alternative contact method available for visitors who cannot complete CAPTCHA, and distinguish success from a failed verification attempt.
Related tools
Start with general contact, then use a more focused form when sales, support, client, product, or website inquiries need their own questions and owners.
Create a general-purpose contact flow with clear sender details, topic selection, and message fields.
Open toolBuild a straightforward website inquiry form and embed it where visitors already look for help.
Open toolQualify prospective customers with source, need, timing, and contact fields for sales follow-up.
Open toolTurn technical and account questions into structured requests that can be assigned by topic.
Open toolGive existing clients a dedicated path for project questions, updates, and document requests.
Open toolCollect product, use-case, quantity, and purchasing questions before they reach the product team.
Open toolFAQ
Practical answers for website owners balancing spam resistance, useful inquiries, and a clear visitor experience.
It is a website form that collects a visitor's inquiry and adds a verification step before accepting the submission. Typical fields include name, reply address, topic, and message. CAPTCHA is intended to make automated submission more difficult; routing, validation, monitoring, and clear error handling remain important parts of the workflow.
No single control should be described as stopping every spam attempt. CAPTCHA adds friction for automated scripts, but unwanted messages can still come from more capable automation or real people. Review recurring patterns and combine verification with field validation, sensible rate controls, topic routing, and inbox filtering appropriate to your site.
Place verification at the submission boundary, close to the final button, so the visitor understands it is required before the message is accepted. If verification fails, preserve the completed answers, move focus to a clear error, and offer a retry. Do not show a success confirmation until the submission has actually been recorded.
Use clear instructions, keyboard-operable controls, visible focus, understandable error messages, and a verification option that does not depend on one sensory mode. Test zoom, mobile layouts, and screen-reader announcements. Where appropriate, publish an alternative contact route for someone who cannot complete the verification step.
For a general form, start with name, email, topic, and a message prompt. Add phone, company, order reference, timing, budget range, or uploads only when they help the assigned team respond. Use conditional logic so support-only or sales-only questions appear after the visitor chooses that topic. Never request passwords or secret access codes.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect submissions without a response cap. The paid tier removes the Makeform badge. Review the generated structure and test your CAPTCHA and routing behavior before embedding the form on a public page.
Yes. Publish the form and embed it on the relevant contact page, then use the topic selection to direct sales, support, partnership, or general inquiries to the intended destination. Test every branch, including the fallback route, and confirm notifications contain the details an owner needs without exposing unnecessary information.
Keep the visitor on the form, preserve their answers, state that verification was not completed, and provide a direct retry action. The message should not blame the visitor or suggest the inquiry was received. Log enough operational information to investigate repeated failures, while avoiding needless collection of personal details.
Give genuine visitors a clear route to your team.
