How to Follow Up Website Enquiries Without Losing Track

A new website enquiry is the beginning of a conversation. Someone may be ready to buy, comparing options or checking whether you cover their area. Treating every message as a likely sale makes it difficult to judge either your marketing or your follow-up.

Start with a shared list your team will actually maintain. You can use a spreadsheet or a customer management tool. The useful part is knowing who owns each conversation and what happens next.

Put incoming enquiries in one place

Record the customer's name, contact details, request, arrival date and where they found you, when known. Include enquiries from website forms, phone calls and messaging channels so the picture is not limited to one inbox.

Check for repeat messages from the same person. Keep their conversation together instead of counting each attempt as a new opportunity. Mark spam and unrelated requests separately; they still tell you something about the quality of incoming traffic.

Test your form regularly. Send an enquiry, check the shared list and confirm that the right person receives it. If messages are unreliable, review the checks in our landing-page guide.

Assign an owner and a realistic response window

Give every enquiry one responsible person, even when several people can access the inbox. Name a backup for leave and busy periods. “Someone will reply” is difficult to manage because nobody can see when it has failed.

An automatic acknowledgement can confirm receipt and explain working hours. It should not suggest that a person has reviewed the request if that has not happened. Choose a response window your team can meet, and use a reminder to flag conversations approaching it.

When you reply, refer to the customer's actual request. Answer what you can, then ask only for the missing details needed to suggest a next step.

Define what makes an enquiry suitable

Write a short qualification checklist in ordinary language. Can you provide the requested service? Is the location suitable? Is the timing workable? Are the customer's expectations compatible with what you offer?

Budget can matter, but it may need a conversation about the work before either side can judge it. An incomplete form is not automatically a poor enquiry.

Use a few clear stages:

• New: received and waiting for someone to respond.
• Contact attempted: you have replied and are waiting for an answer.
• Qualified: you understand the request and can reasonably help.
• Proposal sent: the customer has a specific offer to consider.
• Won or lost: the outcome is known, with a short reason where possible.

Define “won” for your business, such as an accepted agreement or a confirmed booking. Apply that definition consistently.

Give each conversation a next action

After a call, note the agreed action and date: send a quotation, arrange a visit or check in after the customer speaks with a colleague. Avoid leaving everything under an unhelpful “pending” label.

If a customer has not replied, send a useful reminder that refers to their request. After a reasonable final follow-up, mark the conversation inactive instead of repeatedly chasing them. Respect requests to stop contact and make reopening the conversation straightforward.

Review progress beyond the enquiry total

Look at how many unique enquiries become qualified opportunities, how many receive proposals and how many become customers. Compare groups received during the same period and allow time for longer decisions. Recent enquiries may still be in progress.

Read the reasons behind lost or stalled conversations. Repeated questions about availability may point to missing website information. Delays in sending proposals may point to an internal capacity problem. No workflow guarantees sales, but a consistent record makes those differences visible.

If keeping the list current involves repeated copying between tools, explore custom business systems. Bring a few anonymised examples of the current process when you talk to Kinstel, so the discussion starts with the work your team needs to do.