The First 15 Minutes of a Lead: Where Website Enquiries Get Lost
A customer submits an enquiry through your website, sees a thank-you message, closes the tab, and gets on with his day. As far as he is concerned, someone at your business now has the question.
Inside the business, things might be less certain. Perhaps the form sends an email to an address nobody checks regularly. Perhaps the enquiry reaches the CRM but the service the customer selected disappears along the way. Or perhaps three people receive the notification, and each assumes someone else will reply.
The website has done enough to display "Thank you." The business still has to earn the customer's confidence.
One useful way to find these gaps is to follow a test enquiry through its first 15 minutes. That gives you a manageable window to inspect what happens after submission. Your response commitment can still reflect your opening hours, staffing, and the kind of service you provide.
Start with a form your customers actually use. Submit a realistic question about a specific service, using contact details your team controls and a name that clearly identifies it as a test. Tell the people handling enquiries what you are doing so they do not spend time pursuing a fictional customer.
Write down when you submitted it and which page you used. Then look for it.
Did the confirmation screen appear? Did an acknowledgement arrive? Was a CRM record created? Who received the notification, and where would they go to respond?
You might discover that colleagues have different answers to these questions. Someone remembers setting up an integration. Someone else believes every form goes to the shared inbox. Walking through the process together replaces those assumptions with something everyone can see.
Try your main enquiry routes, including a mobile submission and one outside business hours. Forms that look identical can have different destinations. As with verifying conversion tracking, completing the journey yourself is more revealing than checking whether the settings look correct.
Read the record as if you were answering it.
Once the enquiry reaches the CRM, compare the record with what you submitted.
The important question is whether a colleague could pick it up and help customers without asking them to repeat themselves.
Check the requested service, the complete message, contact details, and preferred contact methods. Can recipients tell on which page the customer was? Is the submission time clear?
Small mapping errors can create awkward workarounds. A service choice stored in a general notes field might be visible to a person but unavailable to an assignment rule. A phone number treated as a number rather than text might lose its leading zero. These are easy details to overlook during setup. They become harder to ignore when someone is trying to make a call.
Be honest about what you know.
Source information needs a closer look, too. The page where someone submits a form tells you where the conversation started on your website. It does not necessarily tell you how that person first found the business.
Keep those details separate. Preserve campaign information when it is available and leave room for uncertainty when it is not. An empty field is more useful than a confident but misleading default.
Check permission choices in the same way. If someone leaves an optional newsletter box unchecked, does that choice survive the journey into the systems used for email marketing?
Test a declined choice and a blank field. Ask the person responsible for your privacy requirements to confirm how the business should record and use that information.
Now ask a straightforward question: who is supposed to do something with this enquiry?
"Everyone gets the email" is an incomplete answer.
Look for a named owner or a queue that someone is responsible for checking. The arrangement can be simple. A small team might manage perfectly well with a shared queue, provided someone checks it and knows when to step in.
Then consider an ordinary disruption. The usual recipient is on leave. The customer selects a service that has no assignment rule. An enquiry arrives late on Friday.
What happens next?
You should be able to explain the answer without relying on a particular colleague remembering to forward an email. Check who watches for unassigned records and how overdue enquiries become visible.
Separate receipt from a useful reply.
An acknowledgement email tells the customer that the message arrived. That is worth doing, but it should have its own place in your reporting.
Track submission, CRM creation, assignment, and the first meaningful response separately. Otherwise, a fast automated email can conceal a long wait for help.
Agree on what counts as meaningful. It could be an answer to the question, a request for information needed to assess it, or a clear explanation of when the right person will respond.
Choose a standard the team can meet consistently. If the website promises one business day, make sure someone can find enquiries approaching that deadline. Check how weekends and holidays affect the promise. This gives your lead follow-up process a clear starting point: an enquiry somebody owns and knows how to handle.
Finally, ask whoever maintains the connection how a failed handoff would be detected. Where possible, test that process in a safe environment or through another agreed method.
Who gets the alert? Can the original submission be recovered? Could retrying it cause two people to contact the same customer?
Finish with a short list of fixes, each with an owner and a date to test it again. Repeat the exercise after changing a form, an integration, or an assignment rule.
Customers cannot see any of this. They have sent questions and are waiting for your business to take it from there. A good handoff makes that expectation reasonable.
Allan Diel is a web developer and lead consultant at ADPH Consulting.