Fewer website enquiries, better ones: reading a quieter contact form

A contact form collects very different messages under one number. Some come from people who are ready to buy and fit what you sell. Many come from people who only want one fact: what it costs, whether you deliver to their country, what the minimum order is, whether the product fits their machine.

When the website does not answer those questions, people have to ask. Every question counts as an “enquiry”, and the monthly total looks healthy. When the website does answer them, two groups stop writing:

• People who got their answer and do not need anything else yet.
• People who learned that you are not the right supplier: too expensive, too large, the wrong region, the wrong product.

Neither group was going to buy this month. What remains are the people who read the price and the conditions and still want to talk. That is why a falling submission count on its own tells you nothing. It is a count of messages, not of opportunities.

The opposite case exists too. If a redesign hides the form, breaks it on phones or makes the page slower, enquiries also fall, and good ones are lost with the rest. The numbers below tell the two cases apart.

Three questions replace the single number:

1. How many enquiries were qualified, meaning from a customer you can serve, about something you sell, with a real need?
2. How much time did the team spend answering all of them?
3. How many ended in a quotation and in a won deal?

If submissions fall while qualified enquiries and won deals hold or rise, the website improved. If qualified enquiries fall in step with the total, something is in the way of good customers, and the form, the page speed and the wording need a look. A review of the path to the form is ordinary UX work and usually finds the cause quickly.

To answer the first question, every enquiry needs a class. Keep the classes few, so that two colleagues would choose the same one.

The following figures are an illustrative example, not measured data. They describe an imagined supplier that added price ranges, minimum order quantities, delivery regions and a short list of answered questions to its product pages. One quarter before the change is compared with one quarter after it.

The total falls from 240 to 150, a drop of 37.5 per cent. Almost all of the fall is in basic questions (110 to 45) and unsuitable enquiries (50 to 27). Qualified enquiries rise slightly, from 60 to 66.

The hours come from an average handling time per class: 40 minutes for a qualified enquiry, 15 for a basic question, 10 for an unsuitable one and 2 for spam. Before the change that is 2,400 + 1,650 + 500 + 40 = 4,590 minutes, or 76.5 hours. After it, 2,640 + 675 + 270 + 24 = 3,609 minutes, or about 60 hours. The team spends more time on qualified customers (2,640 minutes against 2,400) and about 16 hours less in total.

A manager who saw only the first row would conclude that the website lost more than a third of its enquiries. The full table says something else: three more won deals, a larger share of each working hour spent on real customers, and less answering per deal.

None of this needs special software. It needs three habits, started before you change the website, so that there is a “before” to compare with.

Add one field to wherever enquiries land: the list of form entries, the shared mailbox or the customer database. Whoever answers the enquiry sets the class, at the moment of answering. For basic questions and unsuitable enquiries, also note the subject in two or three words (“price”, “delivery Spain”, “below minimum”). After a month that list tells you exactly which answers are missing from the website.

Exact time recording is not necessary. Estimate an average per class once, by timing ten enquiries of each kind, and multiply by the counts, as in the example. Review the averages once or twice a year. Remember the work that does not show in the inbox: phone calls that follow a form message, and internal questions to colleagues.

Each qualified enquiry gets a result within a set period: quotation sent or not, won, lost, or still open. The link between the form entry and the deal is the step most companies skip, and it is the one that makes the rest meaningful. If your sales team works in a separate system, a reference number or an automatic hand-over through workflow automation saves the copying. Website statistics alone cannot do this, because they stop at the moment the form is sent. A sound analytics setup covers the path to the form, and your own records cover what happens after it.

The classified list is also a work plan. Basic questions that still arrive point to answers the site does not give clearly enough. Unsuitable enquiries that keep coming from one region or for one product show a wrong expectation that a sentence on the page can correct. Qualified enquiries that never receive a quotation are a question for sales, not for the website.

Report the new numbers in place of the old one. A monthly line with qualified enquiries, quotations, won deals and hours spent answering gives a truer picture than “the form was used 150 times”, and it stops a good change from being reversed because one number went down.