Introduction
A customer tells you they filled in the form and never heard back. So you test it. The form submits, the thank you page appears, the email arrives. The form works.
The enquiry still went nowhere. Both things are true, because a working form answers one question and the enquiry had a much longer trip ahead of it.
What the form test actually proves
Your test covered the first step. It proved that a submission leaves the browser and that at least one message arrives somewhere.
It said nothing about whether a record was created, whether a person became responsible for it, whether that person saw it in time, or whether the customer ever heard from a human. Those are separate questions, and in most businesses nothing is watching any of them. The only alarm in the system is a customer ringing back annoyed, which is a late and expensive way to find out.
Trace one enquiry end to end
Every enquiry passes through a series of hops. Each one can stop it quietly, which is the part that matters, because a loud failure gets fixed the same day.
- Submission. The browser sends the enquiry. It can fail on a page that has been sitting open since yesterday, or when a required field rejects a valid Australian phone number.
- Bot check. Something filters spam, and it does not tell you what it stopped. A genuine customer refused here leaves no trace anywhere in the business.
- Notification. An email goes out. It can land in spam, be filed by a rule, arrive at an address nobody watches, or go to a person who left last year.
- Record write. The enquiry should become a record. The connection can fail, create a duplicate of an existing customer, or land without a source so nobody can tell where it came from.
- Assignment. Someone has to own it. Without a name attached, it sits in a queue that belongs to everybody, which means it belongs to nobody.
- Acknowledgement. The customer hears something. If an automatic reply went out, the team may treat the enquiry as handled, and the customer is still waiting on a person.
- Next action. The record needs a next step and a date. A status with neither is a record that ages quietly until someone asks about it.
That is the trace. The failures are not dramatic. Nothing errors, nothing turns red, and the business finds out much later that enquiries have been queueing behind one broken hop.
What the customer sees while that happens
Nothing. They see silence, and they read it as an answer about how you would handle their job.
Then they contact someone else, and you never learn that the enquiry existed. This is why enquiry loss is so hard to notice from inside the business. The evidence of the problem leaves with the customer.
Run the trace yourself this week
Do this once and you will know more about your enquiry path than any report will tell you.
- Submit a real enquiry from your phone, off the office network, using a name and number nobody in the business will recognise.
- Note when the notification arrives, when a record appears and when a person actually replies. Those are separate times, and the gaps between them are the interesting part.
- Open the record. Does it have a source, an owner, a next action and a date? Missing any one of those is a hop to fix.
- Ask whoever should have handled it what they saw, in their own words. That conversation usually finds the real gap.
- Repeat from a number you already have on file, to see whether it attaches to the existing customer or quietly creates a second one.
- Then test the other front doors. The phone call, the missed call, the message on your Google Business Profile, the direct message on social. Most businesses have several and only ever test the form.
Write down where it stopped. That is your first build, and it is almost never the form.
What to fix first
Fix the ownership before the technology. Every enquiry gets a named owner, a next action and a date, even while the rest is still manual.
Then make the failures visible, so a missing record raises something instead of waiting for a complaint. After that, automate the parts that were always going to be late when the day gets busy. The useful reply, the qualifying questions, the chase that runs until the customer decides.
Once every enquiry lands on one record with a status, an owner and a next step, the state of your front door is something you look at rather than something you hope about. That is the point of putting the whole journey on one screen.
Bring one enquiry you know went cold to an Operations Review and we will trace it with you, hop by hop, and show you where it stopped.
FAQs
Should we just add another notification email?
It helps a little and it hides the real issue. A second inbox still relies on somebody noticing, and it creates the awkward case where two people assume the other one replied. A named owner on a record is the fix. The notification is a convenience on top of it.
How would we know if a form submission was silently blocked?
You would not, unless the blocking is logged and someone reviews it. That is why we keep a record of what a bot check refused rather than discarding it, and why the enquiry count is worth watching for quiet drops. A sudden change with no matching change in traffic is usually a broken hop, not a slow week.
Does this mean we need a new website?
Not usually. The website is one hop out of many, and the ones after it fail more often. Rebuilding the site while the handoff behind it stays broken gives you a better looking version of the same problem.
SOURCES
CONTENTS