The enquiry described a sensible need. It included a location and a clear question. It was quite a pleasant enquiry, as enquiries go.
The person receiving it couldn't help.
Another team could, but that detail was not obvious from the message. The request began a small tour of the organisation.
I find this kind of problem easy to miss when reviewing lead quality. A request can be suitable for the business and unsuitable for the desk where it lands. If we call it a poor lead immediately, we may be mislabelling a routing problem.
The customer has usually done what the page invited them to do. They don't know our internal divisions. Their message shouldn't require an apprenticeship in the company structure.
Follow the first reply
For a fictional review, I drafted the opening answer to three sample enquiries. One fitted the receiving team. One belonged elsewhere. One didn't fit the offer.
Writing those replies made the differences clearer than a score attached to each form submission.
For the second request, the receiving colleague could have helped by passing it along with enough context. Instead, the sample reply asked the customer to use another form and describe the same thing again.
That is an irritating handover even when everyone means well.
I would want the message to include the relevant page or service, the customer's actual request and whatever detail lets the team recognise where it belongs. Sometimes the destination page already gives us most of that context. We just fail to carry it into the notification.
Adding several new form fields may be unnecessary if the website already knows which offer the customer has been reading.
Make the choice understandable
If the visitor genuinely needs to choose between services, use labels they can recognise. A department abbreviation might be exact internally and meaningless on a public form.
Examples can help. A short description of the situation each service handles can support a choice without asking the customer to diagnose the whole requirement.
There should also be a route for uncertainty. A person who isn't sure should not have to pick a misleading option simply to submit.
The receiving process then needs a way to handle that uncertainty. A thoughtfully worded form is only half the improvement if the message still reaches an unattended inbox.
This is the part where marketing needs a colleague who knows what actually happens after submission. I can make the invitation clearer; I cannot discover the whole handover by admiring the page.
Keep unsuitable and misdirected apart
When reviewing a sample, I would record why a request couldn't progress. Was the offer wrong for the need? Was a decisive detail missing? Was it sent to the wrong team? Did it need a conversation before anyone could judge it?
Those explanations lead to different changes.
A misdirected request may need a better route. A genuinely unsuitable one may need clearer limits on the page. A thin request may need a better prompt.
Combine all three under “bad leads” and we risk adjusting the advertisement to solve the wrong bloody problem.
I like a handover that lets the customer continue from what they already told us. It feels modest, but it respects the effort they've made.
A useful request shouldn't become useless merely because it took the wrong corridor.
A thought worth keeping?
