Start with the decision after the enquiry
Before choosing acronyms or scoring rules, describe the decision the team needs to make. Should the person receive an initial response, a technical assessment, a referral to a representative or further follow-up? Different routes can require different information and owners.
For manufacturers and technical distributors, interest often relates to an application, an operational requirement or a project. A completed form does not establish purchase intent or a sales opportunity. The first task is to understand the request and determine whether there is enough relevant information to choose a next action.
Choose one area to start with, such as enquiries for a product line or campaign. Mapping the whole business at once can conceal differences between channels and create an agreement that is difficult to use. A bounded pilot helps the team identify adjustments before extending the routine.
Define criteria that people can observe
Qualification should not rely entirely on individual judgement. Agree what the team needs to know before routing an enquiry, separating essential information from details that can be established during a conversation. Requiring every detail before responding can create unnecessary friction.
Separate fit from timing. A company may match the target market while still exploring options. Another may need an immediate response for a product or territory outside your coverage. These cases need different destinations even if they arrive through the same campaign.
Avoid importing another company’s definition of a qualified lead without examining your operation. If you use MQL or SQL, document what each term means locally and what evidence permits a stage change. The terminology is useful only when the teams interpret it consistently.
- Does the company and its application fit the business you serve?
- Is the request clear enough to select the appropriate respondent?
- Is there sales coverage or a suitable partner for the territory?
- Can the available information support a meaningful next action?
Transfer the context with the contact details
A name and email address identify who made an enquiry, but they may not explain why. The record should allow the owner to continue the conversation without asking for information already provided. That requires organisation rather than indiscriminate data collection.
Agree a minimum record: company, source, request, application where known, previous routing and suggested next action. Include information that remains unconfirmed. An assumption about interest or potential should not appear as an established fact in the history.
Use the tools already available when they are sufficient. The important requirements are a record accessible to authorised people, understandable fields and consistent updates. Avoid maintaining conflicting versions across spreadsheets, inboxes and messages without a common reference.
Agree acceptance, timing and backup ownership
Forwarding an enquiry does not complete the handoff. The team needs to know whether the intended recipient has accepted responsibility. Define who monitors the queue, how acceptance is recorded and what happens when someone is absent or unable to take the case.
Response expectations should reflect the request, operating hours and team capacity. An urgent commercial enquiry may need different handling from early research. There is no universal response target suited to every situation; the agreement needs to be feasible, understood and reviewed.
- A primary receiving owner and an identified backup.
- An agreed period to assess the case and record the first action.
- An escalation route for handoffs that remain unacknowledged.
- A destination for duplicates, unsuitable enquiries and cases needing more time.
Make feedback useful for the next handoff
Sales feedback needs more detail than “good lead” or “bad lead”. Specific reasons help marketing review targeting, content and channels. They also help distinguish an acquisition issue from a service issue or a record that lacks essential context.
A short classification might identify an unsupported application, uncovered territory, duplicate enquiry, project without a confirmed timeframe or conversation with an agreed next action. The list should be simple enough to use and specific enough to support a decision.
Cases that cannot progress yet may need a review point or a suitable alternative route. Record the reason and the condition for reopening the case. Follow-up must respect the original request and applicable communication requirements; retaining a record does not authorise every future approach.
An illustrative technical enquiry
Imagine a distributor receiving a website enquiry about components for an industrial application. Marketing records the source and request. The receiving owner checks whether the relevant product range is supported, identifies the territory and forwards the context to the assigned sales contact.
Sales acknowledges the handoff and finds that a technical specification is missing. Instead of treating the lead as lost, the owner records the missing detail and arranges an assessment with the technical team. The history is then updated with the response and next action.
If the application falls outside the portfolio, that reason is recorded too. During the campaign review, marketing can investigate whether the content attracts unsuitable requests. This is an illustrative workflow, not a customer example, an observed result or a mandatory process for every business.
Monitor the quality of the process
Begin with a small set of measures: eligible enquiries handed over, sales acceptance, first actions within the agreed period and records without a next step. Define the base of each calculation and separate channels or product lines with different rules.
Review a sample of cases with the people involved. Numbers identify where to investigate; records help explain what happened. More rejected enquiries could reflect poor targeting, revised criteria or simply more consistent recording of rejection reasons.
Update the agreement when the evidence supports a change and communicate it to the people using the process. Lead handoff is a shared routine that depends on clear criteria, active ownership and learning from actual cases. Alder & Hale can support these connections across marketing, sales and partners within a defined engagement.