Turn an enquiry into a useful next step.

Keep the original request available to the reviewer. A short label such as “pricing lead” may lose the product, delivery condition or existing conversation that explains what the person needs. Separate their words from any category or summary the system suggests.

Identify the requested action. Someone may want a specification, a delivery answer, a revised quote or help with an existing order. Routing every request into a new-business sequence can make the recipient repeat information and create work for the wrong team.

Collect enough information to handle the enquiry without forcing a premature buying questionnaire. When something is missing, ask a useful next question. A request can be worth a response even when the budget, purchasing process or exact scope is not yet known.

Check the company and operating unit, the existing relationship, the account owner and relevant open work. Make an uncertain identity match visible. An email domain may suggest a group relationship without proving which site, contract or purchasing unit is involved.

The account research brief helps prepare source evidence and questions. For known customers, the account plan can explain current priorities and relationships. Use that context to improve the response, not to infer that a new requirement has already been qualified.

Where useful, keep the campaign or content that prompted the enquiry, including what it promised the reader. A person who read an order-preparation guide may be asking about internal processing rather than placing an order. Knowing which promise they encountered can prevent a sales response to the wrong task.

Fit concerns whether the business can serve the requirement: location, product or service, operating conditions and material exclusions. Use the ideal customer profile as a starting point, then assess the actual request rather than accepting a company-level label as sufficient.

Activity describes observed events such as an enquiry, page visit or meeting. It can help prioritise a review, but it does not tell you everything about the person’s need or authority. HubSpot’s scoring documentation distinguishes property-based fit scores from event-based engagement scores. Your qualification decision still needs a business definition and a responsible person.

Readiness concerns the next decision the customer can usefully make. A clear requirement with an agreed technical discussion may be ready for that discussion while still being far from a purchase. Record what has been agreed and what remains open instead of collapsing these states into a single “hot” label.

Choose the smallest unresolved issue that prevents a useful response. In the branch example, a product reference may need clarification before a price is meaningful. Asking for a full procurement process first could add friction while leaving the immediate problem untouched.

Phrase the question so the customer can correct your assumption: “Does this request sit under the existing group arrangement, or does the branch buy separately?” gives the customer a chance to correct the context. “We have opened a new opportunity for your expansion” would assert a project they have not described.

Record the answer and its source. Where a quotation becomes the next step, the quote follow-up guide keeps the current version and the customer’s next decision clear. A follow-up should refer to that decision, not just the elapsed time since the last email.

A workflow can preserve the request, suggest a category, find a possible account match and prepare a reviewer task. It can highlight missing information and draft a clarification for approval. Define which of those actions are allowed and which require a person.

Lead routing rules need an owner, cover and a destination for ambiguous cases. The reviewer needs a way to correct the category or match without losing the original request. Changes should improve the record rather than force the person to work around it in a separate inbox.

Keep website observations separate from the enquiry’s explicit statements. A matched company visit can be relevant context for review. It does not establish that the sender visited those pages, holds a buying role or has authorised an unrelated sales approach.

Examine a small varied sample of enquiries: suitable, unsupported, ambiguous, existing-customer and incomplete requests. Ask whether the recorded status explains the evidence and whether the next action was actually agreed. A pipeline full of records with guessed values is not evidence of better qualification.

Track missing context, incorrect matches and requests awaiting an owner separately from the reasons a request is unsuitable. Keep operational problems distinct from commercial outcomes. A slow response may be a handover issue; an unsupported location may be a campaign or targeting issue.

A bounded task that prepares checked records or clarification drafts may fit AI Workflows; a standalone enquiry process receives its own scope and quote. In a Build campaign, agree who reviews responses, asks clarifying questions, qualifies an opportunity and arranges a next conversation. ClarityRev can take on the agreed response work. Sales conversations, phone follow-up, product commitments and pricing decisions stay with your team. Define that division before deciding what to automate.