
Inbound Capture
Part of B2B website conversion paths
Helping visitors choose the right enquiry route
Visitors should not have to know a company's internal departments to ask a useful question.
Visitors should not have to know a company's internal departments to ask a useful question. Offer routes based on their task, and say what response each route produces.
Name the choices by outcome
“See the product” can lead to a demo; “discuss a project” to a consultation; “ask about an order” to support. State whether a call, email or self-serve answer follows. Keep the options few enough to scan. If a visitor cannot tell which applies, offer a general enquiry route with a clear owner rather than forcing a guess.
On service pages, recommend the most relevant path and preserve the page context in the enquiry record. Test whether a request from each page reaches the intended team. A wrong route creates friction after the form as surely as a long form does before it.
Write the confirmation message for each route as carefully as the form itself. After submitting, visitors should see what will happen, who will respond and roughly when. A vague thank-you can leave people unsure whether the request arrived, and some may then try another route.
Enquiry Route Outcomes and Expected Responses
- See the product
- Demo scheduled (call or email)
- Discuss a project
- Consultation booked (call or email)
- Ask about an order
- Support response (email or self-serve)
- General enquiry
- Forwarded to designated owner (email)
Check usability and measurement
Use clear field labels and instructions; W3C guidance explains that labels should be associated with controls so people can identify what to enter. Track completed submissions separately by route.
Google Analytics publishes guidance on recommended events, so check its documentation and note that any event used to record a submitted request must be configured and verified. Review misrouted enquiries and no-response cases with sales and support, then revise labels based on actual confusion rather than click volume alone.
Usability and Measurement Best Practices
- Use clear, descriptive labels for form fields
- Associate labels with their input controls
- Track submissions by enquiry route in analytics
- Verify event tracking configuration for request submissions
- Review misrouted enquiries with sales and support teams
- Revise labels based on real user confusion, not just click volume
Review routes as the business changes
A new service, a retired product or a reorganised team can quietly make an option misleading. Ask the people who handle the enquiries which route labels still match the requests they receive, and remove any choice that no longer leads to a distinct response.


