Your website gets enquiries. What happens next?

A customer fills in the form. An email lands in a shared inbox. Someone reads it on their phone between jobs and plans to reply later.

The website did its part. What follows is where a useful enquiry can become another thing to remember. Before adding more traffic, it is worth following one enquiry all the way through to a booked job.

Ask for enough to take the next step

The form should collect the information you need to decide what to do next. For a trade, that might be the type of work, postcode, a short description and an optional photo. For a consultancy, it may be the problem, the current tools and a contact method.

Avoid turning the form into the entire briefing process. If a question does not help you route the enquiry or prepare a reply, consider leaving it for the conversation.

Make optional fields visibly optional. Test the form on a phone, including uploading a photograph and correcting a mistake. A form that works only when every entry is perfect is going to create support work.

Give the enquiry an owner

A shared inbox is a place to store messages. It does not, by itself, make responsibility clear.

A small team might start with a simple rule: one named person checks new enquiries at agreed times and records the next action. A larger team may route work by service or location. Either way, someone should be able to tell whether the customer has had a reply.

An acknowledgement can confirm that the form arrived, but it should not promise a response time your team cannot meet. Explain what happens next in ordinary language.

Carry the details into the quote

The customer’s name, address and job description should not have to be retyped every time the work changes stage. A connection to your CRM can create or update a record and attach the enquiry to it.

Before automating that, agree how existing customers are recognised. An email match may help, but shared addresses and spelling mistakes need a review route. Merging the wrong customers creates more work than entering a record manually.

Useful stages might be new enquiry, waiting for information, visit booked, quote sent and accepted. The exact labels matter less than making the next action obvious. Our guide to quoting software covers the point where a job brief becomes a priced document.

Design for the failed handoff

What happens if the CRM is unavailable when the form is submitted? Keep the enquiry somewhere recoverable, flag the failed transfer and provide a way to retry without creating duplicates.

Test the full journey with a clearly labelled test enquiry. Confirm that it reaches the right person, appears in the right record and produces the expected customer message. Check the failure route as well as the successful one. Delete the test record when you are finished.

AI is optional here. Fixed rules are often enough to move a completed form between systems. AI becomes more relevant when you need help interpreting a long, free-text description, with a person checking uncertain cases.

Start with the point where work gets lost

You do not have to buy a new CRM to improve this process. If a reliable owner and a shared list solve it, use them. If the team is repeatedly copying details or losing track of quotes, connecting the tools may be worth the effort.

Kerbside builds websites with customer and job systems, and integrations for existing tools. The first question is what currently happens after someone presses Send. That answer usually tells us where to start.