After a website enquiry, the form should pass a short set of facts (who they are, what they asked for, which page they were on) into the system your team already uses, and one named person should own the reply. If the thank-you page is the end of the path, your site is still a brochure.
When owners ask me what should happen after a website enquiry, they usually expect an answer about design or copy. It's almost always about plumbing: where the enquiry goes, who picks it up and whether anyone has to retype it. Here's how I'd decide the hand-off before you touch the pages.
The enquiry dies in a mailbox
Many sites look finished. The form still sends the enquiry to a shared inbox, and nobody is sure who should answer. Someone copies the name, the company and the request into the CRM, then again into a spreadsheet, because the site never handed those facts on.
Visitors leave. Marketing thinks the lead is with ops. Ops thinks it's still in the inbox. Another form tool won't fix a handoff the site already fumbles.
And the clock is running. When Harvard Business Review audited how over 2,000 US companies handled web leads, 23% never replied at all and the average reply took 42 hours. It's older US data, but the pattern is familiar: the enquiry wasn't lost because nobody cared, but because nobody owned it.
Write down what leaves the form
Before you change the design, write the fields the next system needs. Name, work email, company, what they asked for and which page they came from are usually enough. Questions nobody reads only slow the form.
- The page they were on when they enquired
- What they asked for, in their words
- Who owns the reply
- Where the record lives after the form submits
That restraint is also the law. Data minimisation is one of the UK GDPR principles: the personal data you collect should be adequate, relevant and limited to what you need. And at the point you collect it, people should be told who you are, why you want it and how long you'll keep it, usually through a short line by the form linking to your privacy notice.
Say you run a 20-person accountancy practice. Your contact form asks for turnover, VAT status, year end, number of employees and how they heard about you. Most people abandon it halfway, and the ones who finish get a call that asks the same questions anyway. Cut it to name, email, phone, what they need help with and the page they came from. Ask the rest on the call, where it's a conversation rather than a form.
One owner for the next step
Marketing and ops often argue over whose inbox owns the lead. Pick one place where the enquiry shows up, and name the person responsible for the next step. If two teams can both claim it, both will wait.
Owning it doesn't mean doing every step by hand. The confirmation email and the first booking link can send themselves; the owner's job is the same-day personal reply and anything that needs judgement. I've set out a sequence for that in how to follow up with leads who don't book.
Content and hosting stay in accounts the business controls. You open hosting and invite the people who build. Shape the pages around how you win work, and treat the site as a front door that passes the work on. If an agency or freelancer holds the only login to your domain or your form tool, you don't own your enquiry path.
Hand the same facts to the rest of the business
A written scope should say which systems receive the enquiry and what follow-up starts from the same record. If the thank-you page is the end of the path, the site is still a brochure.
In practice that means one record, created once, that the rest of the business reads from:
- Follow-up starts from it, using what they asked for.
- The CRM holds it, so nobody retypes the details.
- Reporting counts it, by page and by service, so you can see what's bringing in work.
- Chat and calls write to the same place, so a visitor who chats and then rings is one customer, not two. See what website chat should handle before a person steps in.
This guide is about your main site's everyday enquiry path. Campaign pages raise a related problem, keeping the source attached and not spawning a separate list, which I've covered in how to launch a landing page without a second inbox. If you're counting what it costs when these tools don't talk, read the real cost of disconnected tools, or browse our other guides.
See Websites for a site built around that handoff: enquiry paths into the systems you already pay for, and follow-up that starts from the same facts.
Questions people ask
What should happen after a website enquiry?
The enquiry should land as one record in the system your team already uses, the person gets an immediate confirmation with a clear next step, and a named owner replies personally, ideally the same working day.
What fields should a website contact form have?
Usually name, email, phone or company, what they need, and the page they came from (captured automatically). Ask anything else on the first call.
Who should own website enquiries?
One named person or role, not a team inbox. If marketing and ops can both claim it, decide now and write it down.
Do I need a privacy notice on my contact form?
You need to tell people who you are, why you're collecting their details and how long you'll keep them, at the point you collect them. A short line by the form linking to your privacy notice is the usual way.
Sources
- The Short Life of Online Sales Leads (Harvard Business Review)
- Principle (c): Data minimisation (Information Commissioner's Office)
- Right to be informed (Information Commissioner's Office)