Define qualification inputs
Choose fields that decide the next action: postcode or project location, supply versus installation, product family, approximate footprint and intended timing. If a field is optional, define a route for an unanswered value. For example, an unsupported product request can go to review while an in-territory request for a standard range goes to the assigned sales team. Keep the routing reason visible.
Keep rules and decisions separate
Write the routing rules against the submitted product and project fields. Define whether a rule routes a project, flags missing information or asks for review. Keep the responsible sales decision identifiable, and avoid interpreting an incomplete draft as a submitted buyer request.
Check the results before relying on them
Test realistic submissions, autofill, pasted information and missing optional fields. Review whether the assigned person receives the chosen configuration and understands the routing reason. Compare submitted inquiries and qualified proposals using actual recorded outcomes, not an opaque score promoted as a guarantee.
Implementation checklist
- Relevant qualification inputs
- Routing versus review distinguished
- Autofill and incomplete cases
- Recorded commercial decisions