B2B lead scoring and routing
Prioritise by service fit and expressed need, with explainable scores, ownership and exception handling.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
Lead scoring prioritises follow-up rather than automatically judging customer value. Define valid enquiries, fit and urgency, separating rule scores from human decisions. Routing must handle existing customers, duplicates, absence, unaccepted assignments and returns with visible reasons.
When to use this guide
For sales teams with missed follow-ups, disputed ownership or manual form-enquiry assignment.
Scoring and routing rules
| Area | Rule example | Acceptance |
|---|---|---|
| Validity | Contactable, non-test, non-spam | Unknown distinct from invalid |
| Fit | Service need and project stage | Explainable reason retained |
| Routing | Existing customer, region, capacity | Conflict, absence, unaccepted task |
| Review | Manual override and return | Reason, owner and history |
Use available data and preserve unknowns
Missing budget or timing does not establish low intent; preserve unknowns and seek clarification. Do not substitute unrelated personal traits for procurement needs. Explain the purpose of each rule and review mistaken assignments and overlooked enquiries.
Require ownership after assignment
Track assignment, acceptance, meaningful first follow-up and reassignment instead of treating a notification as completion. Provide fallback queues for absence, overload or no response. Preserve existing customer relationships while retaining new needs and a reviewable history.
Review rules against actual outcomes
Compare acceptance, meaningful contact, qualification and opportunity progression by enquiry type. Retain counts and periods when samples are small rather than claiming guaranteed conversion gains. Version rule changes so comparisons remain interpretable.
Illustrative scenario
Hypothetical routing: a CRM integration enquiry goes to the integration team. Missing budget remains unknown for staff clarification. An absent owner triggers a fallback queue rather than downgrading the enquiry. This is an illustrative rule set.
Frequently asked questions
Does scoring require AI?
Clear rules can use ordinary automation; add AI only where useful and testable.
Does a high score guarantee a sale?
No. A score only prioritises work using known conditions.
Should repeated enquiries be deleted?
Distinguish resubmission from a new project and preserve needs and provenance.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service