How should website forms route leads so none get lost?

Every website form should send each submission to an inbox or system that more than one person monitors, keep a stored copy outside email, filter spam without hiding real inquiries, and be tested end to end after launch and after every change. Name one person who owns the routing and one backup. The handoff after the form needs as much attention as the form itself.

A form that works in a demo can still fail in practice. Notifications go to a former employee's mailbox. A spam filter catches a real quote request. A plugin update quietly stops email delivery. Nobody notices for weeks, because a form that sends nothing looks exactly like a slow month.

This page is for owners and marketing leads setting up or reviewing forms on a new site. The platform details below come from Netlify, Squarespace and WordPress documentation; the routing principles apply to any of them.

Map where every form sends

Before configuring anything, write down each form and where its submissions should go. A short map prevents most lost leads.

Settle the map with the people who answer the inquiries. The person configuring the form should not have to invent who handles a commercial request versus a warranty call. That routing is business knowledge, and it belongs in the brief before the build begins. If different requests need different people, consider separate forms or a required "what do you need" field that sets the route.

What each platform provides

On Netlify sites, Netlify's documentation says form notifications can go to email, webhooks or a Slack workspace, and can be set for verified submissions to a specific form or to any form on the site. By default the notification emails come from formresponses@netlify.com, and replies go to that address. Netlify recommends including a field named email so the notification's reply-to is set to the person who submitted it, which lets staff reply directly.

On Squarespace sites, each form needs at least one storage option. The choices include Squarespace's Contacts panel, email, a Google Drive spreadsheet, Mailchimp and Zapier. The email option sends a message for each submission, and each form can connect only one email address, so that address should be a shared inbox. Squarespace also notes that form submission emails are disabled on trial sites, which is worth knowing before anyone tests a form on a site that has not launched.

On WordPress sites, the form comes from whichever form tool the site uses, and its notification settings live there. Underneath, WordPress sends mail through its wp_mail function, and WordPress's developer reference notes that a true return value does not automatically mean the email was received, only that the request was processed without errors. That is a good reason to keep stored copies and to test delivery rather than trusting a success message.

Filter spam without losing real leads

Netlify filters all form submissions through Akismet; submissions that pass appear in the form's verified list, and flagged ones can be found in a separate spam list. Netlify also supports a hidden honeypot field and a reCAPTCHA challenge, and submissions rejected by those two never appear in the spam list at all. Squarespace calls Google reCAPTCHA the best way to prevent form spam, and when email is the storage option, it says flagged submissions still arrive in the inbox with a warning at the top.

The practical lesson is the same on every platform. A spam filter is not a lead filter, and it will sometimes be wrong in both directions. Assign someone to look through the spam list or flagged emails on a regular schedule, and keep the honeypot and challenge settings simple enough that real visitors are not turned away.

A fictional example: the mailbox that stopped

Consider a fictional HVAC company in Tennessee. Its contact form sent notifications to the personal work address of a dispatcher who left the company in spring. The address was closed, and emails bounced without anyone seeing them. Phone calls kept coming in, so the drop in web inquiries looked like seasonal slowness until a customer mentioned on the phone that she had filled out the form twice.

The fix took an afternoon. Notifications now go to a shared dispatch inbox. Each submission is also kept in the platform's submissions list. The office manager submits a test inquiry on the first business day of each month and confirms it arrives. The question that would have caught it earlier is worth asking any team: "When did someone here last submit our own contact form and watch what happened next?"

Routing does not end at the inbox. Agree on who replies to each kind of inquiry, how quickly the business aims to respond, and where the inquiry is recorded once someone picks it up, so two people do not answer the same request and nobody assumes someone else did.

Test after launch, and after every change

Test every form with a real submission before launch, after launch on the live domain, and again after any platform update, plugin update, email change or staff change that touches the inbox. Confirm the email arrives, the reply-to works, the stored copy exists and the visitor sees a clear confirmation message that says what happens next and when. If analytics records form submissions, check that the count matches what the inbox received; tracking setup is covered in what to measure after a new website launches. For what a form should and should not collect, read what a website needs when it collects contact information.

Hudson South builds websites around the same four steps as its content work: Authority Asset gathers approved business knowledge and evidence, Hudson Twenty-One records how the business communicates across 21 dimensions so the writing sounds like it, Market Intelligence researches the buyer questions and the market, and AEO Creation turns those inputs into answer-first content. Form submissions emailed to the business are part of every build as a practice, and the routing map above is the kind of business knowledge the first step is meant to gather. The website builds overview covers the rest.

Make sure the inquiries reach a person

On a free 30-minute call, Hudson South compares your site with the competitors your buyers also look at and talks through what your next build should get right.

Sources

1. Form notifications. Netlify Docs. Read 2026-10-17.
2. Spam filters. Netlify Docs. Read 2026-10-17.
3. Set up form and newsletter storage. Squarespace Help Center. Read 2026-10-17.
4. Preventing form and newsletter block spam. Squarespace Help Center. Read 2026-10-17.
5. wp_mail(). WordPress Developer Resources. Read 2026-10-17.