Website Contact Form Template
A contact form built for embedding on your site that captures which page the visitor came from, so replies arrive with context attached.
Questions, corrections, ideas: tell us what's on your mind and where you found it, and we'll get back to you quickly.
Helps us see exactly what you saw, especially for corrections and bugs.
A website contact form has one advantage over a generic inbox that most sites squander: the sender is standing somewhere specific on your site at the moment they write. This template is built around capturing that location. The page-link question turns "your pricing seems wrong" (un-actionable) into "the annual price on /pricing contradicts the checkout page," which someone can fix in five minutes.
The page-link question does the work. The URL field is the signature move. It is a proper link input rather than free text, so you get a clickable path to exactly what the visitor saw. It is indispensable for typo reports, broken pages, and "where do I find X" questions, and its description explains the why, which roughly doubles how often people bother to paste. The reason selector has four honest lanes, including "just saying hello," because a form that admits friendliness gets friendlier messages, and the correction lane deputizes every reader as a proofreader. Name and email stay minimal, and the message prompt ("what were you looking for, and what happened instead?") doubles as a bug-report template that works for non-bugs too.
Kept off the form. Phone and company fields, because a visitor with a site question rarely wants a sales call. CAPTCHA walls, because layered invisible protection handles the bots that hammer every embedded form. A newsletter checkbox, because asking to market to someone mid-question sours the exchange.
Who needs the which-page answer. Content sites and documentation hubs where "this page is wrong" is the most valuable message a reader can send, small-business sites replacing an info@ address, and anyone whose site has enough pages that "which page?" is the first reply they'd otherwise have to write.
Embed it, then reap the context. Embed it inline on a /contact page, where the form inherits your accent color and reads as part of the site, or use the popup embed so "Contact" in your nav opens it anywhere. Rename the reason lanes to your reality: docs sites add "suggest a topic", shops add "order question". If corrections deserve special handling, add a logic rule that reveals a "what should it say instead?" field when that lane is chosen. Keep notifications on, and if you pipe responses anywhere, the webhook payload carries the page URL so your issue tracker gets the link too. Every reply then starts a step ahead, because you know the page, the intent, and the words. Multiply that saved first-reply across a year of messages, and this one extra field is the highest-leverage question on your site.
Frequently asked questions
Why ask for the page link at all?
It removes the most common first reply, "which page were you on?". A pasted link turns vague reports into fixable ones and saves a full email round-trip.
Does the embedded form clash with my site design?
Use the inline embed and set your theme (accent color, background, font, and corner radius) so it reads as a native section. The iframe variant is the fallback for tricky CMSes.
Can bug reports go somewhere different from hellos?
Route with a webhook and branch on the "what can we help with" answer in your receiving tool: corrections to the issue tracker, business enquiries to the founder's inbox.
Will I drown in spam once this is on every page?
Embedded public forms do attract bots, which is why honeypot, timing analysis, and an escalating invisible challenge run on every submission without adding visitor friction.