The form says sent. Who has the job?
A facilities manager sends a maintenance enquiry. The website thanks them. The message lands in the same inbox as domestic callouts, invoices and supplier promotions. On screen, everything worked. In the office, somebody still has to notice the request and decide who owns it.
That is a useful place to look. It is more useful than announcing that your website has lost a hundred customers we have never counted.
The shared inbox was a reasonable solution.
When the crew was smaller, everyone knew the jobs and a shared mailbox kept things simple. You did not need a committee or a new application to answer a customer. You needed the phone picked up and the work booked.
As the work changes, that same inbox can ask one person to act as dispatcher, estimator and commercial gatekeeper. The tool still works. The responsibility has become harder to see.
We start with the way your crew actually works.
We ask what makes a commercial enquiry worth acting on, who can assess it, who covers that person and what they need to respond. You know which requests need a site visit and which can be qualified from a short description. We turn those distinctions into a working path.
With permission, we trace a labelled test enquiry from the website to its destination, assigned person and recorded next action. We check the existing tools before proposing another subscription.
Measure the handling. Leave the fantasy revenue out.
Here is an illustrative calculation: eight enquiries needing ten minutes each to identify, forward and explain create 80 minutes of handling. If three then need another ten-minute chase, the total is 110 minutes. That does not prove lost customers or lost revenue. It identifies work worth measuring.
The useful baseline is how many relevant enquiries arrive, how long assignment takes and whether a response is recorded. We use your actual records to find out whether a change helped.
Busy days expose the weak handoff.
Emergency callouts happen. People take leave. Attachments fail. Buyers send half a brief and expect an answer. A workable enquiry path needs to cope with that ordinary mess.
We define the fallback: where an unassigned request is visible, who covers an absent owner and what the team does when a notification fails. A receipt to the customer and an accepted task inside the business are two different checks.
One repair. A visible test. A proper handover.
We move fast by agreeing a small repair with a clear finish. Depending on what we find, that could mean a commercial service page, a better enquiry form, a routing rule, an acknowledgement or a simple record of the next action. The job gets an owner, an access list and a check everyone understands.
We build the agreed change, run a labelled test through the whole path and show you the result. Then we hand over the destination, responsibilities and recovery steps. If a dependency blocks release, we name it early and agree the next action. We do not hide it behind a progress percentage.
A Systems Diagnostic is generally around five working days after scope and access are agreed. Implementation timing follows the actual repair and your approvals. You get a specific scope and fee before the work starts.
Yeah, we do all that basic digital stuff. Websites. Forms. Search. Integrations. But we are not going to tell you your “website’s costing you x100 customers”. That is not us. If we have not measured it, we are not putting it in a scare pitch.
We are just here to help. So mate, tell us what’s up. Is the wrong work coming in, is a good enquiry getting stuck, or has a small fix been waiting forever? Send the page URL and a couple of sentences. We can start there.