Why most service-business websites lose enquiries after launch (and what to track from day one).

The launch is the beginning, not the result

A website does not win work. It gives people who are already looking a reason to contact you, and a way to do it. After launch, the number that matters is enquiries: how many, from which pages, of what quality, and what happened to them. Most service-business sites never measure that, so when enquiries are thin nobody knows whether the problem is traffic, trust, the phone number or the voicemail.

The five leak points

1. Unclear positioning

The visitor cannot tell within a few seconds what you do, where, for whom, and why you rather than the next result. Sites that lead with a slogan and a stock photo lose the buyer before the scroll. The fix is a first screen that states the service, the area, a proof point and the next step, which we cover in Service pages that win.

2. Contact paths hidden on mobile

On desktop the phone number sits in the header. On a phone it collapses into a menu, the form is three pages away, and WhatsApp, which many customers prefer, is not offered at all. Well over half of service-business traffic is mobile, so test every contact path with your thumb: can you call, message or enquire from any page without hunting?

3. Slow follow-up

The enquiry arrives, goes to an inbox that is checked in the evening, and by then the buyer has spoken to two other firms. Speed to first response is the single most controllable variable in converting an enquiry, and it has nothing to do with the website. Decide who responds, by when, and through which channel, before launch.

4. Unqualified enquiries

The form asks for a name and a message, so you get "how much for a job?" with no address, no scope and no timing. Every one of those takes a phone call to qualify, and most are not the work you want. A few well-chosen questions (project type, location, rough timing) on the form, or a short checker before it, raise the quality of what arrives without reducing the volume of serious enquiries.

5. No attribution

You know you had some enquiries last month. You do not know which pages produced them, whether they came from Google, a referral, a directory or a recommendation, or which ones turned into quotes and jobs. Without that, every decision about the site is a guess.

What to track from day one

None of this needs a marketing department. It needs a few events, a spreadsheet and fifteen minutes a week.

Contact clicks

Fire a contact_click event in GA4 whenever someone taps a phone link (tel:), an email link (mailto:) or a WhatsApp link, with a parameter for the method. A tap is not a conversation, but it is the closest you get to counting intent on a small site, and it tells you which method people prefer. Where the site has a cookie consent banner, these events run only after consent, so treat the numbers as a sample.

Form and booking events

Track form submissions and booking-link clicks as their own events. If you use an online calendar such as Cal.com or Calendly, track the click through to it.

Source page

Record the page the enquiry came from. For tracked events this is automatic; for a form, add a hidden field with the page URL; for phone calls, ask "which page were you on?" or use a distinct number on the site. Source page is the link between traffic and work. It turns "this page gets the most impressions" into "this page produces enquiries", which is a more useful statement.

Search Console

Verify the site in Google Search Console before launch and check the Performance report monthly: which queries and pages earn impressions, where the click-through rate is weak, and whether any important page is not indexed. It is free, and it is the only place Google tells you what it thinks your pages are for.

A simple enquiry log

A shared spreadsheet with one row per enquiry, filled in within a day of each one arriving. The columns that earn their place:

• Date and channel (phone, form, WhatsApp, email, referral, directory).
• Source page, where known.
• Project type in your own categories (for a structural engineer: crack inspection, beam calculation, extension, other).
• Contact preference, because it changes how you follow up.
• Outcome: quoted, won, lost, not a fit, no response. Update it as you go.

After a quarter, this log answers the questions that matter: which pages and channels bring the work you want, which bring noise, and where the follow-up is failing. It also gives you the real conversion rate, enquiry to quote to job.

Weekly reporting in fifteen minutes

Once a week, look at four things: contact clicks and form events by page; new rows in the enquiry log and their outcomes; any Search Console pages with impressions but poor clicks; and whether every enquiry got a response within your target time. Write three lines about what changed. Over a few months those lines tell you where the leak is, and fixing one leak usually does more than a redesign.

When qualification tools help

If the log shows plenty of enquiries but too many that are small, vague or outside your area, the leak is qualification. That is when a short checker or calculator earns its place: a tool that asks the buyer three or four questions, gives them a useful answer, and passes a pre-qualified enquiry through with the details already captured. Panoptic's "Do I need a structural engineer?" checker does this: it helps the homeowner decide, and it sends through an enquiry with the project type and contact preference attached, deep-linkable and with a WhatsApp message pre-filled. We build tools like this as part of custom tools and web apps, but only when the log says qualification is the problem.

When automation becomes worth it (and not before)

Automation (auto-replies, CRM hand-offs, follow-up sequences, missed-call text-backs) is worth it when manual handling is the bottleneck: when enquiries are arriving faster than they can be answered well, or when the same admin step is repeated many times a week. It is not worth it before that. Automating a process that produces five enquiries a month adds complexity without changing the outcome. Fix positioning, contact paths and qualification first, measure for a quarter, then automate the step that is genuinely slowing you down. That is the order we work in: website, search, tools, then automation.